date:20180826

This change was made by a bot.

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

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

Title:
  Ubuntu Freezes While Playing Video

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever any video is being played, after few minutes sometimes early
  sometimes late the ubuntu system got freezes and only way to get out
  is to power off from the hard reset.

  uname -a
  Linux Logan 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  free
totalusedfree  shared  buff/cache   
available
  Mem:1925572 1544948   76088  144920  304536  
193280
  Swap:   2097148  213772 1883376

  
  lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  1
  Core(s) per socket:  4
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   55
  Model name:  Intel(R) Celeron(R) CPU  N2930  @ 1.83GHz
  Stepping:8
  CPU MHz: 725.170
  CPU max MHz: 2165.8000
  CPU min MHz: 499.8000
  BogoMIPS:3665.20
  Virtualization:  VT-x
  L1d cache:   24K
  L1i cache:   32K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi 
flexpriority ept vpid tsc_adjust smep erms dtherm ida arat

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikki  9401 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 26 18:18:21 2018
  InstallationDate: Installed on 2018-08-15 (11 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=357ffd1f-7b8f-431d-b765-be7ea2205ff9 ro quiet splash acpi=force 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.502
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-08-26 Thread Robin Bettridge

Peter Smith - I had the same experience of trying the 4.15.0-33 and it not 
working for me.
** Try 4.15.0.23 if you would like to be on the 4.15 kernel **

Background:
In my case I am running Mint, but same Ubuntu kernels. It is a desktop PC which 
is not often suspended so I noticed the problem only a couple of days ago, when 
already on 4.15.0-30, so tried the 4.15.0-33 which Mint's update manager was 
offering.. no improvement. The modprobe trick worked and I have a Realtec NIC.

I had seen references to 4.13.0-31 working and also 4.15.0-20, both of
which worked for me.

I worked my way up through the following:-
4.15.0-20 resumes
4.15.0-22 resumes
4.15.0-23 resumes
4.15.0-24 does not resume
4.15.0-30 does not resume
4.15.0-33 does not resume
The modprobe treatment worked for the recent -30 and -33, but curiously not on 
-24. That's probably a symptom of progress.

I thought I experienced a surprising result of going to -24 then back to -23 
and the problem reappearing in -23. After a power-off restart all was well 
again. I had a theory that maybe since all I was doing were OS "restarts" 
without the PC shutting down the hardware might be holding some state.
I've tried recreating that problem (because it seemed such a dodgy assertion) - 
but without luck. On the one hand it might be a valid thought that it is very 
easy to just do restarts between kernels and actually still be holding some 
unfortunate state in the hardware - OR my bad in accidentally booting the wrong 
kernel (I've mostly done a uname -a check straight after the boot)

There do seem to have been some inconsistencies in people's experiences, so I 
wonder if hardware state can be a factor, after all, we are in the area of 
suspended motherboard h/w
People who know more about Linux initial initialisation of hardware may say I'm 
talking bo***cks!

Anyway, I'm happy with suspend/resume with 4.15.0-23-generic

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mi

[Kernel-packages] [Bug 1781879] [NEW] Latest ASUS trackpad doesn't work in Ubuntu

You have been subscribed to a public bug:

It seems there might be a new hardware variant of the elan trackpad in
the newer ASUS machines.

The issue is the shown here with some reasonably deep investigation.  Is
this something that I can do or am I reduced to having to find out a
mouse if I want to use Linux?

https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
 Virtual core pointer  id=2[master pointer  (3)]
   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
   ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
   ↳ Logitech USB Receiver id=13   [slave  pointer  (2)]
 Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Video Bus id=9[slave  keyboard (3)]
↳ Power Button  id=10   [slave  keyboard (3)]
↳ Sleep Button  id=11   [slave  keyboard (3)]
↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Latest ASUS trackpad doesn't work in Ubuntu
https://bugs.launchpad.net/bugs/1781879
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

2018-08-26 Thread Paul White

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems there might be a new hardware variant of the elan trackpad in
  the newer ASUS machines.

  The issue is the shown here with some reasonably deep investigation.
  Is this something that I can do or am I reduced to having to find out
  a mouse if I want to use Linux?

  https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

  user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
   Virtual core pointer  id=2[master pointer  (3)]
 ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
 ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
 ↳ Logitech USB Receiver id=13   [slave  pointer  (2)]
   Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
  ↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

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

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2018-08-26 Thread esl

The same problem. Clean install. Asus S46CM.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  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.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: RF511/RF411/RF711
  dmi.product.

[Kernel-packages] [Bug 1777238] Re: video lag

2018-08-26 Thread Jon Delano

Something to try, run system monitor. If I have it open I don't have any
issues playing videos. Strange but true.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem exists for months and I didn't find a good answer on it.
  It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind
  the video the sounds continues, but the video stops), youtube,
  Hangouts and every software where video is played.

  I experienced that there are 2 things that can break it:
   - if I move the mouse out and in on the affected window (it doesn't work in 
full screen)
   - if I open the system monitor, the problem also disappears

  other people also face with this problem:
  
https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters
  
https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome
  
https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194
  https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04

  Ubuntu 4.15.0-23.25-generic 4.15.18
  it was upgraded from 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 14:34:26 2018
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2016-08-04 (680 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  vandor 3436 F pulseaudio
   /dev/snd/controlC1:  vandor 3436 F pulseaudio
   /dev/snd/controlC0:  vandor 3436 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c
  InstallationDate: Installed on 2016-08-04 (681 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1789118] [NEW] Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2018-08-26 Thread Andy Smith

Public bug reported:

After the most recent 18.04 32-bit upgrade of linux-image-generic, it
now refuses to boot under Xen PV mode:

.
.
.
[0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
[0.114423] pinctrl core: initialized pinctrl subsystem
[0.134326] RTC time: 165:165:165, date: 165/165/65
[0.134442] NET: Registered protocol family 16
[0.134457] xen:grant_table: Grant tables using version 1 layout
[0.134502] Grant table initialized
[0.134544] audit: initializing netlink subsys (disabled)
[0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
[0.134678] EISA bus registered
[0.136019] PCI: setting up Xen PCI frontend stub
[0.136073] BUG: unable to handle kernel paging request at edc21fd9
[0.136084] IP: eisa_bus_probe+0x19/0x36
[0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
[0.136100] Oops:  [#1] SMP
[0.136105] Modules linked in:
[0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
[0.136120] EIP: eisa_bus_probe+0x19/0x36
[0.136125] EFLAGS: 00010246 CPU: 0
[0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
[0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
[0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
[0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
[0.136166] Call Trace:
[0.136173]  do_one_initcall+0x49/0x174
[0.136179]  ? parse_args+0x143/0x390
[0.136187]  ? set_debug_rodata+0x14/0x14
[0.136193]  kernel_init_freeable+0x149/0x1c5
[0.136201]  ? rest_init+0xa0/0xa0
[0.136207]  kernel_init+0xd/0xf0
[0.136213]  ret_from_fork+0x2e/0x38
[0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
[0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
[0.14] CR2: edc21fd9
[0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
[0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

This is: [0.00] Linux version 4.15.0-33-generic
(buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
#36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu 4.15.0-33.36-generic
4.15.18)

Switching to a 64-bit kernel allows boot to proceed.

I cannot include output of the commands you request (uname,
version_signature, dmesg, lspci) because the guest doesn't boot. The
above kernel output is from a just-installed clean guest however.

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1789118

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

Status in linux-meta package in Ubuntu:
  New

Bug description:
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it
  now refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeabl

[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2018-08-26 Thread Andy Smith

Additionally, this means that the netboot installer at e.g.
http://gb.archive.ubuntu.com/ubuntu/dists/bionic/main/installer-i386/current/images/netboot/xen/vmlinuz
also does not boot under Xen PV. Again, the 64-bit equivalent does still
work.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1789118

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

Status in linux-meta package in Ubuntu:
  New

Bug description:
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it
  now refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

Status in linux package in Ubuntu:
  New

Bug description:
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it
  now refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

[Kernel-packages] [Bug 1789118] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1789118

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: bionic

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it
  now refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2018-08-26 Thread Andy Smith

I am unable to run apport-collect because the guest does not boot.

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

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it
  now refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 
 
  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

[Kernel-packages] [Bug 1789131] [NEW] Probable regression with EXT3 file systems and CVE-2018-1093 patches

Public bug reported:

A customer reported on all of their ext3 and none of their ext4 systems
that the file system was in read-only mode, I believe after rebooting
into 3.13.0-157.207 from 3.13.0-156.206. Here is the output of tune2fs
-l for one of the file systems:

tune2fs 1.42.12 (29-Aug-2014)
Last mounted on:  /
Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype 
needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options:(none)
Filesystem state: clean with errors
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  1966080
Block count:  7863296
Reserved block count: 393164
Free blocks:  4568472
Free inodes:  1440187
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  1022
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
RAID stride:  128
RAID stripe width:512
Filesystem created:   Thu Feb 25 21:54:24 2016
Last mount time:  Fri Aug 24 07:40:51 2018
Last write time:  Fri Aug 24 07:40:51 2018
Mount count:  1
Maximum mount count:  25
Last checked: Fri Aug 24 07:38:54 2018
Check interval:   15552000 (6 months)
Next check after: Wed Feb 20 07:38:54 2019
Lifetime writes:  7381 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:  256
Required extra isize: 28
Desired extra isize:  28
Journal inode:8
Default directory hash:   half_md4
Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
Journal backup:   inode blocks
FS Error count:   210
First error time: Fri Aug 24 07:40:51 2018
First error function: ext4_validate_block_bitmap
First error line #:   376
First error inode #:  0
First error block #:  0
Last error time:  Sun Aug 26 19:35:16 2018
Last error function:  ext4_remount
Last error line #:4833
Last error inode #:   0
Last error block #:   0

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  New

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:   inode blocks
  FS Error count:   210
  First error time: Fri Aug 24 07:40:51 2018
  First error function: ext4_validate_block_bitmap
  Firs

[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches

I noticed the unusual thing here is:

RAID stride: 128
RAID stripe width: 512

I'm going to do some testing around this to see if it's related. It
could be this is the issue and not anything EXT3 vs. EXT4.

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  New

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:   inode blocks
  FS Error count:   210
  First error time: Fri Aug 24 07:40:51 2018
  First error function: ext4_validate_block_bitmap
  First error line #:   376
  First error inode #:  0
  First error block #:  0
  Last error time:  Sun Aug 26 19:35:16 2018
  Last error function:  ext4_remount
  Last error line #:4833
  Last error inode #:   0
  Last error block #:   0

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-08-26 Thread monogato

I agree with #13

The problem is still there, switching to power saving mode doesn't save
any power since the graphic card is always on anyway.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Incomplete
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  
  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  
  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

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

[Kernel-packages] [Bug 1789131] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1789131

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1789131

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:   inode blocks
  FS Error count:   210
  First error time: Fri Aug 24 07:40:51 2018
  First error function: ext4_validate_block_bitmap
  First error line #:   376
  First error inode #:  0
  First error block #:  0
  Last error time:  Sun Aug 26 19:35:16 2018
  Last error function:  ext4_remount
  Last error line #:4833
  Last error inode #:   0
  Last error block #:   0

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

[Kernel-packages] [Bug 1789135] [NEW] package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-08-26 Thread Kevin Greene

Public bug reported:

Now unable to restart current applications on the host.
Serious problem.

root@xray:/boot# su zimbra
zimbra@xray:/boot$ zmcontrol start
Perl API version v5.14.0 of Socket does not match v5.18.0 at 
/usr/share/perl/5.18/XSLoader.pm line 117.
Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
Compilation failed in require at /opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm 
line 23.
BEGIN failed--compilation aborted at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27.
BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27.
zimbra@xray:/boot$

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-45-generic 3.13.0-45.74
ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-117-generic x86_64
NonfreeKernelModules: gpio_ich lpc_ich hpilo mac_hid e752x_edac edac_core 
shpchp tg3 cciss pata_acpi
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 26 19:29 seq
 crw-rw 1 root audio 116, 33 Aug 26 19:29 timer
AplayDevices: aplay: device_list:268: no soundcards found...
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: arecord: device_list:268: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Sun Aug 26 20:36:34 2018
DuplicateSignature: 
package:linux-image-3.13.0-45-generic:3.13.0-45.74:subprocess installed 
post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=01d95e3f-884b-481d-b871-b941923121e2
InstallationDate: Installed on 2011-04-13 (2692 days ago)
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
IwConfig:
 eth2  no wireless extensions.
 
 eth3  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: HP ProLiant DL380 G4
PciMultimedia:
 
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-117-generic 
root=/dev/mapper/hostname-root ro text
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
Title: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: Upgraded to trusty on 2018-08-26 (0 days ago)
dmi.bios.date: 07/19/2007
dmi.bios.vendor: HP
dmi.bios.version: P51
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP51:bd07/19/2007:svnHP:pnProLiantDL380G4:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL380 G4
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade trusty

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

Title:
  package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  Now unable to restart current applications on the host.
  Serious problem.

  root@xray:/boot# su zimbra
  zimbra@xray:/boot$ zmcontrol start
  Perl API version v5.14.0 of Socket does not match v5.18.0 at 
/usr/share/perl/5.18/XSLoader.pm line 117.
  Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  Compilation failed in require at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  BEGIN failed--compilation aborted at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27.
  BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27.
  zimbra@xray:/boot$

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  NonfreeKernelModules: gpio_ich lpc_ich hpilo mac_hid e752x_edac edac_core 
shpchp tg3 cciss pata_acpi
  AlsaDevices:
   total 0

[Kernel-packages] [Bug 1789135] Re: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-08-26 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  Now unable to restart current applications on the host.
  Serious problem.

  root@xray:/boot# su zimbra
  zimbra@xray:/boot$ zmcontrol start
  Perl API version v5.14.0 of Socket does not match v5.18.0 at 
/usr/share/perl/5.18/XSLoader.pm line 117.
  Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  Compilation failed in require at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  BEGIN failed--compilation aborted at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27.
  BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27.
  zimbra@xray:/boot$

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  NonfreeKernelModules: gpio_ich lpc_ich hpilo mac_hid e752x_edac edac_core 
shpchp tg3 cciss pata_acpi
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 26 19:29 seq
   crw-rw 1 root audio 116, 33 Aug 26 19:29 timer
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Aug 26 20:36:34 2018
  DuplicateSignature: 
package:linux-image-3.13.0-45-generic:3.13.0-45.74:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=01d95e3f-884b-481d-b871-b941923121e2
  InstallationDate: Installed on 2011-04-13 (2692 days ago)
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  IwConfig:
   eth2  no wireless extensions.
   
   eth3  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: HP ProLiant DL380 G4
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-117-generic 
root=/dev/mapper/hostname-root ro text
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  Title: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to trusty on 2018-08-26 (0 days ago)
  dmi.bios.date: 07/19/2007
  dmi.bios.vendor: HP
  dmi.bios.version: P51
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP51:bd07/19/2007:svnHP:pnProLiantDL380G4:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 G4
  dmi.sys.vendor: HP

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

[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches

I confirmed that adding "-E stride=128,stripe_width=512" to the call to
mkfs results gets the following errors almost immediately at boot with
3.13.0-157.207:

[5.680480] EXT4-fs error (device xvda1): ext4_validate_block_bitmap:376: 
comm mountall: bg 213: block 7007360: invalid block bitmap
[5.681182] Aborting journal on device xvda1-8.
[5.681827] EXT4-fs (xvda1): Remounting filesystem read-only
[5.681850] EXT4-fs error (device xvda1) in ext4_free_blocks:4876: IO failure
[5.682538] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4967: 
Journal has aborted
[5.683254] EXT4-fs error (device xvda1) in ext4_orphan_del:2682: Journal 
has aborted
[5.683883] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4967: 
Journal has aborted

And that this does not happen without stride=128,stripe_width=512 and
that is not present in 3.13.0-156.206.


It does *not* happen with ext4 and "-E stride=128,stripe_width=512" being set. 
This file system mounted without errors:

Last mounted on:  /
Filesystem UUID:  12df937e-795c-4d98-a90b-dca002109a34
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype 
needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg 
dir_nlink extra_isize
Filesystem flags: signed_directory_hash 
Default mount options:(none)
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  1966080
Block count:  7863296
Reserved block count: 393164
Free blocks:  7358461
Free inodes:  1885947
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  1022
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
RAID stride:  128
RAID stripe width:512
Flex block group size:16
Filesystem created:   Sun Aug 26 21:06:58 2018
Last mount time:  Sun Aug 26 21:14:39 2018
Last write time:  Sun Aug 26 21:14:39 2018
Mount count:  3
Maximum mount count:  20
Last checked: Sun Aug 26 21:06:58 2018
Check interval:   15552000 (6 months)
Next check after: Fri Feb 22 21:06:58 2019
Lifetime writes:  2504 MB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Journal inode:8
Default directory hash:   half_md4
Directory Hash Seed:  8d081584-5ec6-4446-a213-97f2012d8755
Journal backup:   inode blocks

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:

[Kernel-packages] [Bug 1789135] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Now unable to restart current applications on the host.
  Serious problem.

  root@xray:/boot# su zimbra
  zimbra@xray:/boot$ zmcontrol start
  Perl API version v5.14.0 of Socket does not match v5.18.0 at 
/usr/share/perl/5.18/XSLoader.pm line 117.
  Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm line 10.
  Compilation failed in require at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  BEGIN failed--compilation aborted at 
/opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23.
  Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27.
  BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27.
  zimbra@xray:/boot$

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  NonfreeKernelModules: gpio_ich lpc_ich hpilo mac_hid e752x_edac edac_core 
shpchp tg3 cciss pata_acpi
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 26 19:29 seq
   crw-rw 1 root audio 116, 33 Aug 26 19:29 timer
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Aug 26 20:36:34 2018
  DuplicateSignature: 
package:linux-image-3.13.0-45-generic:3.13.0-45.74:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=01d95e3f-884b-481d-b871-b941923121e2
  InstallationDate: Installed on 2011-04-13 (2692 days ago)
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  IwConfig:
   eth2  no wireless extensions.
   
   eth3  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: HP ProLiant DL380 G4
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-117-generic 
root=/dev/mapper/hostname-root ro text
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  Title: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to trusty on 2018-08-26 (0 days ago)
  dmi.bios.date: 07/19/2007
  dmi.bios.vendor: HP
  dmi.bios.version: P51
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP51:bd07/19/2007:svnHP:pnProLiantDL380G4:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 G4
  dmi.sys.vendor: HP

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

[Kernel-packages] [Bug 1789135] BOT: Examined VarLogDistupgradeApttermlog.gz

Internal Error: Could not find image (/boot/vmlinuz-3.13.0-100-generic)
   dpkg: error processing package linux-image-3.13.0-100-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-101-generic)
   dpkg: error processing package linux-image-3.13.0-101-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-103-generic)
   dpkg: error processing package linux-image-3.13.0-103-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-105-generic)
   dpkg: error processing package linux-image-3.13.0-105-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-106-generic)
   dpkg: error processing package linux-image-3.13.0-106-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-107-generic)
   dpkg: error processing package linux-image-3.13.0-107-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-108-generic)
   dpkg: error processing package linux-image-3.13.0-108-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-109-generic)
   dpkg: error processing package linux-image-3.13.0-109-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-110-generic)
   dpkg: error processing package linux-image-3.13.0-110-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-112-generic)
   dpkg: error processing package linux-image-3.13.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-115-generic)
   dpkg: error processing package linux-image-3.13.0-115-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-116-generic)
   dpkg: error processing package linux-image-3.13.0-116-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-117-generic)
   dpkg: error processing package linux-image-3.13.0-117-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   ) points to /boot/vmlinuz-3.13.0-157-generic
(/boot/vmlinuz-3.13.0-157-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-3.13.0-157-generic.postinst line 491.
   Examining /etc/kernel/postinst.d.

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-44-generic)
   dpkg: error processing package linux-image-3.13.0-44-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-45-generic)
   dpkg: error processing package linux-image-3.13.0-45-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-46-generic)
   dpkg: error processing package linux-image-3.13.0-46-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-48-generic)
   dpkg: error processing package linux-image-3.13.0-48-generic (--configure):
subprocess installed post-installation script returned error exit status 2

   Internal Error: Could not find image (/boot/vmlinuz-3.13.0-49-generic)
   dpkg: error processing package linux-image-3.13.0-49-generic (--configure):
subprocess installed post-installation script returned error exit status 2


** Tags added: varlogdistupgradeapttermlog-examined

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

Title:
  package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Now unable to restart current applications on the host.
  Serious problem.

  root@xray:/boot# su zimbra
  zimbra@

[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches

I believe a command sequence like this can be used to reliably reproduce
the issue:

umount /mnt
truncate -s128m /tmp/test.img
cmd="/sbin/mkfs.ext3 -E stride=128,stripe_width=512 -F /tmp/test.img"
echo $cmd > /dev/kmsg
$cmd
mount -o loop /tmp/test.img /mnt/
while dd if=/dev/zero of=/mnt/$RANDOM bs=1M count=1; do true; done

I do not see any failures when ext4 is replaced for ext3 above.

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:   inode blocks
  FS Error count:   210
  First error time: Fri Aug 24 07:40:51 2018
  First error function: ext4_validate_block_bitmap
  First error line #:   376
  First error inode #:  0
  First error block #:  0
  Last error time:  Sun Aug 26 19:35:16 2018
  Last error function:  ext4_remount
  Last error line #:4833
  Last error inode #:   0
  Last error block #:   0

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

[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches

As for running

apport-collect 1789131

This doesn't appear to work well in a headless system with a minimal
install. I believe I've given all the necessary details for reproducing
the issue.

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

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:   inode blocks
  FS Error count:   210
  First error time: Fri Aug 24 07:40:51 2018
  First error function: ext4_validate_block_bitmap
  First error line #:   376
  First error inode #:  0
  First error block #:  0
  Last error time:  Sun Aug 26 19:35:16 2018
  Last error function:  ext4_remount
  Last error line #:4833
  Last error inode #:   0
  Last error block #:   0

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

[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches

This problem doesn't show up in 4.4.0-134-generic.

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

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:  /
  Filesystem UUID:  748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags: signed_directory_hash
  Default mount options:(none)
  Filesystem state: clean with errors
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  1966080
  Block count:  7863296
  Reserved block count: 393164
  Free blocks:  4568472
  Free inodes:  1440187
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  1022
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:512
  Filesystem created:   Thu Feb 25 21:54:24 2016
  Last mount time:  Fri Aug 24 07:40:51 2018
  Last write time:  Fri Aug 24 07:40:51 2018
  Mount count:  1
  Maximum mount count:  25
  Last checked: Fri Aug 24 07:38:54 2018
  Check interval:   15552000 (6 months)
  Next check after: Wed Feb 20 07:38:54 2019
  Lifetime writes:  7381 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:   inode blocks
  FS Error count:   210
  First error time: Fri Aug 24 07:40:51 2018
  First error function: ext4_validate_block_bitmap
  First error line #:   376
  First error inode #:  0
  First error block #:  0
  Last error time:  Sun Aug 26 19:35:16 2018
  Last error function:  ext4_remount
  Last error line #:4833
  Last error inode #:   0
  Last error block #:   0

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

[Kernel-packages] [Bug 1773024] Re: Errors at boot

2018-08-26 Thread Stefan Pappalardo

I can confirm the issue with freshly installed Ubuntu Server 18.04.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

$ sudo apt-cache policy linux-image-4.15.0-33-generic 
linux-image-4.15.0-33-generic:
  Installiert:   4.15.0-33.36
  Installationskandidat: 4.15.0-33.36
  Versionstabelle:
 *** 4.15.0-33.36 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Errors at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  LOGS DMESG:

  [0.048089] ACPI: Added _OSI(Module Device)
  [0.048090] ACPI: Added _OSI(Processor Device)
  [0.048091] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.048091] ACPI: Added _OSI(Processor Aggregator Device)
  [0.049587] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049598] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049607] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049615] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049676] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049684] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049692] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049700] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049760] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049768] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049776] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049783] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049843] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049851] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049859] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049867] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049925] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049933] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049941] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049948] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050008] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050016] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050024] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050032] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050091] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050099] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050107] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050115] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050173] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050181] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050190] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050198] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050258] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050267] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050274] ACPI Exception: Could not find/resolve named package element: 
