[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Mark]

This still looks like the getrandom() hang described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572. This was
caused by the fix in the kernel for CVE-2018-1108. Two complementary
fixes have been discussed in the Debian bug neither of which modify the
kernel. The first is a change to the Plymouth package to avoid
fontconfig generating uuids, which reportedly has the added bonus of
speeding up boot compared to pre-CVE-fix times. The second is a change
to randutils in the utils-linux package so they don't block on
getrandom().

There's a link to the updated plymouth package which I tried:

https://packages.debian.org/sid/amd64/plymouth/download

Unfortunately all I got was a black screen, with or without haveged
installed. This is not the getrandom hang. The screen remains black and
no log is displayed. I suspect this is because some modification to the
package or config files is needed for Ubuntu. Or maybe some other
package needed reconfiguring due to the change plymouth. I'm no Ubuntu
expert.

As I stated in comment #48, if these fixes indeed work, when properly
incorporated into Ubuntu, they are preferable to backing out the CVE
fix.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

Re: [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

[Peter Tsiampas]

Thank you for that, I don't need lillo and have removed it.

*Peter Tsiampas* | Architect/Developer | Melbourne, Australia
Mobile: +61 433 322 100 | Web: peter.tsiampas.com | LinkedIn:
http://www.linkedin.com/in/petertsiampas
Social:google.com/+PeterTsiampas | Email: pe...@tsiampas.com

On 9 July 2018 at 22:18, Seth Forshee 
wrote:

> The failure comes from a lilo post-installation script:
>
>   run-parts: /etc/initramfs/post-update.d//runlilo exited with return
> code 1
>
> Likely you don't need lilo and can remove the package. If you really do
> need it then this bug should be against lilo and not linux-firmware.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

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

[Kernel-packages] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

[Daniel van Vugt]

Thanks for the link.

It appears your crash occurred in the nvidia graphics driver (version
390):

Xorg (7) /lib/x86_64-linux-gnu/libgcc_s.so.1+11ba4 → /lib/x86_64-linux-
gnu/libc-2.27.so+165f21 → /lib/x86_64-linux-gnu/libgcc_s.so.1+12da5 →
/lib/x86_64-linux-gnu/libgcc_s.so.1+f373 → /lib/x86_64-linux-
gnu/libgcc_s.so.1+10550 → /lib/x86_64-linux-gnu/libgcc_s.so.1+1138c →
/lib/x86_64-linux-gnu/libc-2.27.so+131168 → /usr/lib/xorg/Xorg+1b88ad →
/usr/lib/xorg/Xorg+1bc649 → /lib/x86_64-linux-
gnu/libpthread-2.27.so+12890 → /lib/x86_64-linux-gnu/ld-2.27.so+fe47 →
/lib/x86_64-linux-gnu/ld-2.27.so+1770a →
/usr/lib/xorg/modules/libwfb.so+25597 → /usr/lib/x86_64-linux-
gnu/nvidia/xorg/nvidia_drv.so+60a46c → [heap]+d35cb0

That's something which isn't open source but hopefully a future update
from Nvidia will resolve it.

If the cause of the crash is in the open source parts of that stack
trace, we can't tell, unfortunately.

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Tags added: nvidia

** Summary changed:

- Xorg crashes after system sleep / wakeup
+ [nvidia] Xorg crashes after system sleep / wakeup

** Summary changed:

- [nvidia] Xorg crashes after system sleep / wakeup
+ [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → 
nvidia_drv.so+60a46c → [heap]+d35cb0

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

Title:
  [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597
  → nvidia_drv.so+60a46c → [heap]+d35cb0

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  after putting the system to sleep, and waking it up, Xorg crashes, and
  I'm lead to a new greeter / login screen. naturally the state of my
  desktop is lost in this process, and I'm stuck with a new login with
  no apps running.

  the error reporter says:

  Error: [Errno 21] is a directory:
  '/proc/driver/nvidia/gpus/:01:00.0/'

  which is indeed true:

  $ ls /proc/driver/nvidia/gpus/\:01\:00.0/
  information  registry

  the same system worked fine with ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 07:51:42 2018
  DistUpgraded: 2018-05-04 09:38:04,874 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.13.0-39-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 680] [3842:3687]
  InstallationDate: Installed on 2016-04-03 (764 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e56cb504-229d-4c7a-b16c-b259d05e992b ro noprompt quiet splash 
vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (3 days ago)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by 

[Kernel-packages] [Bug 1760508] Re: system hang

[Launchpad Bug Tracker]

[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/1760508

Title:
  system hang

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Xenial:
  Expired

Bug description:
  The system hangs when I ask it to print, and I can't get it to panic
  and dump.  Keyboard sysrq doesn't seem to do anything, nor does
  waiting 15 minutes.  Using the text console makes no difference
  either.  Memtest shows no errors.  When I boot 4.4.0-112 kernel
  there's no problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbw1945 F pulseaudio
   /dev/snd/controlC1:  dbw1945 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Apr  1 19:16:11 2018
  HibernationDevice: RESUME=UUID=94c6940e-4c23-4002-960a-45e56867ea6d
  InstallationDate: Installed on 2016-05-06 (695 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=d0cf2d81-4dbf-4a5a-b898-285e3c3fdd8b ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/11/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu Xenial)
   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/1760508

Title:
  system hang

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Xenial:
  Expired

Bug description:
  The system hangs when I ask it to print, and I can't get it to panic
  and dump.  Keyboard sysrq doesn't seem to do anything, nor does
  waiting 15 minutes.  Using the text console makes no difference
  either.  Memtest shows no errors.  When I boot 4.4.0-112 kernel
  there's no problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dbw1945 F pulseaudio
   /dev/snd/controlC1:  dbw1945 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Apr  1 19:16:11 2018
  HibernationDevice: RESUME=UUID=94c6940e-4c23-4002-960a-45e56867ea6d
  InstallationDate: Installed on 2016-05-06 (695 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=d0cf2d81-4dbf-4a5a-b898-285e3c3fdd8b ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/11/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760508/+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 1770291] Re: Monitor becomes unknown/undetected/low resolution

[Launchpad Bug Tracker]

[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/1770291

Title:
  Monitor becomes unknown/undetected/low resolution

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

Bug description:
  reverting to 4.15.0-15 resolves issue.

  Same problem regardless of recommended or legacy nvidia drivers or
  open software.

  4.15.0-15:
  $ inxi -G
  Graphics:  Card: NVIDIA GT218 [GeForce 210]
 Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: 
fbdev,vesa)
 Resolution: 1280x1024@75.02hz
 GLX Renderer: NVA8 GLX Version: 3.0 Mesa 17.2.8

  Monitor Dell 1907FPf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770291/+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 1770178] Re: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

[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/1770178

Title:
  package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  I came in this morning, and the bug reporter tool was complaining
  about this.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u388mw 2403 F pulseaudio
   /dev/snd/controlC0:  u388mw 2403 F pulseaudio
  Date: Wed May  9 06:30:24 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=2cfbf33c-ccf2-4fa0-95fd-c3242e7ca36a
  InstallationDate: Installed on 2018-02-12 (85 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Synergio System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-122-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LE/CSM
  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.:bvr0805:bd12/23/2011:svnSynergio:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLE/CSM:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: Synergio

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770178/+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 1770291] Re: Monitor becomes unknown/undetected/low resolution

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu Bionic)
   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/1770291

Title:
  Monitor becomes unknown/undetected/low resolution

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

Bug description:
  reverting to 4.15.0-15 resolves issue.

  Same problem regardless of recommended or legacy nvidia drivers or
  open software.

  4.15.0-15:
  $ inxi -G
  Graphics:  Card: NVIDIA GT218 [GeForce 210]
 Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: 
fbdev,vesa)
 Resolution: 1280x1024@75.02hz
 GLX Renderer: NVA8 GLX Version: 3.0 Mesa 17.2.8

  Monitor Dell 1907FPf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770291/+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 1770357] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned

[Launchpad Bug Tracker]

[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/1770357

Title:
  package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to
  install/upgrade: installed linux-image-4.15.0-20-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Nvidia drivers installation not able to identify kernel headers.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: rfcomm bnep 8250_dw intel_rapl x86_pkg_temp_thermal 
uvcvideo intel_powerclamp coretemp videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_core videodev media snd_soc_skl snd_soc_skl_ipc 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc btusb snd_soc_acpi btrtl 
snd_soc_core btbcm snd_hda_codec_hdmi snd_hda_codec_conexant 
snd_hda_codec_generic btintel iwlmvm hid_sensor_magn_3d mac80211 ac97_bus 
intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec bluetooth snd_hda_core 
hid_sensor_als wmi_bmof intel_wmi_thunderbolt hid_sensor_accel_3d 
hid_sensor_gyro_3d iwlwifi hid_sensor_trigger cfg80211 
industrialio_triggered_buffer kfifo_buf thinkpad_acpi hid_sensor_iio_common 
industrialio mei_me mei shpchp idma64 virt_dma intel_lpss_pci intel_pch_thermal 
intel_lpss tpm_crb mac_hid wacom hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 sdhci_pci sdhci intel_ish_ipc intel_ishtp wmi i2c_hid 
pinctrl_sunrisepoint
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 11:44:53 2018
  ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-04-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to 
install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal 
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/+bug/1770357/+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 1780893] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw had been previously installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-124-generic 4.4.0-124.148
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-124-generic:4.4.0-124.148
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
  InstallationDate: Installed on 2015-09-22 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780893/+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 1780894] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw have previously been installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-112-generic:4.4.0-112.135
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
  InstallationDate: Installed on 2015-09-22 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780894/+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 1691817] Re: ubuntu 17.04 lpfc fix.

[Po-Hsu Lin]

Hi Laurie,
Thanks for the info!

It looks like bug 1768103 has been fixed and
7e04e21afa82ef024416f5413b5bdb66e0505bcd has landed in the bionic-kernel
as well.

So for this one, it's asking for commit 7e04e21af to land in other
kernels?

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

Title:
  ubuntu 17.04 lpfc fix.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Can someone from ubuntu check the 17.04 lpfc sources and make sure that this 
fix is in?
7e04e21afa82ef024416f5413b5bdb66e0505bcd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691817/+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 1780893] Re: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[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/1780893

Title:
  package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw had been previously installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-124-generic 4.4.0-124.148
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-124-generic:4.4.0-124.148
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
  InstallationDate: Installed on 2015-09-22 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780893/+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 1780894] Re: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[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/1780894

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw have previously been installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-112-generic:4.4.0-112.135
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
  InstallationDate: Installed on 2015-09-22 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780894/+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 1780894] [NEW] package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Randy Bass]

Public bug reported:

I was trying to install Libreoffice Base. Libreoffice writer, calc, and
draw have previously been installed and used extensively.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-112-generic 4.4.0-112.135
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  randy  1991 F pulseaudio
 /dev/snd/controlC0:  randy  1991 F pulseaudio
Date: Mon Jul  9 20:13:27 2018
DpkgHistoryLog:
 Start-Date: 2018-07-09  20:13:19
 Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
 Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
DuplicateSignature:
 package:linux-image-4.4.0-112-generic:4.4.0-112.135
 Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
 Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
 dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
InstallationDate: Installed on 2015-09-22 (1021 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
MachineType: Dell Inc. OptiPlex 780
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0C27VV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw have previously been installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-112-generic:4.4.0-112.135
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: 

[Kernel-packages] [Bug 1780893] [NEW] package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Randy Bass]

Public bug reported:

I was trying to install Libreoffice Base. Libreoffice writer, calc, and
draw had been previously installed and used extensively.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-124-generic 4.4.0-124.148
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  randy  1991 F pulseaudio
 /dev/snd/controlC0:  randy  1991 F pulseaudio
Date: Mon Jul  9 20:13:27 2018
DpkgHistoryLog:
 Start-Date: 2018-07-09  20:13:19
 Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
 Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
DuplicateSignature:
 package:linux-image-4.4.0-124-generic:4.4.0-124.148
 Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
 Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
 dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=7f28c03f-cc04-4d1c-9d1d-f3ce2dbe4fea