LNKB

[Kernel-packages] [Bug 1789145] [NEW] Microphone cannot be detected with front panel audio combo jack on HP Z8-G4 machine

2018-08-26 Thread Hui Wang

Public bug reported:

Steps to reproduce: Plug 3-ring headset to front audio jack.

Expected result: Microphone of headset could be detected

Actual result: Microphone is not detected

Failure rate: 100%

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1783289 stella

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Tags added: originate-from-1783289 stella

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

Title:
  Microphone cannot be detected with front panel audio combo jack on HP
  Z8-G4 machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce: Plug 3-ring headset to front audio jack.

  Expected result: Microphone of headset could be detected

  Actual result: Microphone is not detected

  Failure rate: 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789145/+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

[Kernel-packages] [Bug 1789145] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1789145

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1789145

Title:
  Microphone cannot be detected with front panel audio combo jack on HP
  Z8-G4 machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce: Plug 3-ring headset to front audio jack.

  Expected result: Microphone of headset could be detected

  Actual result: Microphone is not detected

  Failure rate: 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789145/+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

[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

2018-08-26 Thread og11

Here's the syslog from today. Had another drop network connection
episode around around 9:40pm. same behaviour. Works Ok most of the day,
often for a day or two, though the download speed on the speedtests is
no where near where it should be (that's my indication that something is
not configured right, I've never seen this before). Upload speed on the
speedtests is fine though. I have to disable and then re-enable the
ethernet interface to get the internet connection back when I notice
there is no connectivity to the internet via a browser.

** Attachment added: "syslog"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+attachment/5181105/+files/syslog

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

Title:
Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
keeps Dropping Internet Connection

Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete

Bug description:
I've turned up many, many new server and workstation systems over the
years on both Linux and Windows. Never seen anything like this
behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
lose Internet connectivity while using a browser. Ethernet interfaces
usually either work or they don't work.

I've configured the Intel I219-V Ethernet interface (wired Ethernet
connection, there is no wifi on this system) using the e1000e driver
for Ubuntu. The Ethernet connection is configured to use
NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock
Z370m Pro4 motherboard.

The Ethernet interface will drop the Internet connectivity when I'm
using either the Firefox or Chrome browser. It usually happens when
I'm using the search features of the browser. I can't figure out what
would cause this type of behaviour. When the Internet connection
drops, the only way to get back Internet connectivity is to disconnect
the wired connection using the Ubuntu features and then re-connect
(this restarts the NetworkManager service I notice).

In the NetworkManager logs I do notice an "auth" error about a file or
directory not found. I've never seen that before.

Note: The auth error does not coincide with the loss of Internet
connectivity, but it does proceed it. Often there can be many hours
between the auth error and the actual loss of Internet connectivity.

After I reconnect the connection (via re-starting the NetworkManager
service) all will be fine for up to a day or so, but then I stress
test it with a bunch of searches using the browser and usually I can
get the Internet connectivity to drop again. Repeat the disconnect
and reconnect process again (aka re-start NetworkManager) and the
Internet connectivity will be fine again. The longest I've seen it go
without an "Internet connectivity drop" issue is about 36 hours.

I notice that the e1000e driver does not list the I219-V as a
supported Ethernet interface in the Intel documentation for the Linux
version of the driver. I'm not sure why that is. The I219-V is
supposed to used another driver, but it's not clear there's a Linux
version for of the driver for the I219-V.

I'm really disappointed that I've run into this issue with Ubuntu
Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my
standard server OS, a great Linux distro) on this same motherboard for
a week with no issues, so I know the motherboard and the I219-V
Ethernet interface are 100% good hardware wise and can work properly.
CentOS 7.4 uses NetworkManager as the default for managing the
Ethernet interface.

The only reason I'm using Ubuntu Server 18.04 on this motherboard is
because of a specific package that Ubuntu has a newer packaged version
than CentOS. CentOS is extremely stable when it comes to basic server
functionality.

Hopefully, this bug with the I219-V Ethernet interface using the
e1000e drive for Linux can be verified and a fix rolled out.

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

[Kernel-packages] [Bug 1789145] Re: Microphone cannot be detected with front panel audio combo jack on HP Z8-G4 machine

2018-08-26 Thread Hui Wang

** Description changed:

- Steps to reproduce: Plug 3-ring headset to front audio jack.
  
- Expected result: Microphone of headset could be detected
+ [Impact]
+ This bug comes from OEM cert project of HP, the front mic jack can't detect
+ any plug/unplug, and we can't record any sound from plugged mic. This is a
+ block for OEM project.
  
- Actual result: Microphone is not detected
+ [Fix]
+ The fix comes from Realtek, it is said that this is a power issue, after 
changing
+ the capability of the pin of linein, the power will keep being on for both 
linein
+ and front mic, then this issue is fixed.
  
- Failure rate: 100%
+ [Test Case]
+ We tested plug/unplug detection and record through iphone/nokia type 
headset-mic,
+ all worked well.
+ 
+ [Regression Potential]
+ none, this is new added quirk, and only apply to the specific machine.

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

Title:
  Microphone cannot be detected with front panel audio combo jack on HP
  Z8-G4 machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  [Impact]
  This bug comes from OEM cert project of HP, the front mic jack can't detect
  any plug/unplug, and we can't record any sound from plugged mic. This is a
  block for OEM project.

  [Fix]
  The fix comes from Realtek, it is said that this is a power issue, after 
changing
  the capability of the pin of linein, the power will keep being on for both 
linein
  and front mic, then this issue is fixed.

  [Test Case]
  We tested plug/unplug detection and record through iphone/nokia type 
headset-mic,
  all worked well.

  [Regression Potential]
  none, this is new added quirk, and only apply to the specific machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789145/+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

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

2018-08-26 Thread milton hagler

Same issue with a Lenovo T480s with Intel graphics. Blank screen upon
resume after suspend. Mouse cursor works, can CTL+ALT+F1 to a command
prompt. Was working properly until last week, but had this issue 2 times
over 2 days. Machine is routinely kept up to date.

Hardware:
Intel(R) Core(TM) i7-8650U
Integrated Intel® UHD Graphics 620
1 TB PCIe SSD

uname -r:
4.15.0-33-generic

OS:
Kubuntu 18.04 
plasmashell 5.12.6

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Systems with acpi-lpss can't do S3/S4 on Bionic.

  [Test]
  Users confirmed these patches work for them.

  [Fix]
  Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system
  sleep handling) applies quirks for both runtime and system suspend.
  This causes problems for some systems, so avoid using quirks on S3 and
  S4.

  [Regression Potential]
  Low. These patches are in upstream stable, and it brings back driver's
  old behavior.

  ===Original Bug Report===
  I have installed Kubuntu 18.04 on 3 different machines (my friend's and my 
own) with no suspend problems but my HP Pavilion 11 x360 does not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  Correct behaviour is -

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  What happens -

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  Checking the logs suggests that the machine believes it is in suspend
  mode sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

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

[Kernel-packages] [Bug 1789050] [NEW] package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

You have been subscribed to a public bug:

will auf 16.04.5 LTS Upgrade machen habe 14.04 linux-firmware hat er
nicht installiert

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.20
ProcVersionSignature: Ubuntu 3.13.0-157.207-generic 3.13.11-ckt39
Uname: Linux 3.13.0-157-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sat Aug 25 22:33:52 2018
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-06-30 (56 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: initramfs-tools
Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-08-25 (0 days ago)

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial
-- 
package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/1789050
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware in Ubuntu.

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

[Kernel-packages] [Bug 1788786] Re: installation of nvidia-396 fails due to "trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvid

It sounds like the "nvidia-396" package from that PPA is broken. Please
use 'ppa-purge' to remove the PPA from your system.

Also, sorry that package isn't from the Ubuntu archive so we can't
support it here.

** Package changed: nvidia-graphics-drivers-375 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu.
https://bugs.launchpad.net/bugs/1788786

Title:
  installation of nvidia-396 fails due to "trying to overwrite
  '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also
  in package xserver-xorg-video-nvidia-390 390.48-0ubuntu3"

Status in Ubuntu:
  Invalid

Bug description:
  Installation of `nvidia-396` after `sudo add-apt-repository ppa
  :graphics-drivers/ppa` on Ubuntu 18.04 fails due to

  ```
  > sudo apt-get install -f nvidia-driver-396
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 
libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 
libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 
libnvidia-fbc1-396:i386
    libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 
libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 
nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime nvidia-settings
    nvidia-utils-396 screen-resolution-extra xserver-xorg-video-nvidia-396
  The following packages will be REMOVED:
    libnvidia-cfg1-390 libnvidia-compute-390 libnvidia-compute-390:i386 
xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
    libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 
libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 
libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 
libnvidia-fbc1-396:i386
    libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 
libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 
nvidia-driver-396 nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime
    nvidia-settings nvidia-utils-396 screen-resolution-extra 
xserver-xorg-video-nvidia-396
  0 upgraded, 25 newly installed, 4 to remove and 1 not upgraded.
  Need to get 0 B/88,1 MB of archives.
  After this operation, 224 MB of additional disk space will be used.
  Do you want to continue? [J/n] j
  (Reading database ... 748099 files and directories currently installed.)
  Preparing to unpack 
.../xserver-xorg-video-nvidia-396_396.54-0ubuntu0~gpu18.04.1_amd64.deb ...
  Unpacking xserver-xorg-video-nvidia-396 (396.54-0ubuntu0~gpu18.04.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/xserver-xorg-video-nvidia-396_396.54-0ubuntu0~gpu18.04.1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', 
which is also in package xserver-xorg-video-nvidia-390 390.48-0ubuntu3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/var/cache/apt/archives/xserver-xorg-video-nvidia-396_396.54-0ubuntu0~gpu18.04.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

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

[Kernel-packages] [Bug 1736828] Re: package linux-firmware 1.157.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1736828

Title:
  package linux-firmware 1.157.14 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  no

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.14
  ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Wed Dec  6 20:20:20 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-12-05 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.14 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kernel-packages] [Bug 1663568] Re: installed post-installation script returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1663568

Title:
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  /home/budda/software# apt-get dist-upgrade -y
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  2 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: deferring update (trigger activated)
  Setting up linux-firmware (1.157.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
  cp: cannot stat '/usr/share/plymouth/themes/details': No such file or 
directory
  E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-62-generic with 1.
  dpkg: error processing package linux-firmware (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
  cp: cannot stat '/usr/share/plymouth/themes/details': No such file or 
directory
  E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-62-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   linux-firmware
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

[Kernel-packages] [Bug 1659813] Re: subprocess installed post-removal script returned error exit status 1

*** This bug is a duplicate of bug 1659812 ***
https://bugs.launchpad.net/bugs/1659812

** This bug has been marked a duplicate of bug 1659812
   subprocess installed post-removal script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1659813

Title:
  subprocess installed post-removal script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  i cant download application from software center

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

[Kernel-packages] [Bug 1787228] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1787228

Title:
  package linux-firmware 1.173.1 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  Just an upgrade from 16.04.5 to 18.04(.1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.1
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Aug 15 16:54:17 2018
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-07-08 (1133 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.173.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago)

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

[Kernel-packages] [Bug 1782869] Re: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1782869

Title:
  package linux-firmware 1.157.20 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Sometimes, network card is not working and getting crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.20
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Jul 16 23:14:16 2018
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-03-02 (140 days ago)

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

[Kernel-packages] [Bug 1659812] Re: subprocess installed post-removal script returned error exit status 1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!


** Package changed: linux-firmware (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1659812

Title:
  subprocess installed post-removal script returned error exit status 1

Status in Ubuntu:
  Incomplete

Bug description:
  i cant download application from software center

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

[Kernel-packages] [Bug 1780740] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1780740

Title:
  package linux-firmware 1.173.1 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  This is an overall error with the initrd image, not sure what is going
  on or how to fix it.  I suspect somewhere it's getting the wrong
  information about the distribution that I am using.  I just don't know
  enough to debug it. :(

  ---
  $ df -ha | grep /boot
  /dev/sda199M   30M   70M  30% /boot/efi

  
  $ df -h /boot
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdc3   198G   33G  155G  18% /

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  
  ---
  Full Error:

  Processing triggers for linux-image-4.15.0-23-generic (4.15.0-23.25) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
  /etc/kernel/postinst.d/zz-runlilo:
  Warning: /dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S3NYNF0JA23675B is not 
on the first disk
  Fatal: open /boot/vmlinuz-4.13.0-39-generic.efi.signed: No such file or 
directory
  run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
  dpkg: error processing package linux-image-4.15.0-23-generic (--configure):
   installed linux-image-4.15.0-23-generic package post-installation script 
subprocess returned error exit status 1
  Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
  Warning: /dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S3NYNF0JA23675B is not 
on the first disk
  Fatal: open /boot/vmlinuz-4.13.0-39-generic.efi.signed: No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   linux-firmware
   linux-image-4.15.0-23-generic
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ---

  Happy to provide more information.  It's not really causing any
  problems yet, just when I do an update I am getting the error at the
  end.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jul  9 18:00:25 2018
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-03-24 (107 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.173.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (72 days ago)

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

[Kernel-packages] [Bug 1787452] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1787452

Title:
  package linux-firmware 1.173.1 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  package linux-firmware 1.173.1 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.1
  ProcVersionSignature: Ubuntu 4.4.0-132.158-generic 4.4.140
  Uname: Linux 4.4.0-132-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Thu Aug 16 17:34:34 2018
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-03-05 (1260 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.173.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kernel-packages] [Bug 1673083] Re: package linux-firmware 1.157.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags added: bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1673083

Title:
  package linux-firmware 1.157.8 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Was performing an upgrade, when I try to log into the Desktop the
  problem error pops up and it instructs me to report it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.8
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue Mar  7 16:25:21 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (219 days ago)

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

[Kernel-packages] [Bug 1789050] Re: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

*** This bug is a duplicate of bug 1673083 ***
https://bugs.launchpad.net/bugs/1673083

** Package changed: initramfs-tools (Ubuntu) => linux-firmware (Ubuntu)

** This bug has been marked a duplicate of bug 1673083
   package linux-firmware 1.157.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1789050

Title:
  package linux-firmware 1.157.20 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  will auf 16.04.5 LTS Upgrade machen habe 14.04 linux-firmware hat er
  nicht installiert

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.20
  ProcVersionSignature: Ubuntu 3.13.0-157.207-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-157-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Aug 25 22:33:52 2018
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-30 (56 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-08-25 (0 days ago)

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

[Kernel-packages] [Bug 1787887] Re: CC_STACKPROTECTOR_STRONG is needed for Trusty 4.4

2018-08-26 Thread Po-Hsu Lin

As this kernel will be built with Trusty (gcc 4.8), the flag -fstack-
protector-strong is not available there.

This might need to be fixed in the qrt test suite.

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

Title:
  CC_STACKPROTECTOR_STRONG is needed for Trusty 4.4

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  443.  ==
  444.  FAIL: test_185_config_stack_protector_strong 
(__main__.KernelSecurityConfigTest)
  445.  CONFIG_CC_STACKPROTECTOR_STRONG set
  446.  --
  447.  Traceback (most recent call last):
  448.  File "./test-kernel-security.py", line 2350, in 
test_185_config_stack_protector_strong
  449.  self.assertKernelConfig(config_option, expected)
  450.  File "./test-kernel-security.py", line 207, in assertKernelConfig
  451.  self.assertKernelConfigSet(name)
  452.  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  453.  '%s option was expected to be set in the kernel config' % name)
  454.  AssertionError: CC_STACKPROTECTOR_STRONG option was expected to be set 
in the kernel config
  455.  
  456.  --
  457.  Ran 99 tests in 65.463s

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1787887/+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

[Kernel-packages] [Bug 1762989] Re: Display Port issues - screen blackouts

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Display Port issues - screen blackouts

Status in linux package in Ubuntu:
  Expired

Bug description:
  I use a Philips BDM4037U 40'', 4k monitor.
  Connecting it via DP to my Lenovo 910 4k gives me random blackouts.

  It appears to me that this mostly happens after some time of work,
  also more likely when the CPU has to handle more than average load,
  sooner in 30Hz than in 60Hz mode. But it happens for sure after some
  time, each day.

  I was unsure if this is a problem with the monitor itself (although when 
connected via HDMI this isn't an issue).
  I found similar bug reports for Windows, where it was suggested to update the 
firmware.
  My laptop has updated everything - a current BIOS (which dates back to June 
2017 or so), updated Windows, latest Ubuntu.
  The same problem existed in 17.10, with x-org and Wayland sessions.

  Note, there is another issue with this monitor filed by me, but
  unrelated AFAIK:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762986

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thet   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 12:07:06 2018
  HibernationDevice: RESUME=UUID=bedd1248-32dd-43ca-be9f-28337086ea86
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 80VF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=998520ff-c841-45ab-8312-2bb876ae2a0b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO

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

[Kernel-packages] [Bug 1729673] Re: Blacklist floppy module to increase boot performance

2018-08-26 Thread Po-Hsu Lin

** Changed in: linux-gcp (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1729673

Title:
  Blacklist floppy module to increase boot performance

Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-gcp source package in Xenial:
  Fix Released

Bug description:
  The floppy module tries to probe for a floppy device but fails. This
  adds on average 7 seconds of boot time to Ubuntu (all versions). It's
  a trivial fix to blacklist the module.

  $ echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf 
  $ sudo update-initramfs -u

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

[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending

2018-08-26 Thread Kai-Heng Feng

** Description changed:

+ ===SRU Justification===
+ [Impact]
+ r8169 failed to establish connection after the fix for LP: #1752772
+ landed.
+ 
+ [Fix]
+ Accepts BIOS WoL settings again, and disables MSI-X for certain chip
+ revisions.
+ 
+ [Test]
+ Users confirmed the fix worked for them.
+ 
+ [Regression Potential]
+ Low. This brings back the old behavior for both WoL and MSI.
+ 
+ ===Original Bug Report===
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  minihydra   2085 F pulseaudio
-  /dev/snd/controlC0:  minihydra   2085 F pulseaudio
-  /dev/snd/controlC1:  minihydra   2085 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  minihydra   2085 F pulseaudio
+  /dev/snd/controlC0:  minihydra   2085 F pulseaudio
+  /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jul  3 10:13:19 2018
  HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd
  InstallationDate: Installed on 2018-07-02 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
-  enp2s0no wireless extensions.
-  
-  lono wireless extensions.
+  enp2s0no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-24-generic N/A
-  linux-backports-modules-4.15.0-24-generic  N/A
-  linux-firmware 1.173.1
+  linux-restricted-modules-4.15.0-24-generic N/A
+  linux-backports-modules-4.15.0-24-generic  N/A
+  linux-firmware 1.173.1
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  r8169 no internet after suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 failed to establish connection after the fix for LP: #1752772
  landed.

  [Fix]
  Accepts BIOS WoL settings again, and disables MSI-X for certain chip
  revisions.

  [Test]
  Users confirmed the fix worked for them.

  [Regression Potential]
  Low. This brings back the old behavior for both WoL and MSI.

  ===Original Bug Report===
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  minihydra   2085 F pulseaudio
   /dev/snd/controlC0:  minihydra   2085 F pulseaudio
   /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tu

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-08-26 Thread Kai-Heng Feng

Please try this kernel for Bionic:
https://people.canonical.com/~khfeng/lp1745032-bionic/

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Kernel-packages] [Bug 1778851] Re: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: installed linux-headers-4.15.0-23-generic package post-installation script subproces

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: installed linux-headers-4.15.0-23-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've done update to 18.04 from 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kan1695 F pulseaudio
  Date: Wed Jun 27 07:54:34 2018
  ErrorMessage: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2017-09-19 (281 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=9dca5be7-8f3d-4249-90e0-b2058e40d97d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: installed linux-headers-4.15.0-23-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-06-27 (0 days ago)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.4
  dmi.board.name: 07T996
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.4:bd01/31/2018:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn07T996:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1788782] [NEW] Ubuntu 16.04.03(P8/Tuleta): SEGV-panic in smp_send_reschedule(). Machine keeps rebooting with oops message even after reboot.