InstallationDate: Installed on 2015-09-22 (1021 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
MachineType: Dell Inc. OptiPlex 780
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic 
root=/dev/mapper/vg_ubu-h4_ubu_root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0C27VV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-4.4.0-124-generic 4.4.0-124.148 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  New

Bug description:
  I was trying to install Libreoffice Base. Libreoffice writer, calc,
  and draw had been previously installed and used extensively.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-124-generic 4.4.0-124.148
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  randy  1991 F pulseaudio
   /dev/snd/controlC0:  randy  1991 F pulseaudio
  Date: Mon Jul  9 20:13:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-07-09  20:13:19
   Commandline: aptdaemon role='role-commit-packages' sender=':1.67'
   Install: libhsqldb1.8.0-java:i386 (1.8.0.10+dfsg-6, automatic), 
libservlet3.1-java:i386 (8.0.32-1ubuntu1.6, automatic), 
libreoffice-java-common:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base:i386 (1:5.1.6~rc2-0ubuntu1~xenial3), 
libreoffice-sdbc-firebird:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-sdbc-hsqldb:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic), 
libreoffice-base-drivers:i386 (1:5.1.6~rc2-0ubuntu1~xenial3, automatic)
  DuplicateSignature:
   package:linux-image-4.4.0-124-generic:4.4.0-124.148
   Setting up linux-image-4.4.0-112-generic (4.4.0-112.135) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-112-generic)
   dpkg: error processing package linux-image-4.4.0-112-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: 

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

[Po-Hsu Lin]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1768103

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  == SRU Justification ==
  It was reported by Broadcom that an early asic model (A0) of their 16/32GB
  HBA's doesn't boot with the lpfc driver in Ubuntu 18.04.

  Bionic with the lpfc driver 12.0.0.0 can't see LPe16002-M6 but can see
  LPe16002B-M6.

  This bug is fixed by commits bf316c78517d and c221768bd49a, which are
  both still in linux-next.  Broadcom tested with this two commits and
  confirmed they resolve the bug and allow the system to boot.

  == Fixes ==
  Currently in linux-next:
  bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")
  c221768bd49a ("scsi: lpfc: Fix 16gb hbas failing cq create.")

  == Regression Potential ==
  Low.  Patches fix a current regression and are limited to lpfc.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update.

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+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 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven)

[Bug Watch Updater]

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=200087.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-06-16T04:43:34+00:00 bakarichard91 wrote:

Created attachment 276583
dmesg after starting kernel with pci=noacpi

This is a brand new notebook on the market with Ryzen 5/Radeon. With
disabled ACPI kernel boots without any problem but my notebook produces
more heat than on Win10. Otherwise this happens when it is stayed on the
bios screen in a while.

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/13


On 2018-06-16T04:51:39+00:00 bakarichard91 wrote:

CPU: AMD Ryzen 5 2500U
GPU1: AMD Radeon Vega 8
GPU2: AMD Radeon 535

(I wrote to Acer to fix their bios problems but they said Linux is not
supported. I don't think they are right but what can I do?)

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/14


On 2018-06-16T04:53:11+00:00 erik.schmauss wrote:

Created attachment 276585
attachment-31427-0.html

Out of office 6/18-6/27

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/15


On 2018-06-16T04:54:10+00:00 bakarichard91 wrote:

Created attachment 276587
Soft lockup failure without noacpi

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/16


On 2018-06-16T05:07:17+00:00 bakarichard91 wrote:

Nothing changes with disabled iommu.

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/17


On 2018-06-16T05:49:32+00:00 bakarichard91 wrote:

Created attachment 276589
dmesg after amd_iommu_dump=1

[0.00] AMD-Vi: Using IVHD type 0x11
[0.00] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: b0 info 
[0.00] AMD-Vi:mmio-addr: fd90
[0.00] AMD-Vi:   DEV_SELECT_RANGE_START  devid: 00:01.0 flags: 00
[0.00] AMD-Vi:   DEV_RANGE_END   devid: ff:1f.6
[0.00] AMD-Vi:   DEV_ALIAS_RANGE devid: ff:00.0 flags: 
00 devid_to: 00:14.4
[0.00] AMD-Vi:   DEV_RANGE_END   devid: ff:1f.7
[0.00] AMD-Vi:   DEV_SPECIAL(HPET[0])   devid: 00:14.0
[0.00] AMD-Vi:   DEV_SPECIAL(IOAPIC[33])devid: 00:14.0
[0.00] AMD-Vi:   DEV_SPECIAL(IOAPIC[34])devid: 00:00.1
[0.00] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/19


On 2018-06-16T07:34:30+00:00 bakarichard91 wrote:

Created attachment 276591
Error message before freezing (without quite splash)

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/20


On 2018-06-29T23:43:58+00:00 erik.schmauss wrote:

Please try booting with linux 4.18-rc1 or later. Also, please try
4.18-rc1+ with/without ACPI

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/21


On 2018-06-30T02:22:38+00:00 bakarichard91 wrote:

Hi Erik,

Absolutely the same thing on 4.18rc1 and on rc2 too.

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/22


On 2018-06-30T03:20:02+00:00 bakarichard91 wrote:

Fedora loads without any additional parameters(mysterious).

[0.00] Switched APIC routing to physical flat.
[0.002000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[0.007000] tsc: Fast TSC calibration using PIT
[0.008000] tsc: Detected 1996.299 MHz processor
[0.008000] clocksource: tsc-early: mask: 0x max_cycles: 
0x398d0c7513b, max_idle_ns: 881590744042 ns
[0.008000] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 3992.59 BogoMIPS (lpj=1996299)

Heat production may be still present but I can't measure it because
there is no temperature values in "sensors" (there is 5 values in
Win10).

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/23


On 2018-06-30T03:21:12+00:00 bakarichard91 wrote:

Created attachment 277069
Fedora loads without noacpi

Reply at: https://bugs.launchpad.net/amd/+bug/1776563/comments/24

[Kernel-packages] [Bug 1780759] Re: nvidia-kernel-source-390 390.48-0ubuntu3: nvidia kernel module failed to build [cc crashed with {standard input}: Internal error (Ошибка сегментирования).]

[Daniel van Vugt]

It appears it's your compiler that crashed when updating the Nvidia
driver. Not a bug in the driver itself. Reassigning to the compiler.

** Summary changed:

- nvidia-kernel-source-390 390.48-0ubuntu3: nvidia kernel module failed to build
+ nvidia-kernel-source-390 390.48-0ubuntu3: nvidia kernel module failed to 
build [cc crashed with {standard input}: Internal error (Ошибка 
сегментирования).]

** Package changed: nvidia-graphics-drivers-390 (Ubuntu) => gcc-defaults
(Ubuntu)

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

Title:
  nvidia-kernel-source-390 390.48-0ubuntu3: nvidia kernel module failed
  to build [cc crashed with {standard input}: Internal error (Ошибка
  сегментирования).]

Status in gcc-defaults package in Ubuntu:
  New

Bug description:
  this is an automatic bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-source-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-24-generic
  Date: Mon Jul  2 17:10:25 2018
  Dependencies:
   
  InstallationDate: Installed on 2015-08-05 (1068 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageVersion: 390.48-0ubuntu3
  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.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.48-0ubuntu3: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1780759/+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 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[Daniel van Vugt]

Great. Thanks for figuring that out.

Was there any sign of corruption? Were you able to upgrade gdm3 to the
latest version again?

I wonder - if it happens again then please check:
  1. if your disk/partition is full (run: df -h); or
  2. if the disk has experienced any hardware errors (run the Disks app > 
burger menu > SMART Data & Self-Tests...).

If most other people here are experiencing bug 1779827 instead of this
then it is possible this bug was entirely unique to your machine.

** No longer affects: 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/1779476

Title:
  Ubuntu 18.04: gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+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 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

Yes that was released a few hours ago:
https://launchpad.net/ubuntu/+source/linux-firmware/1.157.20

George: as the original reporter can you confirm that today's update to
the 'linux-firmware' package has fixed it?

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

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

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

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics 

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

You can ignore comment #29 now. The proper official fix for 18.04 is:
https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1/+build/15084683

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1754396] Re: nvidia 390 driver creates unknown screen

[Paul White]

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

** Tags added: bionic

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

Title:
  nvidia 390 driver creates unknown screen

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  ubuntu 18.04 Laptop Samsung RF711 and Sony V7
  the nvidia driver creates an unknown screen and also opens it.

  I do not see a login window and a desktop
  I enter the password blind, I start the desktop and do not see him.
  with the right mouse button and background I can change the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1754396/+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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[DH]

#29 Fix confirmed on Ubuntu 18.04 on Miix 700 / Intel 8260

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1754396] [NEW] nvidia 390 driver creates unknown screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

ubuntu 18.04 Laptop Samsung RF711 and Sony V7
the nvidia driver creates an unknown screen and also opens it.

I do not see a login window and a desktop
I enter the password blind, I start the desktop and do not see him.
with the right mouse button and background I can change the screen.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
nvidia 390 driver creates unknown screen
https://bugs.launchpad.net/bugs/1754396
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-390 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 1764645] Re: Bluetooth not working

[Zero]

This is now working again for me as of Linux-Firmware 1.157.20 and
kernel 4.4.0.130.136 received today.

THANK YOU, THANK YOU, THANK YOU!!!

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

Title:
  Bluetooth not working

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  A regression was discovered in Bionic.  The regression was introduced by
  mainline commit f44cb4b19ed4, which then made it's way into Bionic in
  4.15.0-14 as commit c91729972ac6 via stable updates.

  This regression is fixed by mainline commit 803cdb8ce584.  Commit
  803cdb8ce584 was also cc'd to stable.  However, it has not landed in
  upstream stable 4.15 or Bionic.

  
  == Fix ==
  803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 
models")

  
  == Regression Potential ==
  Low.  This fix has also been cc'd to upstream stable, so it has had
  additonal upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
    Installato: 3.28.0-2
    Candidato:  3.28.0-2
    Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
     Soft blocked: no
     Hard blocked: no
  1: phy0: Wireless LAN
     Soft blocked: no
     Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
  Ethernet [1969:10a1] (rev 10)
  Bus 002 Device 002: ID 8087:8000 Intel Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   

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

[Ubuntu Kernel Bot]

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

Title:
  Upgrade ubuntu 14.04 to 16.04 crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When i am trying tu uipgarde from 14,04 to 16.04 (ubuntu)
  when the process starts, a crash occurs:
  first step {preparandola actualizacion} "preparing the update" runs ok.
  the process crash in the "second step" called {configurando nuevos canales de 
software} "configuring new software channels" with the error message {No se ha 
podido calcular la actualizacion} "enable to calculate the update" 
  the third possible cause is {paquetes no oficiales de software no 
proporcionados por ubuntu} "non-official packages don't provided for ubuntu" 
looks is my issue. I have disabled third part sources from the configuration, 
but there must be something else because it even does not work.
  Please help "all of us" with this issue to be able to upgrade to ubuntu 16.04 
(in order to go to ubuntu 18.04 already available)
  Thanks in advance.
  lsb_release -rd
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-153-generic 3.13.0-153.203
  ProcVersionSignature: Ubuntu 3.13.0-153.203-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-153-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juan   2042 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  9 18:33:25 2018
  HibernationDevice: RESUME=UUID=d636c2b9-ed1b-472f-93c6-12845c9560d1
  InstallationDate: Installed on 2016-02-09 (881 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: Dell Inc. Inspiron 1440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic 
root=UUID=3ec0f1ba-dc84-47b0-9fec-4595cd904f69 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-153-generic N/A
   linux-backports-modules-3.13.0-153-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2018-06-19 (20 days ago)
  dmi.bios.date: 07/29/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0K138P
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/29/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1440
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780880/+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 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Zero]

This is now working again as of Linux-Firmware 1.157.20 received today.

THANK YOU, THANK YOU, THANK YOU!!!

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in anticipation
  ---
  ApportVersion: 

[Kernel-packages] [Bug 1780880] [NEW] Upgrade ubuntu 14.04 to 16.04 crash

[Juan Manuel Carrillo Campos]

Public bug reported:

When i am trying tu uipgarde from 14,04 to 16.04 (ubuntu)
when the process starts, a crash occurs:
first step {preparandola actualizacion} "preparing the update" runs ok.
the process crash in the "second step" called {configurando nuevos canales de 
software} "configuring new software channels" with the error message {No se ha 
podido calcular la actualizacion} "enable to calculate the update" 
the third possible cause is {paquetes no oficiales de software no 
proporcionados por ubuntu} "non-official packages don't provided for ubuntu" 
looks is my issue. I have disabled third part sources from the configuration, 
but there must be something else because it even does not work.
Please help "all of us" with this issue to be able to upgrade to ubuntu 16.04 
(in order to go to ubuntu 18.04 already available)
Thanks in advance.
lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-153-generic 3.13.0-153.203
ProcVersionSignature: Ubuntu 3.13.0-153.203-generic 3.13.11-ckt39
Uname: Linux 3.13.0-153-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  juan   2042 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul  9 18:33:25 2018
HibernationDevice: RESUME=UUID=d636c2b9-ed1b-472f-93c6-12845c9560d1
InstallationDate: Installed on 2016-02-09 (881 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
MachineType: Dell Inc. Inspiron 1440
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic 
root=UUID=3ec0f1ba-dc84-47b0-9fec-4595cd904f69 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-153-generic N/A
 linux-backports-modules-3.13.0-153-generic  N/A
 linux-firmware  1.127.24
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2018-06-19 (20 days ago)
dmi.bios.date: 07/29/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0K138P
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/29/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1440
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 trusty

** Attachment added: "Message with the crash error"
   
https://bugs.launchpad.net/bugs/1780880/+attachment/5161689/+files/crash%20error%20when%20trying%20to%20upgrade%20to%20ubuntu%2016.04.png

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

Title:
  Upgrade ubuntu 14.04 to 16.04 crash

Status in linux package in Ubuntu:
  New

Bug description:
  When i am trying tu uipgarde from 14,04 to 16.04 (ubuntu)
  when the process starts, a crash occurs:
  first step {preparandola actualizacion} "preparing the update" runs ok.
  the process crash in the "second step" called {configurando nuevos canales de 
software} "configuring new software channels" with the error message {No se ha 
podido calcular la actualizacion} "enable to calculate the update" 
  the third possible cause is {paquetes no oficiales de software no 
proporcionados por ubuntu} "non-official packages don't provided for ubuntu" 
looks is my issue. I have disabled third part sources from the configuration, 
but there must be something else because it even does not work.
  Please help "all of us" with this issue to be able to upgrade to ubuntu 16.04 
(in order to go to ubuntu 18.04 already available)
  Thanks in advance.
  lsb_release -rd
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-153-generic 3.13.0-153.203
  ProcVersionSignature: Ubuntu 3.13.0-153.203-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-153-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juan   2042 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  9 18:33:25 2018
  HibernationDevice: RESUME=UUID=d636c2b9-ed1b-472f-93c6-12845c9560d1
  InstallationDate: Installed on 2016-02-09 (881 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: Dell Inc. Inspiron 1440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic 
root=UUID=3ec0f1ba-dc84-47b0-9fec-4595cd904f69 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-153-generic N/A
   linux-backports-modules-3.13.0-153-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

[njsf]

NOTE: Results w/ haveged installed...

I installed gdm3 3.28.0-ubuntu1 with:

apt-get install gdm3=3.28.0-0ubuntu1 libgdm1=3.28.0-0ubuntu1
gir1.2-gdm-1.0=3.28.0-0ubuntu1

After reboot gdm3 would still not start.

After I noticed the path used I decided to:

rm -rf /var/lib/gdm3/*
rm -rf /var/lib/gdm3/.[a-z]*

After a reboot gdm3 started both w/ Xwayland and Xorg

It seems that the upgrade to kernel 4.15.0-24 together w/ gdm3 upgrade
caused some corruption of the gdm3 cached contents under /var/lib/gdm3
that prevented it from starting.

IMO this is not an easy thing to troubleshoot as nothing in the logs indicated 
any issue.
It is could also be preventable: have the gdm3 package always clear 
/var/lib/gdm3 as the next start will recreate.

As it stands now, my issue of gdm3 not starting is resolved, the
haveged/entropy dependency is properly tracked by bug 1779827.

Leave it up to you whether you want to use this bug to improve the gdm3
upgrade process or close it as I documented how I fixed it

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

Title:
  Ubuntu 18.04: gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  

[Kernel-packages] [Bug 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1780124

Title:
  linux-gcp: 4.15.0-1012.12~16.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780124/+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 997825] Re: Missing nls_utf8.ko kernel module

[Ken Sharp]

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

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

Title:
  Missing nls_utf8.ko kernel module

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I think I can't mount a CIFS share since I don't have the nls_utf8
  module in the kernel linux-image-virtual.

  May 10 17:41:30 kickseed kernel: [ 6319.282908] CIFS VFS: CIFS mount
  error: iocharset utf8 not found

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-virtual 3.2.0.24.26
  ProcVersionSignature: Ubuntu 3.2.0-24.37-virtual 3.2.14
  Uname: Linux 3.2.0-24-virtual i686
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 mai 10 15:56 seq
   crw-rw---T 1 root audio 116, 33 mai 10 15:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Thu May 10 17:51:10 2012
  HibernationDevice: RESUME=UUID=fb76e125-6895-456c-a2c4-0a2979a0de1b
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 
(20120424.1)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   TERM=screen
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-virtual 
root=UUID=191ae0c4-da2c-4772-bff3-7ff22378389c ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-virtual N/A
   linux-backports-modules-3.2.0-24-virtual  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/13/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/13/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997825/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

[Seth Forshee]

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

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

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+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 1780120] Re: linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780120/+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 1780785] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  package linux-image-generic 4.4.0.130.136 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
  code 127

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ACTUALICE PERO DIO ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.130.136
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   2014 F pulseaudio
  Date: Mon Jul  9 15:17:46 2018
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=66ae5499-615e-492d-a994-812d1bf2e83d
  MachineType: Acer Aspire 5733Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=75eda110-9722-43fc-b193-0c6320275164 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733Z:pvrV1.08:rvnAcer:rnAspire5733Z:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780785/+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 1780118] Re: linux-gcp: 4.15.0-1012.12 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1780118

Title:
  linux-gcp: 4.15.0-1012.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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 1779823] Re: xhci_hcd 0000:00:14.0: Root hub is not suspended

[Seth Forshee]

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

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

Title:
  xhci_hcd :00:14.0: Root hub is not suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  Runtime suspended xHC keeps spewing out this message:
  xhci_hcd :00:14.0: Root hub is not suspended

  [Test]
  With the fix, the message stops.

  [Fix]
  Only decrement PM counter when DBC was started.

  [Regression Potential]
  Low. It fixes the overlooked logic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1779823/+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 1779357] Re: linux-oem: 4.15.0-1010.13 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.15.0-1010.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779357/+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 1780117] Re: linux-azure: 4.15.0-1016.16 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-azure: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+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 1780115] Re: linux-aws: 4.15.0-1013.13 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.15.0-1013.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780115/+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 1780119] Re: linux-kvm: 4.15.0-1014.14 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-kvm: 4.15.0-1014.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1780112
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780119/+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 1780112] Re: linux: 4.15.0-26.28 -proposed tracker

[Steve Beattie]

Regression USN needed.

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux: 4.15.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780112/+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 1780785] Re: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

[Ubuntu Kernel Bot]

** 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/1780785

Title:
  package linux-image-generic 4.4.0.130.136 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
  code 127

Status in linux package in Ubuntu:
  New

Bug description:
  ACTUALICE PERO DIO ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.130.136
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   2014 F pulseaudio
  Date: Mon Jul  9 15:17:46 2018
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=66ae5499-615e-492d-a994-812d1bf2e83d
  MachineType: Acer Aspire 5733Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=75eda110-9722-43fc-b193-0c6320275164 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733Z:pvrV1.08:rvnAcer:rnAspire5733Z:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780785/+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 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

[Seth Forshee]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  Enable AMD PCIe MP2 for AMDI0011

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  Touchpad doesn't work on Latitude 5495.

  [Test]
  I can confirm the driver from AMD works.
  All issues found by us should be fixed.

  [Fix]
  The touchpad connects to AMDI0011, which doesn't have any driver until
  now.
  I'll backport the patch to A/B/C once it's in mainline and gets
  thoroughly tested.
   
  [Regression Potential]
  Low. It's a new driver, shouldn't affect any other device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773940/+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 1773392] Re: zfs hangs on mount/unmount

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  zfs hangs on mount/unmount

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and
  4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16;
  also tried 0.7.9).

  Sometimes lxd hangs when I try to stop / restart or "stop && move"
  some containers. Furhter investigation showed that problem is in zfs
  mount or unmount: it just hangs and lxd just wait it. Also commands
  like "zfs list" hangs to.

  It seems that it is not lxd or zfs issue, but kernel bug?
  https://github.com/lxc/lxd/issues/4104#issuecomment-392072939

  I have one test ct that always hangs on restart, so here is info:

  dmesg:
  [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds.
  [ 1330.390994]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391101] txg_syncD0  9944  2 0x8000
  [ 1330.391105] Call Trace:
  [ 1330.391117]  __schedule+0x297/0x8b0
  [ 1330.391122]  schedule+0x2c/0x80
  [ 1330.391136]  cv_wait_common+0x11e/0x140 [spl]
  [ 1330.391141]  ? wait_woken+0x80/0x80
  [ 1330.391152]  __cv_wait+0x15/0x20 [spl]
  [ 1330.391234]  rrw_enter_write+0x3c/0xa0 [zfs]
  [ 1330.391306]  rrw_enter+0x13/0x20 [zfs]
  [ 1330.391380]  spa_sync+0x7c9/0xd80 [zfs]
  [ 1330.391457]  txg_sync_thread+0x2cd/0x4a0 [zfs]
  [ 1330.391534]  ? txg_quiesce_thread+0x3d0/0x3d0 [zfs]
  [ 1330.391543]  thread_generic_wrapper+0x74/0x90 [spl]
  [ 1330.391549]  kthread+0x121/0x140
  [ 1330.391558]  ? __thread_exit+0x20/0x20 [spl]
  [ 1330.391562]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391566]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391569]  ret_from_fork+0x35/0x40
  [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds.
  [ 1330.391630]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391735] lxd D0 12419  1 0x
  [ 1330.391739] Call Trace:
  [ 1330.391745]  __schedule+0x297/0x8b0
  [ 1330.391749]  schedule+0x2c/0x80
  [ 1330.391752]  rwsem_down_write_failed+0x162/0x360
  [ 1330.391808]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [ 1330.391814]  call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391817]  ? call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391821]  down_write+0x2d/0x40
  [ 1330.391825]  grab_super+0x30/0x90
  [ 1330.391901]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391905]  sget_userns+0x91/0x490
  [ 1330.391908]  ? get_anon_bdev+0x100/0x100
  [ 1330.391983]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391987]  sget+0x7d/0xa0
  [ 1330.391990]  ? get_anon_bdev+0x100/0x100
  [ 1330.392066]  zpl_mount+0xa8/0x160 [zfs]
  [ 1330.392071]  mount_fs+0x37/0x150
  [ 1330.392077]  vfs_kern_mount.part.23+0x5d/0x110
  [ 1330.392080]  do_mount+0x5ed/0xce0
  [ 1330.392083]  ? copy_mount_options+0x2c/0x220
  [ 1330.392086]  SyS_mount+0x98/0xe0
  [ 1330.392092]  do_syscall_64+0x73/0x130
  [ 1330.392096]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1330.392099] RIP: 0033:0x4db36a
  [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 
00a5
  [ 1330.392104] RAX: ffda RBX:  RCX: 
004db36a
  [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 
00c420a23b60
  [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: 

  [ 1330.392110] R10:  R11: 0216 R12: 

  [ 1330.392112] R13: 0039 R14: 0038 R15: 
0080
  [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds.
  [ 1330.392171]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.392276] lxd D0 16725  1 0x0002
  [ 1330.392279] Call Trace:
  [ 1330.392284]  __schedule+0x297/0x8b0
  [ 1330.392289]  ? irq_work_queue+0x8d/0xa0
  [ 1330.392293]  schedule+0x2c/0x80
  [ 1330.392297]  io_schedule+0x16/0x40
  [ 1330.392302]  wait_on_page_bit_common+0xd8/0x160
  [ 1330.392305]  ? page_cache_tree_insert+0xe0/0xe0
  [ 1330.392309]  __filemap_fdatawait_range+0xfa/0x160
  [ 1330.392313]  ? _cond_resched+0x19/0x40
  [ 1330.392317]  ? bdi_split_work_to_wbs+0x45/0x2c0
  [ 1330.392321]  ? _cond_resched+0x19/0x40
  [ 1330.392324]  filemap_fdatawait_keep_errors+0x1e/0x40
  [ 1330.392327]  sync_inodes_sb+0x20d/0x2b0
  [ 1330.392333]  __sync_filesystem+0x1b/0x60
  [ 1330.392336]  sync_filesystem+0x39/0x40
  [ 1330.392340]  

[Kernel-packages] [Bug 1777736] Re: hisi_sas_v3_hw: internal task abort: timeout and not done.

[Seth Forshee]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  hisi_sas_v3_hw: internal task abort: timeout and not done.

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

Bug description:
  [Impact]
  On deployments with lots of disks, timeouts can occur that escalate into 
nexus resets. This can cause disk devices to disappear from the system, 
possibly requiring a reboot to recover:

  [18324.951189] cq: iptt:892, task:8026fbde5000, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:16,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
  [18324.951190] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
  [18324.951191] cmd table: 0x0,0x0,0x0,0x0,0x0
  [18324.951192] itct: 
0x12fa0345,0x5000cca25d31dac1,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
  [18324.951334] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8026fbde5000) ignored

  [18325.039774] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
  [18325.044467] cmd table: 0x0,0x0,0x0,0x0,0x0
  [18325.048553] itct: 
0x12fa0345,0x5000c50094c65c55,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
  [18325.057058] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8027dc8e7500) ignored

  [18326.951312] cq: iptt:1705, task:8027820d0200, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:18,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
  [18326.968247] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
  [18326.972938] cmd table: 0x0,0x0,0x0,0x0,0x0
  [18326.977023] itct: 
0x12fa0345,0x5000cca0803e9c1d,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
  [18326.985496] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8027820d0200) ignored

  [18329.384695] hisi_sas_v3_hw :74:02.0: internal task abort: timeout and 
not done.
  [18329.392344] hisi_sas_v3_hw :74:02.0: start dump all regs,reason:abort 
timeout!
  [18329.399904] ***DUMP IS DISABLED***
  [18329.405467] dump reg fail.
  [18329.408162] hisi_sas_v3_hw :74:02.0: I_T nexus reset: internal abort 
(-5)
  [18329.936017] cq: iptt:649, task:8027981f8500, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:19,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
  [18329.936154] cq: iptt:1091, task:8026ff666d00, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:49,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
  [18329.936155] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
  [18329.936156] cmd table: 0x0,0x0,0x0,0x0,0x0
  [18329.936158] itct: 
0x12fa0345,0x5000cca2552b2855,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
  [18329.936301] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8026ff666d00) ignored

  [Test Case]
  This was seen on a system with 100s of disks, something I don't have access 
to, so verification testing will be regression-only.

  [Fix]
  A fix queued in the scsi maintainer's tree adjusts some magic registers in 
the controller, and that somehow fixes the problem (I don't have programming 
docs for this controller, so I can only hand-wave here).

  [Regression Risk]
  The fix is localized to the hisi_sas_v3_hw driver, which is only used in 
Ubuntu for the D06 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136/+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 1780165] Re: tc does not display value of prio and quantum options of htb on bionic

[fumihiko kakuma]

Please backport the following.

https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/tc/q_htb.c?id=d529ea2ff417eed1d48c580e099388aaace16ce9

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

  I think that the above patch can be applied for the bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1780165/+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 1780785] Re: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

[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-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1780785

Title:
  package linux-image-generic 4.4.0.130.136 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
  code 127

Status in linux-meta package in Ubuntu:
  New

Bug description:
  ACTUALICE PERO DIO ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.130.136
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   2014 F pulseaudio
  Date: Mon Jul  9 15:17:46 2018
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=66ae5499-615e-492d-a994-812d1bf2e83d
  MachineType: Acer Aspire 5733Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=75eda110-9722-43fc-b193-0c6320275164 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733Z:pvrV1.08:rvnAcer:rnAspire5733Z:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1780785/+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 1780785] Re: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

[Seth Arnold]

This looks relevant, I hope this helps:

/usr/sbin/grub-mkconfig: 13: /etc/default/grub: psmouse.resolution=1200:
not found

Thanks

** Information type changed from Private Security to Public

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

Title:
  package linux-image-generic 4.4.0.130.136 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
  code 127

Status in linux-meta package in Ubuntu:
  New

Bug description:
  ACTUALICE PERO DIO ERROR

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.130.136
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   2014 F pulseaudio
  Date: Mon Jul  9 15:17:46 2018
  ErrorMessage: dependency problems - leaving unconfigured
  HibernationDevice: RESUME=UUID=66ae5499-615e-492d-a994-812d1bf2e83d
  MachineType: Acer Aspire 5733Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=75eda110-9722-43fc-b193-0c6320275164 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.130.136 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733Z:pvrV1.08:rvnAcer:rnAspire5733Z:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1780785/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

[Scott Moser]

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: cloud-init (Ubuntu Bionic)
   Status: Confirmed => Invalid

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

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+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 1780858] [NEW] Bionic update: upstream stable patchset 2018-07-09

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2018-07-09 (ported from v4.14.42 and v4.16.10)
   from git://git.kernel.org/

hv_netvsc: Fix net device attach on older Windows hosts
tipc: fix one byte leak in tipc_sk_set_orig_addr()
tcp: restore autocorking
sctp: clear the new asoc's stream outcnt in sctp_stream_update
net: systemport: Correclty disambiguate driver instances
net/mlx5e: DCBNL fix min inline header size for dscp
mlxsw: spectrum_switchdev: Do not remove mrouter port from MDB's ports list
net/smc: restrict non-blocking connect finish
proc: do not access cmdline nor environ from file-backed areas
l2tp: revert "l2tp: fix missing print session offset info"
udp: fix SO_BINDTODEVICE
nsh: fix infinite loop
net/mlx5e: Allow offloading ipv4 header re-write for icmp
ipv6: fix uninit-value in ip6_multipath_l3_keys()
hv_netvsc: set master device
net/mlx5: Avoid cleaning flow steering table twice during error flow
net/mlx5e: TX, Use correct counter in dma_map error flow
net: sched: fix error path in tcf_proto_create() when modules are not configured
bonding: send learning packets for vlans on slave
bonding: do not allow rlb updates to invalid mac
tg3: Fix vunmap() BUG_ON() triggered from tg3_free_consistent().
tcp: ignore Fast Open on repair mode
tcp_bbr: fix to zero idle_restart only upon S/ACKed data
sctp: use the old asoc when making the cookie-ack chunk in dupcook_d
sctp: remove sctp_chunk_put from fail_mark err path in sctp_ulpevent_make_rcvmsg
sctp: handle two v4 addrs comparison in sctp_inet6_cmp_addr
sctp: fix the issue that the cookie-ack with auth can't get processed
sctp: delay the authentication for the duplicated cookie-echo chunk
rds: do not leak kernel memory to user land
r8169: fix powering up RTL8168h
qmi_wwan: do not steal interfaces from class drivers
openvswitch: Don't swap table in nlattr_set() after OVS_ATTR_NESTED is found
net/tls: Fix connection stall on partial tls record
net/tls: Don't recursively call push_record during tls_write_space callbacks
net: support compat 64-bit time in {s,g}etsockopt
net_sched: fq: take care of throttled flows before reuse
net sched actions: fix refcnt leak in skbmod
net/mlx5: E-Switch, Include VF RDMA stats in vport statistics
net/mlx5e: Err if asked to offload TC match on frag being first
net/mlx4_en: Verify coalescing parameters are in range
net/mlx4_en: Fix an error handling path in 'mlx4_en_init_netdev()'
net: ethernet: ti: cpsw: fix packet leaking in dual_mac mode
net: ethernet: sun: niu set correct packet size in skb
llc: better deal with too small mtu
ipv4: fix memory leaks in udp_sendmsg, ping_v4_sendmsg
ipv4: fix fnhe usage by non-cached routes
dccp: fix tasklet usage
bridge: check iface upper dev when setting master via ioctl
8139too: Use disable_irq_nosync() in rtl8139_poll_controller()

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2018-07-09 (ported from v4.14.42 and v4.16.10)
+    from git://git.kernel.org/
  
-upstream stable patchset 2018-07-09
-from git://git.kernel.org/
+ hv_netvsc: Fix net device attach on older Windows hosts
+ tipc: fix one byte leak in tipc_sk_set_orig_addr()
+ tcp: restore autocorking
+ sctp: clear the new asoc's stream outcnt in sctp_stream_update

[Kernel-packages] [Bug 1780809] Re: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: wireless-regdb (Ubuntu)
   Status: New => Confirmed

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

Title:
  package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade:
  trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is
  also in package crda 3.18-0ubuntu1

Status in wireless-regdb package in Ubuntu:
  Confirmed

Bug description:
  A requirement of update appeared and I've just accepted it. But during
  the process of installation, a failure happened. It seems to refer to
  the wireless register.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: wireless-regdb 2016.06.10-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Jul  9 11:58:30 2018
  Dependencies:
   
  DuplicateSignature:
   package:wireless-regdb:2016.06.10-0ubuntu1
   Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over 
(2016.06.10-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-04WWLs/56-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb
 (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package crda 3.18-0ubuntu1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package crda 3.18-0ubuntu1
  InstallationDate: Installed on 2017-09-03 (308 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: wireless-regdb
  Title: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: 
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in 
package crda 3.18-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1780809/+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 1607355] Re: Task (usually mongod) blocked more 120 seconds (lock-ups) in juju on lxc/lxd + zfs

[Simos Xenitellis ]

This might be related to #1773392.

On the other hand, the issue in #1773392 appears to have been introduced
in more recent kernels (16.04 not affected).

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

Title:
  Task (usually mongod) blocked more 120 seconds (lock-ups) in juju on
  lxc/lxd + zfs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was able to reproduce this 2 or 3 times last 2 days. I have the
  following setup:

  Containers for Trusty/kilo service machines:

  inaddy@workstation:~$ lxc-ls  | grep tk
  tkcephmon01  RUNNING 0 -  192.168.65.52 -
  tkcephmon02  RUNNING 0 -  192.168.65.51 -
  tkcephmon03  RUNNING 0 -  192.168.65.48 -
  tkcinder RUNNING 0 -  192.168.65.49 -
  tkdash   RUNNING 0 -  192.168.65.50 -
  tkglance RUNNING 0 -  192.168.65.53 -
  tkjuju   RUNNING 0 -  192.168.65.15 -
  tkkeystone   RUNNING 0 -  192.168.65.54 -
  tkmysql  RUNNING 0 -  192.168.65.55 -
  tknova   RUNNING 0 -  192.168.65.56 -
  tkrabbit RUNNING 0 -  192.168.65.57 -
  tkswiftproxy RUNNING 0 -  192.168.65.58 -

  And compute nodes + neutrongw as kvm guests:

  inaddy@workstation:~$ virsh list --all | grep tk
   21tkcompute01running
   22tkcompute02running
   23tkcompute03running
   24tkneutrongwrunning

  All my LXC containers are on top of ZFS:

  Linux workstation 4.4.0-32-generic #51-Ubuntu SMP Tue Jul 19 18:09:07
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  And my KVM guests are on top of ext4 + 1.2 raid0 stripped volume.

  I'm getting the lockups bellow (usually for mongod, from tkjuju
  container, the juju controller). After the first lockup appears
  (schedule timeout coming from zfs sync logic most likely), JuJu
  controller starts giving me errors on "update-status". From "juju
  status":

  glance/0error  idle1.25.6  10  9292/tcp   
tkglance   hook failed: "update-status"
  keystone/0  error  idle1.25.6  11 
tkkeystone hook failed: "update-status"
  mysql/0 error  idle1.25.6  12 
tkmysqlhook failed: "config-changed"
  neutron-api/0   error  idle1.25.6  4   9696/tcp   
tkneutrongwhook failed: "update-status"
  nova-compute/0  error  idle1.25.6  1  
tkcompute01hook failed: "update-status"
  nova-compute/1  error  idle1.25.6  2  
tkcompute02hook failed: "update-status"
  nova-compute/2  error  idle1.25.6  3  
tkcompute03hook failed: "update-status"

  Lockups:

  [105601.816578] INFO: task mongod:14480 blocked for more than 120 seconds.
  [105601.816583]   Tainted: P   O4.4.0-32-generic #51-Ubuntu
  [105601.816584] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [105601.816586] mongod  D 88010ec47ba8 0 14480  16855 
0x0100
  [105601.816590]  88010ec47ba8 57992eeb 880108e5ee00 
880108e58dc0
  [105601.816592]  88010ec48000 88081ecd6d00 7fff 
8182a600
  [105601.816594]  88010ec47d08 88010ec47bc0 81829e05 

  [105601.816596] Call Trace:
  [105601.816603]  [] ? bit_wait+0x60/0x60
  [105601.816606]  [] schedule+0x35/0x80
  [105601.816608]  [] schedule_timeout+0x1b5/0x270
  [105601.816612]  [] ? find_get_pages_tag+0x109/0x190
  [105601.816614]  [] ? bit_wait+0x60/0x60
  [105601.816616]  [] io_schedule_timeout+0xa4/0x110
  [105601.816618]  [] bit_wait_io+0x1b/0x70
  [105601.816620]  [] __wait_on_bit+0x5d/0x90
  [105601.816622]  [] wait_on_page_bit+0xcb/0xf0
  [105601.816625]  [] ? autoremove_wake_function+0x40/0x40
  [105601.816628]  [] __filemap_fdatawait_range+0xf3/0x160
  [105601.816630]  [] filemap_fdatawait_range+0x14/0x30
  [105601.816632]  [] filemap_write_and_wait_range+0x3f/0x70
  [105601.816682]  [] zpl_fsync+0x38/0x90 [zfs]
  [105601.816685]  [] vfs_fsync_range+0x4b/0xb0
  [105601.816687]  [] SyS_msync+0x17e/0x1f0
  [105601.816689]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [117121.961545] INFO: task txg_sync:4589 blocked for more than 120 seconds.
  [117121.961549]   Tainted: P   O4.4.0-32-generic #51-Ubuntu
  [117121.961550] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [117121.961551] txg_syncD 8807e1fbbaa8 0  4589  2 
0x
  

[Kernel-packages] [Bug 1773392] Re: zfs hangs on mount/unmount

[Simos Xenitellis ]

Upstream bug report and pull request to try:

"Kernel error "task zfs:pid blocked for more than 120 seconds" #7691"
https://github.com/zfsonlinux/zfs/issues/7691

"Fix zpl_mount() deadlock #7693"
https://github.com/zfsonlinux/zfs/pull/7693

** Bug watch added: Github Issue Tracker for ZFS #7691
   https://github.com/zfsonlinux/zfs/issues/7691

** Also affects: linux via
   https://github.com/zfsonlinux/zfs/issues/7691
   Importance: Unknown
   Status: Unknown

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

Title:
  zfs hangs on mount/unmount

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and
  4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16;
  also tried 0.7.9).

  Sometimes lxd hangs when I try to stop / restart or "stop && move"
  some containers. Furhter investigation showed that problem is in zfs
  mount or unmount: it just hangs and lxd just wait it. Also commands
  like "zfs list" hangs to.

  It seems that it is not lxd or zfs issue, but kernel bug?
  https://github.com/lxc/lxd/issues/4104#issuecomment-392072939

  I have one test ct that always hangs on restart, so here is info:

  dmesg:
  [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds.
  [ 1330.390994]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391101] txg_syncD0  9944  2 0x8000
  [ 1330.391105] Call Trace:
  [ 1330.391117]  __schedule+0x297/0x8b0
  [ 1330.391122]  schedule+0x2c/0x80
  [ 1330.391136]  cv_wait_common+0x11e/0x140 [spl]
  [ 1330.391141]  ? wait_woken+0x80/0x80
  [ 1330.391152]  __cv_wait+0x15/0x20 [spl]
  [ 1330.391234]  rrw_enter_write+0x3c/0xa0 [zfs]
  [ 1330.391306]  rrw_enter+0x13/0x20 [zfs]
  [ 1330.391380]  spa_sync+0x7c9/0xd80 [zfs]
  [ 1330.391457]  txg_sync_thread+0x2cd/0x4a0 [zfs]
  [ 1330.391534]  ? txg_quiesce_thread+0x3d0/0x3d0 [zfs]
  [ 1330.391543]  thread_generic_wrapper+0x74/0x90 [spl]
  [ 1330.391549]  kthread+0x121/0x140
  [ 1330.391558]  ? __thread_exit+0x20/0x20 [spl]
  [ 1330.391562]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391566]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391569]  ret_from_fork+0x35/0x40
  [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds.
  [ 1330.391630]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391735] lxd D0 12419  1 0x
  [ 1330.391739] Call Trace:
  [ 1330.391745]  __schedule+0x297/0x8b0
  [ 1330.391749]  schedule+0x2c/0x80
  [ 1330.391752]  rwsem_down_write_failed+0x162/0x360
  [ 1330.391808]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [ 1330.391814]  call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391817]  ? call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391821]  down_write+0x2d/0x40
  [ 1330.391825]  grab_super+0x30/0x90
  [ 1330.391901]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391905]  sget_userns+0x91/0x490
  [ 1330.391908]  ? get_anon_bdev+0x100/0x100
  [ 1330.391983]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391987]  sget+0x7d/0xa0
  [ 1330.391990]  ? get_anon_bdev+0x100/0x100
  [ 1330.392066]  zpl_mount+0xa8/0x160 [zfs]
  [ 1330.392071]  mount_fs+0x37/0x150
  [ 1330.392077]  vfs_kern_mount.part.23+0x5d/0x110
  [ 1330.392080]  do_mount+0x5ed/0xce0
  [ 1330.392083]  ? copy_mount_options+0x2c/0x220
  [ 1330.392086]  SyS_mount+0x98/0xe0
  [ 1330.392092]  do_syscall_64+0x73/0x130
  [ 1330.392096]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1330.392099] RIP: 0033:0x4db36a
  [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 
00a5
  [ 1330.392104] RAX: ffda RBX:  RCX: 
004db36a
  [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 
00c420a23b60
  [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: 

  [ 1330.392110] R10:  R11: 0216 R12: 

  [ 1330.392112] R13: 0039 R14: 0038 R15: 
0080
  [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds.
  [ 1330.392171]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.392276] lxd D0 16725  1 0x0002
  [ 1330.392279] Call Trace:
  [ 1330.392284]  __schedule+0x297/0x8b0
  [ 1330.392289]  ? irq_work_queue+0x8d/0xa0
  [ 1330.392293]  schedule+0x2c/0x80
  [ 1330.392297]  io_schedule+0x16/0x40
  [ 1330.392302]  wait_on_page_bit_common+0xd8/0x160
  [ 1330.392305]  ? page_cache_tree_insert+0xe0/0xe0
  [ 1330.392309]  

[Kernel-packages] [Bug 1780832] Re: Cosmic update to v4.17.4 stable release

[Seth Forshee]

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.17.4 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.
  
     git://git.kernel.org/
  
  TEST CASE: TBD
  
     The following patches from the v4.17.4 stable release shall be
  applied:
  
  x86/spectre_v1: Disable compiler optimizations over array_index_mask_nospec()
  x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths
  x86/platform/UV: Add adjustable set memory block size function
  x86/platform/UV: Use new set memory block size function
  x86/platform/UV: Add kernel parameter to set memory block size
  x86/mce: Improve error message when kernel cannot recover
  x86/mce: Check for alternate indication of machine check recovery on Skylake
  x86/mce: Fix incorrect "Machine check from unknown source" message
  x86/mce: Do not overwrite MCi_STATUS in mce_no_way_out()
  x86: Call fixup_exception() before notify_die() in math_error()
  m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap()
  m68k/mac: Fix SWIM memory resource end address
  platform/chrome: cros_ec_lpc: do not try DMI match when ACPI device found
  hwmon: (k10temp) Add support for Stoney Ridge and Bristol Ridge CPUs
  mtd: spi-nor: intel-spi: Fix atomic sequence handling
  serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version
  signal/xtensa: Consistenly use SIGBUS in do_unaligned_user
  PM / Domains: Fix error path during attach in genpd
  PCI / PM: Do not clear state_saved for devices that remain suspended
  ACPI / LPSS: Avoid PM quirks on suspend and resume from S3
  PM / core: Fix supplier device runtime PM usage counter imbalance
  PM / OPP: Update voltage in case freq == old_freq
  mmc: renesas_sdhi: really fix WP logic regressions
  usb: do not reset if a low-speed or full-speed device timed out
  1wire: family module autoload fails because of upper/lower case mismatch.
  ASoC: dapm: delete dapm_kcontrol_data paths list before freeing it
  ASoC: cs35l35: Add use_single_rw to regmap config
  ASoC: mediatek: preallocate pages use platform device
  ASoC: cirrus: i2s: Fix LRCLK configuration
  ASoC: cirrus: i2s: Fix {TX|RX}LinCtrlData setup
  thermal: bcm2835: Stop using printk format %pCr
  clk: renesas: cpg-mssr: Stop using printk format %pCr
  lib/vsprintf: Remove atomic-unsafe support for %pCr
  ftrace/selftest: Have the reset_trigger code be a bit more careful
  mips: ftrace: fix static function graph tracing
  branch-check: fix long->int truncation when profiling branches
  ipmi:bt: Set the timeout before doing a capabilities check
  Bluetooth: hci_qca: Avoid missing rampatch failure with userspace fw loader
  printk: fix possible reuse of va_list variable
  fuse: fix congested state leak on aborted connections
  fuse: atomic_o_trunc should truncate pagecache
  fuse: don't keep dead fuse_conn at fuse_fill_super().
  fuse: fix control dir setup and teardown
  powerpc/mm/hash: Add missing isync prior to kernel stack SLB switch
  powerpc/pkeys: Detach execute_only key on !PROT_EXEC
  powerpc/ptrace: Fix setting 512B aligned breakpoints with PTRACE_SET_DEBUGREG
- powerpc/perf: Fix memory allocation for core-imc based on num_possible_cpus()
  powerpc/ptrace: Fix enforcement of DAWR constraints
  powerpc/powernv/ioda2: Remove redundant free of TCE pages
  powerpc/powernv: copy/paste - Mask SO bit in CR
- powerpc/powernv/cpuidle: Init all present cpus for deep states
  cpuidle: powernv: Fix promotion from snooze if next state disabled
  powerpc/fadump: Unregister fadump on kexec down path.
  libnvdimm, pmem: Do not flush power-fail protected CPU caches
  soc: rockchip: power-domain: Fix wrong value when power up pd with writemask
  powerpc/64s/radix: Fix radix_kvm_prefetch_workaround paca access of not 
possible CPU
  powerpc/e500mc: Set assembler machine type to e500mc
  powerpc/64s: Fix DT CPU features Power9 DD2.1 logic
- cxl: Configure PSL to not use APC virtual machines
- cxl: Disable prefault_mode in Radix mode
  ARM: 8764/1: kgdb: fix NUMREGBYTES so that gdb_regs[] is the correct size
  ARM: dts: sun8i: h3: fix ALL-H3-CC H3 ver VDD-CPUX voltage
  ARM: dts: sun8i: h3: fix ALL-H3-CC H3 ver VCC-1V2 regulator voltage
  ARM: dts: Fix SPI node for Arria10
  ARM: dts: socfpga: Fix NAND controller node compatible
  ARM: dts: socfpga: Fix NAND controller clock supply
  ARM: dts: socfpga: Fix NAND controller node compatible for Arria10
  hwrng: core - Always drop the RNG in hwrng_unregister()
  softirq: Reorder trace_softirqs_on to prevent lockdep splat
  arm64: Fix syscall restarting around signal suppressed by tracer
 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Steve Langasek]

Ok it should be possible to add message-modules to the netboot image,
yes.

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs invocation. Parent PID 8940: 

[Kernel-packages] [Bug 1780833] Re: Cosmic update to v4.17.5 stable release

[Seth Forshee]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Cosmic update to v4.17.5 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.17.5 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.17.5 stable release shall be
  applied:

  usb: cdc_acm: Add quirk for Uniden UBC125 scanner
  USB: serial: cp210x: add CESINEL device ids
  USB: serial: cp210x: add Silicon Labs IDs for Windows Update
  usb: dwc2: fix the incorrect bitmaps for the ports of multi_tt hub
  usb: typec: tcpm: fix logbuffer index is wrong if _tcpm_log is re-entered
  acpi: Add helper for deactivating memory region
  usb: typec: ucsi: acpi: Workaround for cache mode issue
  usb: typec: ucsi: Fix for incorrect status data issue
  xhci: Fix kernel oops in trace_xhci_free_virt_device
  n_tty: Fix stall at n_tty_receive_char_special().
  n_tty: Access echo_* variables carefully.
  staging: android: ion: Return an ERR_PTR in ion_map_kernel
  iio: mma8452: Fix ignoring MMA8452_INT_DRDY
  serial: 8250_pci: Remove stalled entries in blacklist
  serdev: fix memleak on module unload
  vt: prevent leaking uninitialized data to userspace via /dev/vcs*
  drm/amdgpu: Add APU support in vi_set_uvd_clocks
  drm/amdgpu: Add APU support in vi_set_vce_clocks
  drm/amdgpu: fix the missed vcn fw version report
  drm/amdgpu: Grab/put runtime PM references in atomic_commit_tail()
  drm/amdgpu: fix clear_all and replace handling in the VM (v2)
  drm/sti: Depend on OF rather than selecting it
  drm/amd/display: Clear connector's edid pointer
  drm/i915/dp: Send DPCD ON for MST before phy_up
  drm/qxl: Call qxl_bo_unref outside atomic context
  drm/atmel-hlcdc: check stride values in the first plane
  Revert "drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE"
  drm/amdgpu: Don't default to DC support for Kaveri and older
  drm/amdgpu: Use kvmalloc_array for allocating VRAM manager nodes array
  drm/amdgpu: Refactor amdgpu_vram_mgr_bo_invisible_size helper
  drm/amdgpu: Make amdgpu_vram_mgr_bo_invisible_size always accurate
  drm/amdgpu: Update pin_size values before unpinning BO
  drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping
  drm/amdgpu: Count disabled CRTCs in commit tail earlier
  drm/amd/display: release spinlock before committing updates to stream
  drm/i915: Allow DBLSCAN user modes with eDP/LVDS/DSI
  drm/i915: Fix PIPESTAT irq ack on i965/g4x
  drm/i915: Disallow interlaced modes on g4x DP outputs
  drm/i915: Turn off g4x DP port in .post_disable()
  drm/i915: Enable provoking vertex fix on Gen9 systems.
  netfilter: ip6t_rpfilter: provide input interface for route lookup
  netfilter: xt_connmark: fix list corruption on rmmod
  netfilter: nf_tables: use WARN_ON_ONCE instead of BUG_ON in nft_do_chain()
  ARM64: dts: meson-gxl-s905x-p212: Add phy-supply for usb0
  x86/mm: Don't free P4D table when it is folded at runtime
  ARM: dts: imx6q: Use correct SDMA script for SPI5 core
  Linux 4.17.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780833/+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 1780832] [NEW] Cosmic update to v4.17.4 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.17.4 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.17.4 stable release shall be
applied:

x86/spectre_v1: Disable compiler optimizations over array_index_mask_nospec()
x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths
x86/platform/UV: Add adjustable set memory block size function
x86/platform/UV: Use new set memory block size function
x86/platform/UV: Add kernel parameter to set memory block size
x86/mce: Improve error message when kernel cannot recover
x86/mce: Check for alternate indication of machine check recovery on Skylake
x86/mce: Fix incorrect "Machine check from unknown source" message
x86/mce: Do not overwrite MCi_STATUS in mce_no_way_out()
x86: Call fixup_exception() before notify_die() in math_error()
m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap()
m68k/mac: Fix SWIM memory resource end address
platform/chrome: cros_ec_lpc: do not try DMI match when ACPI device found
hwmon: (k10temp) Add support for Stoney Ridge and Bristol Ridge CPUs
mtd: spi-nor: intel-spi: Fix atomic sequence handling
serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version
signal/xtensa: Consistenly use SIGBUS in do_unaligned_user
PM / Domains: Fix error path during attach in genpd
PCI / PM: Do not clear state_saved for devices that remain suspended
ACPI / LPSS: Avoid PM quirks on suspend and resume from S3
PM / core: Fix supplier device runtime PM usage counter imbalance
PM / OPP: Update voltage in case freq == old_freq
mmc: renesas_sdhi: really fix WP logic regressions
usb: do not reset if a low-speed or full-speed device timed out
1wire: family module autoload fails because of upper/lower case mismatch.
ASoC: dapm: delete dapm_kcontrol_data paths list before freeing it
ASoC: cs35l35: Add use_single_rw to regmap config
ASoC: mediatek: preallocate pages use platform device
ASoC: cirrus: i2s: Fix LRCLK configuration
ASoC: cirrus: i2s: Fix {TX|RX}LinCtrlData setup
thermal: bcm2835: Stop using printk format %pCr
clk: renesas: cpg-mssr: Stop using printk format %pCr
lib/vsprintf: Remove atomic-unsafe support for %pCr
ftrace/selftest: Have the reset_trigger code be a bit more careful
mips: ftrace: fix static function graph tracing
branch-check: fix long->int truncation when profiling branches
ipmi:bt: Set the timeout before doing a capabilities check
Bluetooth: hci_qca: Avoid missing rampatch failure with userspace fw loader
printk: fix possible reuse of va_list variable
fuse: fix congested state leak on aborted connections
fuse: atomic_o_trunc should truncate pagecache
fuse: don't keep dead fuse_conn at fuse_fill_super().
fuse: fix control dir setup and teardown
powerpc/mm/hash: Add missing isync prior to kernel stack SLB switch
powerpc/pkeys: Detach execute_only key on !PROT_EXEC
powerpc/ptrace: Fix setting 512B aligned breakpoints with PTRACE_SET_DEBUGREG
powerpc/perf: Fix memory allocation for core-imc based on num_possible_cpus()
powerpc/ptrace: Fix enforcement of DAWR constraints
powerpc/powernv/ioda2: Remove redundant free of TCE pages
powerpc/powernv: copy/paste - Mask SO bit in CR
powerpc/powernv/cpuidle: Init all present cpus for deep states
cpuidle: powernv: Fix promotion from snooze if next state disabled
powerpc/fadump: Unregister fadump on kexec down path.
libnvdimm, pmem: Do not flush power-fail protected CPU caches
soc: rockchip: power-domain: Fix wrong value when power up pd with writemask
powerpc/64s/radix: Fix radix_kvm_prefetch_workaround paca access of not 
possible CPU
powerpc/e500mc: Set assembler machine type to e500mc
powerpc/64s: Fix DT CPU features Power9 DD2.1 logic
cxl: Configure PSL to not use APC virtual machines
cxl: Disable prefault_mode in Radix mode
ARM: 8764/1: kgdb: fix NUMREGBYTES so that gdb_regs[] is the correct size
ARM: dts: sun8i: h3: fix ALL-H3-CC H3 ver VDD-CPUX voltage
ARM: dts: sun8i: h3: fix ALL-H3-CC H3 ver VCC-1V2 regulator voltage
ARM: dts: Fix SPI node for Arria10
ARM: dts: socfpga: Fix NAND controller node compatible
ARM: dts: socfpga: Fix NAND controller clock supply
ARM: dts: socfpga: Fix NAND controller node compatible for Arria10
hwrng: core - Always drop the RNG in hwrng_unregister()
softirq: Reorder trace_softirqs_on to prevent lockdep splat
arm64: Fix syscall restarting around signal suppressed by tracer
crypto: arm64/aes-blk - fix and move skcipher_walk_done out of 
kernel_neon_begin, _end
arm64: kpti: Use early_param for kpti= command-line option
arm64: mm: Ensure writes to 

[Kernel-packages] [Bug 1780833] [NEW] Cosmic update to v4.17.5 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.17.5 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.17.5 stable release shall be
applied:

usb: cdc_acm: Add quirk for Uniden UBC125 scanner
USB: serial: cp210x: add CESINEL device ids
USB: serial: cp210x: add Silicon Labs IDs for Windows Update
usb: dwc2: fix the incorrect bitmaps for the ports of multi_tt hub
usb: typec: tcpm: fix logbuffer index is wrong if _tcpm_log is re-entered
acpi: Add helper for deactivating memory region
usb: typec: ucsi: acpi: Workaround for cache mode issue
usb: typec: ucsi: Fix for incorrect status data issue
xhci: Fix kernel oops in trace_xhci_free_virt_device
n_tty: Fix stall at n_tty_receive_char_special().
n_tty: Access echo_* variables carefully.
staging: android: ion: Return an ERR_PTR in ion_map_kernel
iio: mma8452: Fix ignoring MMA8452_INT_DRDY
serial: 8250_pci: Remove stalled entries in blacklist
serdev: fix memleak on module unload
vt: prevent leaking uninitialized data to userspace via /dev/vcs*
drm/amdgpu: Add APU support in vi_set_uvd_clocks
drm/amdgpu: Add APU support in vi_set_vce_clocks
drm/amdgpu: fix the missed vcn fw version report
drm/amdgpu: Grab/put runtime PM references in atomic_commit_tail()
drm/amdgpu: fix clear_all and replace handling in the VM (v2)
drm/sti: Depend on OF rather than selecting it
drm/amd/display: Clear connector's edid pointer
drm/i915/dp: Send DPCD ON for MST before phy_up
drm/qxl: Call qxl_bo_unref outside atomic context
drm/atmel-hlcdc: check stride values in the first plane
Revert "drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE"
drm/amdgpu: Don't default to DC support for Kaveri and older
drm/amdgpu: Use kvmalloc_array for allocating VRAM manager nodes array
drm/amdgpu: Refactor amdgpu_vram_mgr_bo_invisible_size helper
drm/amdgpu: Make amdgpu_vram_mgr_bo_invisible_size always accurate
drm/amdgpu: Update pin_size values before unpinning BO
drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping
drm/amdgpu: Count disabled CRTCs in commit tail earlier
drm/amd/display: release spinlock before committing updates to stream
drm/i915: Allow DBLSCAN user modes with eDP/LVDS/DSI
drm/i915: Fix PIPESTAT irq ack on i965/g4x
drm/i915: Disallow interlaced modes on g4x DP outputs
drm/i915: Turn off g4x DP port in .post_disable()
drm/i915: Enable provoking vertex fix on Gen9 systems.
netfilter: ip6t_rpfilter: provide input interface for route lookup
netfilter: xt_connmark: fix list corruption on rmmod
netfilter: nf_tables: use WARN_ON_ONCE instead of BUG_ON in nft_do_chain()
ARM64: dts: meson-gxl-s905x-p212: Add phy-supply for usb0
x86/mm: Don't free P4D table when it is folded at runtime
ARM: dts: imx6q: Use correct SDMA script for SPI5 core
Linux 4.17.5

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.17.5 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.17.5 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.17.5 stable release shall be
+ applied:
  
-The following patches from the v4.17.5 stable release shall be
- applied:
+ usb: cdc_acm: Add quirk for Uniden UBC125 

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

[bugproxy]

** Tags removed: severity-critical
** Tags added: severity-high

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Won't Fix

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the console,
  leaving the console free to watch for messages.

  To run:

  A. su - htx (this may take some time)
  B. htx
  C. 

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

[Ubuntu Kernel Bot]

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

Title:
  linux 3.13.0-151 causes win7 qemu-KVM VM to fail boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After my system was upgraded from linux 3.13.0-149 -> 3.13.0-151, my
  windows 7 virtual machine fails to boot.  I tried both my existing
  disk image, and the windows 7 installer.  Both either hang early in
  the boot process or enter a reboot loop.  The windows 10 installer
  boots fine.

  I'm launching qemu-kvm through libvirt using virsh.  I'll attach the
  XML file for the virtual machine here, but I tried simplifying it down
  as far as possible and the problem still reproduces.

  I also tried 3.13.0-153 when it became available, but the issue
  remains.

  For now, I've downgraded back to 3.13.0-149 as a work-around, but this
  doesn't seem like a feasible long-term solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jajones2982 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jul  9 10:19:31 2018
  HibernationDevice: RESUME=UUID=305bcf8e-aef9-4db2-b918-60c1298edd59
  InstallationDate: Installed on 2014-08-28 (1410 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=4ebf72df-8d67-4a16-ac60-022899788a4f ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-D3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780829/+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 1780829] [NEW] linux 3.13.0-151 causes win7 qemu-KVM VM to fail boot

[James Jones]

Public bug reported:

After my system was upgraded from linux 3.13.0-149 -> 3.13.0-151, my
windows 7 virtual machine fails to boot.  I tried both my existing disk
image, and the windows 7 installer.  Both either hang early in the boot
process or enter a reboot loop.  The windows 10 installer boots fine.

I'm launching qemu-kvm through libvirt using virsh.  I'll attach the XML
file for the virtual machine here, but I tried simplifying it down as
far as possible and the problem still reproduces.

I also tried 3.13.0-153 when it became available, but the issue remains.

For now, I've downgraded back to 3.13.0-149 as a work-around, but this
doesn't seem like a feasible long-term solution.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-149-generic 3.13.0-149.199
ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
Uname: Linux 3.13.0-149-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jajones2982 F pulseaudio
CurrentDesktop: KDE
Date: Mon Jul  9 10:19:31 2018
HibernationDevice: RESUME=UUID=305bcf8e-aef9-4db2-b918-60c1298edd59
InstallationDate: Installed on 2014-08-28 (1410 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=4ebf72df-8d67-4a16-ac60-022899788a4f ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-149-generic N/A
 linux-backports-modules-3.13.0-149-generic  N/A
 linux-firmware  1.127.24
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-D3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug trusty

** Attachment added: "libvirt VM definition"
   https://bugs.launchpad.net/bugs/1780829/+attachment/5161481/+files/win7.xml

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

Title:
  linux 3.13.0-151 causes win7 qemu-KVM VM to fail boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After my system was upgraded from linux 3.13.0-149 -> 3.13.0-151, my
  windows 7 virtual machine fails to boot.  I tried both my existing
  disk image, and the windows 7 installer.  Both either hang early in
  the boot process or enter a reboot loop.  The windows 10 installer
  boots fine.

  I'm launching qemu-kvm through libvirt using virsh.  I'll attach the
  XML file for the virtual machine here, but I tried simplifying it down
  as far as possible and the problem still reproduces.

  I also tried 3.13.0-153 when it became available, but the issue
  remains.

  For now, I've downgraded back to 3.13.0-149 as a work-around, but this
  doesn't seem like a feasible long-term solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-149-generic 3.13.0-149.199
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jajones2982 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jul  9 10:19:31 2018
  HibernationDevice: RESUME=UUID=305bcf8e-aef9-4db2-b918-60c1298edd59
  InstallationDate: Installed on 2014-08-28 (1410 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=4ebf72df-8d67-4a16-ac60-022899788a4f ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   0: hci0: Bluetooth

[Kernel-packages] [Bug 1780681] Re: Older version in bionic than in artful

[Launchpad Bug Tracker]

This bug was fixed in the package libvorbisidec -
1.0.2+svn18153-1+deb9u1build0.18.04.1

---
libvorbisidec (1.0.2+svn18153-1+deb9u1build0.18.04.1) bionic-security; 
urgency=medium

  * No change rebuild to bump version higher than artful (LP: #1780681)

 -- Marc Deslauriers   Mon, 09 Jul 2018
10:22:06 -0400

** Changed in: libvorbisidec (Ubuntu)
   Status: New => Fix Released

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

Title:
  Older version in bionic than in artful

Status in libvorbisidec package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  These packages have an older version in bionic than in artful:

  libvorbisidec 1.0.2+svn18153-1+deb9u1 < 1.0.2+svn18153-1+deb9u1build0.17.10.1
  nvidia-graphics-drivers-384 384.111-0ubuntu1 < 384.130-0ubuntu0.17.10.1

  The latter is older than in xenial, too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780680.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvorbisidec/+bug/1780681/+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 1715552] Re: VMWare does not start

[iLugo]

@Michael Harmon, you are very welcome.
I can confirm that my above procedure also works for Workstation Pro 14.1.2.

>> Updated instructions to successfully install Workstation Pro 14.1.2
in (K)ubuntu 18.04

1. Do the normal installation of VMWare Workstation. Do not run vmware
yet. It will fail anyway.

2. Do a git clone (or download as zip package) of the vmware-host-
modules project hosted in https://github.com/mkubecek/vmware-host-
modules.  Make sure to read the README to understand what branch you
need to  checkout. Detailed instructions for doing this is in the
INSTALL  document. For example: If you are installing Workstation
14.1.2, then  you'd do:

git clone https://github.com/mkubecek/vmware-host-modules.git
cd vmware-host-modules
git checkout workstation-14.1.2

 (This project is recommended by:
https://wiki.archlinux.org/index.php/VMware#Kernel_modules).

3. cd to the git repo dir (vmware-host-modules) and follow the  instructions in 
the INSTALL document of the project to "Build and  install modules - DIRECTLY", 
i.e., the section "2a." as of this writing.  This is important, as it will 
ensure that your modules are build  specifically for your CURRENT kernel. 
Follow all the steps carefully.
For example: In my case, I want to build and install modules against my 
current kernel, so I just need to issue this command -from the directory to 
which I cd before:

   make && sudo make install

You are NOT done yet! If you run vmware at this point, you will get the
error that this bug mentions. Next step, you'll fix it.

4. Enter the following sequence of commands in the console:
cd /usr/lib/vmware/lib/libz.so.1
 sudo mv libz.so.1 libz.so.1.old
 sudo ln -s /lib/x86_64-linux-gnu/libz.so.1 .
 sudo depmod -a
 sudo /etc/init.d/vmware restart

5. If all went OK, you should be ready by know. VMware Workstation (at
least 14.1.2 on (K)Ubuntu 18.04) now should work.

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

[Sujith Pandel]

** Attachment added: "dmesg - test-kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779605/+attachment/5161476/+files/dmesg-test-kernel.txt

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

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

[Sujith Pandel]

Verified the test-kernel shared in the above link on the same setup
where the issue was seen with bionic kernels.

Uploading dmesg.

Issue seems to be fixed and change observed now is:

[0.229581] Detected 1 PCC Subspaces
[0.229581] Registering PCC driver as Mailbox controller

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

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1780806] UdevDb.txt

[Arto Teräs]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1780806/+attachment/5161440/+files/UdevDb.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161441/+files/WifiSyslog.txt

** 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/1780806

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161433/+files/ProcCpuinfo.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161435/+files/ProcEnviron.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1780806/+attachment/5161431/+files/Lspci.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161438/+files/PulseList.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161434/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161436/+files/ProcInterrupts.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1780806/+attachment/5161432/+files/Lsusb.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1780806/+attachment/5161439/+files/RfKill.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161437/+files/ProcModules.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

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

[Arto Teräs]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161430/+files/IwConfig.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780806/+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 1780817] [NEW] kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)

[Louis Bouchard]

Public bug reported:

When starting a nested VM in a Bionic VM, the "host" VM kernel panics
following a simple drop to QEMU monitor by hitting A-c. For some
reason kdump is unable to capture the kernel panic so I only have a
screen capture of the panic.

It also happens on the latest mainline kernel(4.18-rc4). It is fairly
trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the
following :

qemu-system-x86_64 -enable-kvm \
-name balloontest \
-display none \
-monitor none \
-nographic \
-nodefaults \
-m 2048M \
-serial mon:stdio \
-smp 2 \
-cpu host \
-drive 
if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \
-drive 
if=pflash,format=raw,file=/home/caribou/balloon/efi.vars

Use A-c to drop to QEMU monitor and .

^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[  
267.784299] general protection fault:  [#1] SMP PTI
[  267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
[  267.804312]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
[  267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
[  267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[  267.811666] RIP: 0010:native_write_cr4+0x4/0x10
[  267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006
[  267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8
[  267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0
[  267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: 
[  267.818625] R10:  R11:  R12: 00025040
[  267.820130] R13: 0001 R14:  R15: 
[  267.821638] FS:  () GS:8c01ffd8() 
knlGS:
[  267.823352] CS:  0010 DS:  ES:  CR0: 80050033
[  267.824592] CR2:  CR3: 00058c00a006 CR4: 003626e0
[  267.826108] DR0:  DR1:  DR2: 
[  267.827567] DR3:  DR6: fffe0ff0 DR7: 0400
[  267.828973] Call Trace:
[  267.829470]  
[  267.829893]  hardware_disable+0xaa/0xc0 [kvm_intel]
[  267.830897]  kvm_arch_hardware_disable+0x19/0x40 [kvm]
[  267.831928]  hardware_disable_nolock+0x2b/0x30 [kvm]
[  267.832912]  flush_smp_call_function_queue+0x4c/0xf0
[  267.833911]  generic_smp_call_function_single_interrupt+0x13/0x30
[  267.835121]  smp_call_function_interrupt+0x36/0xd0
[  267.836069]  call_function_interrupt+0x84/0x90
[  267.836950]  
[  267.837396] RIP: 0010:native_safe_halt+0x6/0x10
[  267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: 
ff03
[  267.839698] RAX: acd97150 RBX: 0006 RCX: 
[  267.840978] RDX:  RSI:  RDI: 
[  267.842258] RBP: a2e1431afe80 R08: 0002 R09: 
[  267.843554] R10: 00b3 R11: 00a6 R12: 0006
[  267.844826] R13:  R14:  R15: 
[  267.846107]  ? __cpuidle_text_start+0x8/0x8
[  267.846875]  default_idle+0x20/0x100
[  267.847533]  arch_cpu_idle+0x15/0x20
[  267.848186]  default_idle_call+0x23/0x30
[  267.848917]  do_idle+0x172/0x1f0
[  267.849516]  cpu_startup_entry+0x73/0x80
[  267.850255]  start_secondary+0x1ab/0x200
[  267.850971]  secondary_startup_64+0xa5/0xb0
[  267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 
00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 
e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0>
[  267.854894] RIP: native_write_cr4+0x4/0x10 RSP: 8c01ffd83f48
[  268.848104] invalid opcode:  [#2] SMP PTI
[  268.848524] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
[  268.854013]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
[  268.855212] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
[  268.855790] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[  268.856438] RIP: 0010:native_machine_crash_shutdown+0x136/0x190
[  268.856893] RSP: 0018:8c01ffd83cc0 EFLAGS: 00010002
[  268.857295] RAX: 

[Kernel-packages] [Bug 1780806] CurrentDmesg.txt

[Arto Teräs]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161429/+files/CurrentDmesg.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780806/+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 1780817] Missing required logs.

[Ubuntu Kernel Bot]

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 1780817

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

Title:
  kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When starting a nested VM in a Bionic VM, the "host" VM kernel panics
  following a simple drop to QEMU monitor by hitting A-c. For some
  reason kdump is unable to capture the kernel panic so I only have a
  screen capture of the panic.

  It also happens on the latest mainline kernel(4.18-rc4). It is fairly
  trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the
  following :

  qemu-system-x86_64 -enable-kvm \
  -name balloontest \
  -display none \
  -monitor none \
  -nographic \
  -nodefaults \
  -m 2048M \
  -serial mon:stdio \
  -smp 2 \
  -cpu host \
  -drive 
if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \
  -drive 
if=pflash,format=raw,file=/home/caribou/balloon/efi.vars

  Use A-c to drop to QEMU monitor and .

  ^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[  
267.784299] general protection fault:  [#1] SMP PTI
  [  267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
  [  267.804312]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
  [  267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
  [  267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), 
BIOS 0.0.0 02/06/2015
  [  267.811666] RIP: 0010:native_write_cr4+0x4/0x10
  [  267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006
  [  267.813960] RAX: 003626e0 RBX: 0046 RCX: 
8c01ffd8
  [  267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 
003606e0
  [  267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: 

  [  267.818625] R10:  R11:  R12: 
00025040
  [  267.820130] R13: 0001 R14:  R15: 

  [  267.821638] FS:  () GS:8c01ffd8() 
knlGS:
  [  267.823352] CS:  0010 DS:  ES:  CR0: 80050033
  [  267.824592] CR2:  CR3: 00058c00a006 CR4: 
003626e0
  [  267.826108] DR0:  DR1:  DR2: 

  [  267.827567] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  267.828973] Call Trace:
  [  267.829470]  
  [  267.829893]  hardware_disable+0xaa/0xc0 [kvm_intel]
  [  267.830897]  kvm_arch_hardware_disable+0x19/0x40 [kvm]
  [  267.831928]  hardware_disable_nolock+0x2b/0x30 [kvm]
  [  267.832912]  flush_smp_call_function_queue+0x4c/0xf0
  [  267.833911]  generic_smp_call_function_single_interrupt+0x13/0x30
  [  267.835121]  smp_call_function_interrupt+0x36/0xd0
  [  267.836069]  call_function_interrupt+0x84/0x90
  [  267.836950]  
  [  267.837396] RIP: 0010:native_safe_halt+0x6/0x10
  [  267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: 
ff03
  [  267.839698] RAX: acd97150 RBX: 0006 RCX: 

  [  267.840978] RDX:  RSI:  RDI: 

  [  267.842258] RBP: a2e1431afe80 R08: 0002 R09: 

  [  267.843554] R10: 00b3 R11: 00a6 R12: 
0006
  [  267.844826] R13:  R14:  R15: 

  [  267.846107]  ? __cpuidle_text_start+0x8/0x8
  [  267.846875]  default_idle+0x20/0x100
  [  267.847533]  arch_cpu_idle+0x15/0x20
  [  267.848186]  default_idle_call+0x23/0x30
  [  267.848917]  do_idle+0x172/0x1f0
  [  267.849516]  cpu_startup_entry+0x73/0x80
  [  267.850255]  start_secondary+0x1ab/0x200
  [  267.850971]  secondary_startup_64+0xa5/0xb0
  [ 

[Kernel-packages] [Bug 1780806] CRDA.txt

[Arto Teräs]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1780806/+attachment/5161428/+files/CRDA.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Sony Corporation SVS1511C5E
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
  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-07-08 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi.product.version: C60AVZAU
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780806/+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 1780806] Re: Kernel 4.15.0 fails to boot with linux-modules-extra

[Arto Teräs]

apport information

** Tags added: apport-collected bionic

** Description changed:

  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM, NVIDIA
  GK107M / GeForce GT 640M LE, original hard disk changed to a Crucial
  SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade process
  went smoothly without issues.
  
  After upgrade, I cannot boot the new kernel version 4.15.0-23 in normal
  mode. The boot process hangs immediately after displaying "Loading
  initial ramdisk". In case I choose "Recovery mode", the system does boot
  successfully with the same kernel. I also tried installing kernels
  4.15.0-22 and 4.15.0-24, which both behave identically.
  
  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal mode.
  However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".
  
- The previous kernel 4.13.0-46 (with linux-modules-extra installed) works
- without problems and the display is recognized correctly.
+ The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  arto   2916 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
+ InstallationDate: Installed on 2017-10-18 (263 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
+ MachineType: Sony Corporation SVS1511C5E
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset
+ 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-07-08 (0 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/17/2012
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: R0142C5
+ dmi.board.asset.tag: N/A
+ dmi.board.name: VAIO
+ dmi.board.vendor: Sony Corporation
+ dmi.board.version: N/A
+ dmi.chassis.asset.tag: N/A
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Sony Corporation
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
+ dmi.product.family: VAIO
+ dmi.product.name: SVS1511C5E
+ dmi.product.version: C60AVZAU
+ dmi.sys.vendor: Sony Corporation

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1780806/+attachment/5161427/+files/AlsaInfo.txt

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed) works 
without problems and the display is recognized correctly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   2916 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71
  InstallationDate: Installed on 2017-10-18 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - 

[Kernel-packages] [Bug 1780809] Re: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.

[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 wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1780809

Title:
  package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade:
  trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is
  also in package crda 3.18-0ubuntu1

Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  A requirement of update appeared and I've just accepted it. But during
  the process of installation, a failure happened. It seems to refer to
  the wireless register.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: wireless-regdb 2016.06.10-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Jul  9 11:58:30 2018
  Dependencies:
   
  DuplicateSignature:
   package:wireless-regdb:2016.06.10-0ubuntu1
   Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over 
(2016.06.10-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-04WWLs/56-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb
 (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package crda 3.18-0ubuntu1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package crda 3.18-0ubuntu1
  InstallationDate: Installed on 2017-09-03 (308 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: wireless-regdb
  Title: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: 
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in 
package crda 3.18-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1780809/+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 1765373] Re: nfp: flower: fixes for cmesg processing timeouts

[Simon Horman]

Hi,

I apologise that I am a little unsure of the process here.
This is a rather severe bug from a Netronome point of view which has now been 
fixed upstream.
Is there a procedure available for backports to be included in an updated 
Bionic kernel?

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

Title:
  nfp: flower: fixes for cmesg processing timeouts

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS

  This patch-set improves MTU handling for flower offload on Netronome 
SmartNICs.
  The max MTU is correctly capped and physical port MTU is communicated to the 
FW
  (and indirectly HW). This prevents the driver from incorrectly reporting a 
larger
  MTU than the HW is configured to handle.

  The upstream commits, accepted for v4.17, are:
  29a5dcae2790 ("nfp: flower: offload phys port MTU change")
  167cebeffadd ("nfp: modify app MTU setting callbacks")

  There are also a dependencies on:
  ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit 
when active")
  b57b62139e53 ("nfp: flower: read extra feature support from fw")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+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 1780806] Missing required logs.

[Ubuntu Kernel Bot]

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 1780806

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

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed)
  works without problems and the display is recognized correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780806/+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 1780809] [NEW] package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda

[Lucas da Silva Lopes]

Public bug reported:

A requirement of update appeared and I've just accepted it. But during
the process of installation, a failure happened. It seems to refer to
the wireless register.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: wireless-regdb 2016.06.10-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Mon Jul  9 11:58:30 2018
Dependencies:
 
DuplicateSignature:
 package:wireless-regdb:2016.06.10-0ubuntu1
 Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over 
(2016.06.10-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-04WWLs/56-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb
 (--unpack):
  trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package crda 3.18-0ubuntu1
ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package crda 3.18-0ubuntu1
InstallationDate: Installed on 2017-09-03 (308 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: wireless-regdb
Title: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: 
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in 
package crda 3.18-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict zesty

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

Title:
  package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade:
  trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is
  also in package crda 3.18-0ubuntu1

Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  A requirement of update appeared and I've just accepted it. But during
  the process of installation, a failure happened. It seems to refer to
  the wireless register.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: wireless-regdb 2016.06.10-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Jul  9 11:58:30 2018
  Dependencies:
   
  DuplicateSignature:
   package:wireless-regdb:2016.06.10-0ubuntu1
   Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over 
(2016.06.10-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-04WWLs/56-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb
 (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package crda 3.18-0ubuntu1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package crda 3.18-0ubuntu1
  InstallationDate: Installed on 2017-09-03 (308 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: wireless-regdb
  Title: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: 
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in 
package crda 3.18-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1780809/+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 1780806] [NEW] Kernel 4.15.0 fails to boot with linux-modules-extra

[Arto Teräs]

Public bug reported:

I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM, NVIDIA
GK107M / GeForce GT 640M LE, original hard disk changed to a Crucial
SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade process
went smoothly without issues.

After upgrade, I cannot boot the new kernel version 4.15.0-23 in normal
mode. The boot process hangs immediately after displaying "Loading
initial ramdisk". In case I choose "Recovery mode", the system does boot
successfully with the same kernel. I also tried installing kernels
4.15.0-22 and 4.15.0-24, which both behave identically.

The problem seems to be related to the linux-modules-extra package. If
the package is not installed, the system boots also in the normal mode.
However, the display is not correctly recognized, it shows up as
"Unknown display" with 1024x768 resolution. That also happens if I
choose "Recovery mode" and "Resume boot".

The previous kernel 4.13.0-46 (with linux-modules-extra installed) works
without problems and the display is recognized correctly.

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

** Package changed: openshot (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/1780806

Title:
  Kernel 4.15.0 fails to boot with linux-modules-extra

Status in linux package in Ubuntu:
  New

Bug description:
  I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM,
  NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a
  Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade
  process went smoothly without issues.

  After upgrade, I cannot boot the new kernel version 4.15.0-23 in
  normal mode. The boot process hangs immediately after displaying
  "Loading initial ramdisk". In case I choose "Recovery mode", the
  system does boot successfully with the same kernel. I also tried
  installing kernels 4.15.0-22 and 4.15.0-24, which both behave
  identically.

  The problem seems to be related to the linux-modules-extra package. If
  the package is not installed, the system boots also in the normal
  mode. However, the display is not correctly recognized, it shows up as
  "Unknown display" with 1024x768 resolution. That also happens if I
  choose "Recovery mode" and "Resume boot".

  The previous kernel 4.13.0-46 (with linux-modules-extra installed)
  works without problems and the display is recognized correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780806/+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 1780806] [NEW] Kernel 4.15.0 fails to boot with linux-modules-extra

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM, NVIDIA
GK107M / GeForce GT 640M LE, original hard disk changed to a Crucial
SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade process
went smoothly without issues.

After upgrade, I cannot boot the new kernel version 4.15.0-23 in normal
mode. The boot process hangs immediately after displaying "Loading
initial ramdisk". In case I choose "Recovery mode", the system does boot
successfully with the same kernel. I also tried installing kernels
4.15.0-22 and 4.15.0-24, which both behave identically.

The problem seems to be related to the linux-modules-extra package. If
the package is not installed, the system boots also in the normal mode.
However, the display is not correctly recognized, it shows up as
"Unknown display" with 1024x768 resolution. That also happens if I
choose "Recovery mode" and "Resume boot".

The previous kernel 4.13.0-46 (with linux-modules-extra installed) works
without problems and the display is recognized correctly.

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

-- 
Kernel 4.15.0 fails to boot with linux-modules-extra
https://bugs.launchpad.net/bugs/1780806
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 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Wui Chia]

This issue didn't go away even I'm on 4.15.0-24.26

-- 
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'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By 

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Manoj Iyer]

Kernel team, looks like the root cause identified by IBM (taken from
description of the bug) is:

== Comment: #8 - Hari Krishna Bathini <> - 2018-06-26 06:06:13 ==
The dump target (/var/crash) is on NVMe device (also, the root disk).
But the kdump initrd is not being built with nvme driver modules.
Eventually, nvme disk is not found and kdump kernel is hitting the
initramfs shell. Using the default initrd, which has the nvme driver
modules included, dump was captured successfully.

Can someone from Canonical take a look at this and comment on why
nvme modules are not included in kdump initrd despite it being the
root disk..

Thanks
Hari

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Colin Watson]

** Project changed: debian-installer => debian-installer (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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh
  

[Kernel-packages] [Bug 1776389] Re: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)

[Manoj Iyer]

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-
  jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 ==
  Problem:
  
  Injecting error multiple times causes kernel crash.

  echo 0x0:1:4:0x60800:0xfff8 >
  /sys/kernel/debug/powerpc/PCI/err_injct

  EEH: PHB#0 failure detected, location: N/A
  EEH: PHB#0-PE#0 has failed 6 times in the
  last hour and has been permanently disabled.
  EEH: Unable to recover from failure from PHB#0-PE#0.
  Please try reseating or replacing it
  ixgbe :01:00.1: Adapter removed
  kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352!
  Oops: Exception in kernel mode, sig: 5 [#1]
  LE SMP NR_CPUS=2048 NUMA PowerNV
  Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds 
mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf 
ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq 
vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser 
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx 
ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect 
sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum 
drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio
  CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu
  NIP:  c077f080 LR: c077f070 CTR: c00aac30
  REGS: c00ff1deb5a0 TRAP: 0700   Not tainted  (4.15.0-10-generic)
  MSR:  90029033   CR: 24002822  XER: 2004
  CFAR: c018bddc SOFTE: 1
  GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00
  GPR04: 02c5   
  GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488
  GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0
  GPR16:    
  GPR20:    c0f48d10
  GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000
  GPR28: c000200e4fcf4288 c00810624480  c00fbb633ea0
  NIP [c077f080] free_msi_irqs+0xa0/0x260
  LR [c077f070] free_msi_irqs+0x90/0x260
  Call Trace:
  [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable)
  [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170
  [c00ff1deb8c0] [c0081060b5c8] 
ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe]
  [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe]
  [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110
  [c00ff1deb9d0] [c085d194] 
device_release_driver_internal+0x224/0x310
  [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0
  [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40
  [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130
  [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130
  [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580
  [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338
  [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200
  [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0
  [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4
  Instruction dump:
  419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d
  6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4
  ---[ end trace 23c446a470e60864 ]---
  ixgbe :01:00.0: Adapter removed

  Sending IPI to other CPUs
  OPAL: Switch to big-endian OS
  OPAL: Switch to little-endian OS
  PHB#[0:0]: eeh_freeze_clear on fenced PHB

   
  ---uname output---
  Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 
18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston-LC 

  :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1]
  :01:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network 

[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Manoj Iyer]

Looks like the patch mentioned in this bug is already present in bionic

0a835c4f090a Reimplement IDR and IDA using the radix tree

Closing out the bionic track as fix released.

** Changed in: crash (Ubuntu Bionic)
   Status: In Progress => Fix Released

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels (hwe-edge on xenial, for 
example; or the standard bionic kernel).

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.

  [Regression Potential]
  Analysis of crashed kernels will require that the crash file be moved to a 
system where crash doesn't have the regression. The patch, however, should 
touch only the broken command, and has been tested.

  -

  
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  files  mach   

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Manoj Iyer]

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-power-systems
   Importance: High => Critical

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Andrew Cloke]

** Tags removed: triage-g
** Tags added: triage-r

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Andrew Cloke]

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in debian-installer:
  New
Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Andrew Cloke]

Re-assigning to Foundations to comment on Manoj's proposal in comment #3. If a 
different resolution is preferred, could the Foundations team clarify what that 
would be?
Thanks.

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in debian-installer:
  New
Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Manoj Iyer]

** Also affects: debian-installer
   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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in debian-installer:
  New
Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh
  Jul  2 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Manoj Iyer]

in bionic mpt3sas is in message-modules

debian.master$ find d-i/ -type f | xargs grep mpt3sas
d-i/modules/message-modules:mpt3sas ?

but message-modules is not in build/pkg-lists/netboot/ppc64el.cfg I
believe d-i needs to include the udeb for message-modules and rebuilt?

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

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in debian-installer:
  New
Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded