[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.

[Ryan C. Underwood]

If you're using zfs-auto-snapshot, you can tell it to ignore bpool by
setting the com.sun:auto-snapshot property to false on the bpool
dataset:

# zfs set com.sun:auto-snapshot=false bpool

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

Title:
  Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
  snapshot of bpool.

Status in grub2 package in Ubuntu:
  Confirmed
Status in grub2-unsigned package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  There is an upstream Bug with Grub where if you create snapshots of bpool, it 
results in a non-booting System. The problem was found to be an upstream Bug 
with Grub2:
  https://savannah.gnu.org/bugs/index.php?64297

  Multiple Ubuntu 22.04.3 Users Affected:
  https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
  https://ubuntuforums.org/showthread.php?t=2494957

  Brought up as an issue at OpenZFS:
  https://github.com/openzfs/zfs/issues/13873

  If you look at this comment 
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was 
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
  https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c

  Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
  to Grub2 2.06 so that Users are not caught of in this bug for or
  currently supported LTS Release.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-amd64 2.06-2ubuntu14.4
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Feb  1 16:40:28 2024
  InstallationDate: Installed on 2021-09-23 (861 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: grub2-unsigned
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

[J C Nash]

As far as I can tell, this has now resolved for me. Anyone still having
issues?

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

Title:
  zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
  kernel module.

  Genrated Crash report, but couldn't send it on it's own.

  Error it kept throwing was:
  >>>
  Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
  Loading new zfs-2.1.5 DKMS files...
  Building for 6.2.0-36-generic 6.2.0-37-generic
  Building initial module for 6.2.0-36-generic
  configure: error:
   *** None of the expected "iops->get_acl()" interfaces were detected.
   *** This may be because your kernel version is newer than what is
   *** supported, or you are using a patched custom kernel with
   *** incompatible modifications.
   ***
   *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2
   *** Compatible Kernels: 3.10 - 5.19

  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/zfs-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
  dpkg: error processing package zfs-dkms (--configure):
   installed zfs-dkms package post-installation script subprocess returned 
error exit status 10
  >>>

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Nov 25 21:00:27 2023
  InstallationDate: Installed on 2021-09-23 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago)

  To recreate:
  - Install Ubuntu 22.04.3.
  - Update to current.
  - Install package 'zfs-dkms'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 1909005] Re: [Dell Inspiron 3593] Ubuntu does not resume (wake up) from suspend

[Jonathan C]

3 years is a long time not to fix a basic sleep problem...

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

Title:
  [Dell Inspiron 3593] Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-
  image-5.0.0-1070-oem-osp1". But with this old kernel I run into
  different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

[J C Nash]

My issue with the zfs-dkms bug was raised by Linux Mint update giving an error 
message each time
an upgrade was run. The error message has now stopped appearing. I've not seen 
any news that the
issue is fixed. Does anyone have information that the corrections have migrated 
through from the
upstream repos?   JN

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

Title:
  zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
  kernel module.

  Genrated Crash report, but couldn't send it on it's own.

  Error it kept throwing was:
  >>>
  Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
  Loading new zfs-2.1.5 DKMS files...
  Building for 6.2.0-36-generic 6.2.0-37-generic
  Building initial module for 6.2.0-36-generic
  configure: error:
   *** None of the expected "iops->get_acl()" interfaces were detected.
   *** This may be because your kernel version is newer than what is
   *** supported, or you are using a patched custom kernel with
   *** incompatible modifications.
   ***
   *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2
   *** Compatible Kernels: 3.10 - 5.19

  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/zfs-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
  dpkg: error processing package zfs-dkms (--configure):
   installed zfs-dkms package post-installation script subprocess returned 
error exit status 10
  >>>

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Nov 25 21:00:27 2023
  InstallationDate: Installed on 2021-09-23 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago)

  To recreate:
  - Install Ubuntu 22.04.3.
  - Update to current.
  - Install package 'zfs-dkms'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2043469] Re: Low-latency kernel can't boot to desktop

[Henry C. Gernhardt, III]

TL;DR:  Something's missing an install hook, and I don't know what needs
it.

I had this one bite me in the posterior just this morning.  Here's what
I've discovered seems to be happening.  When installing the lowlatency
kernel tree on a fresh install with NVidia drivers, the hook that
triggers `nvidia-driver-*` to recompile its kernel module doesn't
happen.  I tried doing a `sudo apt install --reinstall nvidia-
driver-535` to force it to do so on my system, but the hook still didn't
seem to run.

I rebooted to the lowlatency kernel and worked from tty1.  I installed
`nvidia-driver-525` which pulled down `gcc-12-base`, `cpp-12`,
`libgcc-12-dev`, `gcc-12`, and `dkms` as well as the`libnvidia-*` items
needed for building the kernel module.  It then proceeded to do so for
the active kernels.  Onde `dkms` had been called and the nvidia driver
kernel module activated, the desktop came to life.

At this point, installing `nvidia-driver-535` resulted in a kernel
module compilation and install.  Everything now works fine.

I have no idea where this needs to go from here.

Thanks, all!

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

Title:
  Low-latency kernel can't boot to desktop

Status in linux-meta-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  23.10 fresh install. Generic kernel boots without problems. lowlatency
  can't boot to desktop, it gets stuck and shows black screen with
  cursor blinking.

  The same PC worked yesterday with 23.04 and low latency without
  problems. I have been running lowlatency kernel in this machine for a
  couple of years, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-lowlatency 6.5.0.10.10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 12:25:24 2023
  InstallationDate: Installed on 2023-11-13 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: linux-meta-lowlatency
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/2043469/+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 2042546] Re: Include cifs.ko in linux-modules package

[C de-Avillez]

removed modules-extra, rebooted, and installed the new kernel for Azure;
then rebooted again.

modprobe cifs works, and modules-extra is not installed. Marking
verification done for Azure.


** Tags removed: verification-needed-jammy-linux-hwe-6.2
** Tags added: verification-done-jammy-linux-hwe-6.2

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

Title:
  Include cifs.ko in linux-modules package

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2042092] Re: CIFS module is not included in 6.2.0-1016

[C de-Avillez]

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

** This bug has been marked a duplicate of bug 2042546
   Include cifs.ko in linux-modules package

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.

  WORKAROUND: cifs.ko is provided in the linux-modules-extra-azure (as
  noted in comment #7); a 'sudo apt install linux-modules-extra-azure'
  will add it in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042092/+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 2042092] Re: CIFS module is not included in 6.2.0-1016

[C de-Avillez]

given cifs.ko (and associated kmods) is now in modules-extra... was this
an oversight, or is it where it will be from now on?

Added a WORKAROUND to the description, thank you Jean-Francois.

** Description changed:

  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.
+ 
+ WORKAROUND: cifs.ko is provided in the linux-modules-extra-azure (as
+ noted in comment #7); a 'sudo apt install linux-modules-extra-azure'
+ will add it in.

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

Title:
  CIFS module is not included in 6.2.0-1016

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Between 6.2.0-1015 and 6.2.0-1016, the CIFS module was moved from
  fs/cifs/* to fs/smb/client/*, fs/smb/common/* and fs/smb/server/*. The
  inclusion list (root/debian.azure-6.2/control.d/azure.inclusion-list)
  was not updated for this change, so the module is not included in the
  linux-modules-6.2.0-1026-azure package.

  WORKAROUND: cifs.ko is provided in the linux-modules-extra-azure (as
  noted in comment #7); a 'sudo apt install linux-modules-extra-azure'
  will add it in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042092/+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 2037768] Re: Laptop internal keyboard not working on ASUS Vivobook Go E1504GA

[Matt C]

I have built a custom patched kernel 6.5.0-5-generic (#5, 6.5.0-5.5) on this 
hardware, running on mantic 
 (development branch) and I can confirm that the linked patch makes the 
internal keyboard work as expected.

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

Title:
   Laptop internal keyboard not working on ASUS Vivobook Go E1504GA

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On laptop model ASUS Vivobook 15 Go E1504GA the internal keyboard
  doesn't work on Ubuntu Linux 23.04 and 23.10 Beta. Typing has no
  effect.

  A kernel bug has been filed for this issue, 217660:
  https://bugzilla.kernel.org/show_bug.cgi?id=217660

  This issue has been experienced for other laptops, including other
  Vivobooks (see related kernel bug 216158). After running:

  cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
  iasl -d dsdt.dat
  grep -A 40 PS2K dsdt.dsl | grep IRQ -A 1

  I got the output:

  IRQ (Level, ActiveLow, Exclusive, )
  {1}

  This seems to be the same bug as the one linked above which has a
  patch for a list of other models.

  I have also verified the issue still exists on recent mainline
  kernels:

  linux-image-6.5.0-5-generic 6.5.0-5.5 amd64
  linux-image-unsigned-6.5.0-060500-generic6.5.0-060500.202308271831 amd64
  linux-image-unsigned-6.5.5-060505-generic6.5.5-060505.202309230703 amd64
  linux-image-unsigned-6.6.0-060600rc3-generic 6.6.0-060600rc3.202309242231 
amd64

  I think this model needs adding to the quirks list in the keyboard IRQ
  fix patch on kernel bug 216158. Other users have tested the patch with
  this model added and it worked.
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  Other blocking Ubuntu issues for this model:
    * The Ubuntu 23.04 installer partitioning tool misdetects the sector size 
of the 256GB SkHynix M.2 SSD as 512 bytes instead of 4096 bytes, so fails to 
install
    * The Ubuntu 23.10 beta installer partitioning tool is different (like 
gparted), correctly detects the sector size, thus installation is successful. 
However on boot the OS drops to the emergency initrd shell and cannot find the 
root volume. Adding missing modules ufshcd, ufshcd_pci to 
/etc/initramfs-tools/modules and rebuilding initrd resolves this problem
    * Wi-Fi and Bluetooth for this laptop is not supported yet in the kernel: 
MediaTek mt7902 (AzureWave Device 5520)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1793 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Sep 29 23:41:46 2023
  InstallationDate: Installed on 2023-09-26 (4 days ago)
  InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Beta amd64 
(20230925)
  IwConfig:
   lono wireless extensions.

   enx00249b295e86  no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=UUID=98d305e7-5c6d-4a8a-af45-d2357ea3c3bd 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:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E1504GA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E1504GA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 254.222
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1504GA.301:bd04/28/2023:br5.27:efr254.222:svnASUSTeKCOMPUTERINC.:pnVivobookGoE1504GA_E1504GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE1504GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: Vivobook Go E1504GA_E1504GA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 2037768] Re: Laptop internal keyboard not working on ASUS Vivobook Go E1504GA

[Matt C]

** Description changed:

- On laptop model ASUS Vivobook Go E1504GA the internal keyboard doesn't
- work on Ubuntu Linux 23.04 and 23.10 Beta. Typing has no effect.
+ On laptop model ASUS Vivobook 15 Go E1504GA the internal keyboard
+ doesn't work on Ubuntu Linux 23.04 and 23.10 Beta. Typing has no effect.
  
  A kernel bug has been filed for this issue, 217660:
  https://bugzilla.kernel.org/show_bug.cgi?id=217660
  
  This issue has been experienced for other laptops, including other
  Vivobooks (see related kernel bug 216158). After running:
  
  cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
  iasl -d dsdt.dat
  grep -A 40 PS2K dsdt.dsl | grep IRQ -A 1
  
  I got the output:
  
  IRQ (Level, ActiveLow, Exclusive, )
  {1}
  
  This seems to be the same bug as the one linked above which has a patch
  for a list of other models.
  
  I have also verified the issue still exists on recent mainline kernels:
  
  linux-image-6.5.0-5-generic 6.5.0-5.5 amd64
  linux-image-unsigned-6.5.0-060500-generic6.5.0-060500.202308271831 amd64
  linux-image-unsigned-6.5.5-060505-generic6.5.5-060505.202309230703 amd64
  linux-image-unsigned-6.6.0-060600rc3-generic 6.6.0-060600rc3.202309242231 
amd64
  
  I think this model needs adding to the quirks list in the keyboard IRQ
  fix patch on kernel bug 216158. Other users have tested the patch with
  this model added and it worked.
  https://bugzilla.kernel.org/show_bug.cgi?id=216158
  
  Other blocking Ubuntu issues for this model:
    * The Ubuntu 23.04 installer partitioning tool misdetects the sector size 
of the 256GB SkHynix M.2 SSD as 512 bytes instead of 4096 bytes, so fails to 
install
    * The Ubuntu 23.10 beta installer partitioning tool is different (like 
gparted), correctly detects the sector size, thus installation is successful. 
However on boot the OS drops to the emergency initrd shell and cannot find the 
root volume. Adding missing modules ufshcd, ufshcd_pci to 
/etc/initramfs-tools/modules and rebuilding initrd resolves this problem
    * Wi-Fi and Bluetooth for this laptop is not supported yet in the kernel: 
MediaTek mt7902 (AzureWave Device 5520)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1793 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Sep 29 23:41:46 2023
  InstallationDate: Installed on 2023-09-26 (4 days ago)
  InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Beta amd64 
(20230925)
  IwConfig:
   lono wireless extensions.
  
   enx00249b295e86  no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=UUID=98d305e7-5c6d-4a8a-af45-d2357ea3c3bd 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:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E1504GA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E1504GA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 254.222
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1504GA.301:bd04/28/2023:br5.27:efr254.222:svnASUSTeKCOMPUTERINC.:pnVivobookGoE1504GA_E1504GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE1504GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: Vivobook Go E1504GA_E1504GA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
   Laptop internal keyboard not working on ASUS Vivobook Go E1504GA

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On laptop model ASUS Vivobook 15 Go E1504GA the internal keyboard
  doesn't work on Ubuntu Linux 23.04 and 23.10 Beta. Typing has no
  effect.

  A kernel bug has been filed for this issue, 217660:
  

[Kernel-packages] [Bug 2037768] [NEW] Laptop internal keyboard not working on ASUS Vivobook Go E1504GA

[Matt C]

Public bug reported:

On laptop model ASUS Vivobook 15 Go E1504GA the internal keyboard
doesn't work on Ubuntu Linux 23.04 and 23.10 Beta. Typing has no effect.

A kernel bug has been filed for this issue, 217660:
https://bugzilla.kernel.org/show_bug.cgi?id=217660

This issue has been experienced for other laptops, including other
Vivobooks (see related kernel bug 216158). After running:

cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
iasl -d dsdt.dat
grep -A 40 PS2K dsdt.dsl | grep IRQ -A 1

I got the output:

IRQ (Level, ActiveLow, Exclusive, )
{1}

This seems to be the same bug as the one linked above which has a patch
for a list of other models.

I have also verified the issue still exists on recent mainline kernels:

linux-image-6.5.0-5-generic 6.5.0-5.5 amd64
linux-image-unsigned-6.5.0-060500-generic6.5.0-060500.202308271831 amd64
linux-image-unsigned-6.5.5-060505-generic6.5.5-060505.202309230703 amd64
linux-image-unsigned-6.6.0-060600rc3-generic 6.6.0-060600rc3.202309242231 amd64

I think this model needs adding to the quirks list in the keyboard IRQ
fix patch on kernel bug 216158. Other users have tested the patch with
this model added and it worked.
https://bugzilla.kernel.org/show_bug.cgi?id=216158

Other blocking Ubuntu issues for this model:
  * The Ubuntu 23.04 installer partitioning tool misdetects the sector size of 
the 256GB SkHynix M.2 SSD as 512 bytes instead of 4096 bytes, so fails to 
install
  * The Ubuntu 23.10 beta installer partitioning tool is different (like 
gparted), correctly detects the sector size, thus installation is successful. 
However on boot the OS drops to the emergency initrd shell and cannot find the 
root volume. Adding missing modules ufshcd, ufshcd_pci to 
/etc/initramfs-tools/modules and rebuilding initrd resolves this problem
  * Wi-Fi and Bluetooth for this laptop is not supported yet in the kernel: 
MediaTek mt7902 (AzureWave Device 5520)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  matt   1793 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Sep 29 23:41:46 2023
InstallationDate: Installed on 2023-09-26 (4 days ago)
InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Beta amd64 (20230925)
IwConfig:
 lono wireless extensions.

 enx00249b295e86  no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=UUID=98d305e7-5c6d-4a8a-af45-d2357ea3c3bd 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:
 linux-restricted-modules-6.5.0-5-generic N/A
 linux-backports-modules-6.5.0-5-generic  N/A
 linux-firmware   20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E1504GA.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E1504GA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 254.222
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1504GA.301:bd04/28/2023:br5.27:efr254.222:svnASUSTeKCOMPUTERINC.:pnVivobookGoE1504GA_E1504GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE1504GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: Vivobook Go E1504GA_E1504GA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug mantic

** Description changed:

  On laptop model ASUS Vivobook Go E1504GA the internal keyboard doesn't
  work on Ubuntu Linux 23.04 and 23.10 Beta. Typing has no effect.
  
  A kernel bug has been filed for this issue, 217660:
  https://bugzilla.kernel.org/show_bug.cgi?id=217660
  
  This issue has been experienced for other laptops, including other
  Vivobooks (see related kernel bug 216158). After running:
  
  cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
  iasl -d dsdt.dat
  grep -A 40 PS2K dsdt.dsl | grep IRQ -A 1
  
  I got the output:
  
  IRQ (Level, ActiveLow, Exclusive, )
- {1}
+ {1}
  
  This seems to be the same bug as the one linked above which has a patch
  for a list of other models.
  
  I have also verified the 

[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update

[Pierre C. Dussault]

This kernel creates problems for me as well, with rootless podman
commands. See Bug #2026620

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

Title:
  Unrequested kernel update

Status in linux-signed-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+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 2026620] Re: kernel 5.19.0-1010-nvidia-lowlatency issue with rootless podman

[Pierre C. Dussault]

** Summary changed:

- Any podman command in rootless mode does not work. Root usage works fine
+ kernel 5.19.0-1010-nvidia-lowlatency issue with rootless podman

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

** No longer affects: linux-signed-nvidia (Ubuntu)

** Also affects: linux-signed-nvidia-5.19 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  kernel 5.19.0-1010-nvidia-lowlatency issue with rootless podman

Status in libpod package in Ubuntu:
  New
Status in linux-signed-nvidia-5.19 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Podman version 3.4.4+ds1-1ubuntu1.22.04.1

  What I expected to happen: podman commands in rootless mode should
  work.

  What happened instead: podman commands in rootless mode do not work,
  and return an error message that seems to have something to do with
  permissions.

  Whenever I try to type a podman command, such as 
  $ podman info 
  as my regular user, I get:
  cannot clone: Permission denied
  Error: cannot re-exec process

  I have completed the steps in the Rootless Tutorial from the official Podman 
documentation.
  I have all the necessary packages to operate rootless podman.
  I have added valid subuid and subgid range for my user.
  I have user namespaces enabled.
  I can't even run
  $ podman info

  but 
  $ sudo podman info 
  works fine

  If I use 
  $ strace -f podman ps
  I get this error code:
  clone(child_stack=NULL, flags=CLONE_NEWNS|CLONE_NEWUSER|SIGCHLD 

  [pid 18832] <... nanosleep resumed>NULL) = 0
  [pid 18836] <... clone resumed>) = -1 EACCES (Permission denied)

  By searching through the clone(2) man page, EACCES seems to be an
  error code to do with extra restrictions concerning version 2 of
  cgroups. This may be a red herring though.

  I have tried uninstalling, purging, and then reinstalling podman. I
  still have the same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: podman 3.4.4+ds1-1ubuntu1.22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  8 08:28:24 2023
  InstallationDate: Installed on 2022-10-15 (266 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libpod
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2026620/+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 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)

[Daniele C]

I confirm what Lin and Reinhard said. My system can boot -71 if I let
the 30 seconds timer go to zero after rebooting with CTRL+ALT+DEL.

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

Title:
  Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to
  Ryzen APUs)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically
  fails to boot. I see the following error messages:

  "error: cannot allocate kernel buffer
  error: you need to load the kernel first.

  Press any key to continue..._ "

  I am then returned to the GRUB boot menu.

  This has also been experienced by two other AskUbuntu users:
  https://askubuntu.com/questions/1465460/after-kernel-update-error-
  cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme
  appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600.

  In my case, the issue appears to be more likely to occur when I have
  to force-reboot because the system is frozen (due to a separate bug
  which I will link when I can find it again). But I have not yet
  reproduced it.

  Also the log files attached to this report may not contain relevant
  information as the last couple of boots worked correctly. I will try
  to capture a relevant kernel log now that I know this is a kernel
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-71-generic 5.15.0-71.78
  ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92
  Uname: Linux 5.15.0-71-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matthew1288 F pulseaudio
   /dev/snd/controlC0:  matthew1288 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 17:49:11 2023
  InstallationDate: Installed on 2022-01-14 (467 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic 
root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-71-generic N/A
   linux-backports-modules-5.15.0-71-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago)
  dmi.bios.date: 09/28/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.E3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017929/+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 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)

[Daniele C]

Same issues here.

Gigabyte B650 AORUS ELITE AX (Firmware F5b)
AMD Ryzen 9 7900 12-Core Processor

After a few tries / reboot it manages to boot with kernel
5.15.0-71-generic #78-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/2017929

Title:
  Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to
  Ryzen APUs)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically
  fails to boot. I see the following error messages:

  "error: cannot allocate kernel buffer
  error: you need to load the kernel first.

  Press any key to continue..._ "

  I am then returned to the GRUB boot menu.

  This has also been experienced by two other AskUbuntu users:
  https://askubuntu.com/questions/1465460/after-kernel-update-error-
  cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme
  appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600.

  In my case, the issue appears to be more likely to occur when I have
  to force-reboot because the system is frozen (due to a separate bug
  which I will link when I can find it again). But I have not yet
  reproduced it.

  Also the log files attached to this report may not contain relevant
  information as the last couple of boots worked correctly. I will try
  to capture a relevant kernel log now that I know this is a kernel
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-71-generic 5.15.0-71.78
  ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92
  Uname: Linux 5.15.0-71-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matthew1288 F pulseaudio
   /dev/snd/controlC0:  matthew1288 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 17:49:11 2023
  InstallationDate: Installed on 2022-01-14 (467 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic 
root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-71-generic N/A
   linux-backports-modules-5.15.0-71-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago)
  dmi.bios.date: 09/28/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.E3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017929/+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 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error

[C John Klehm]

I was able to work around this by doing 2 things:
* uninstalling the displaylink video driver
* installing nvidia-drivers-530

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

Title:
  Release upgrade to lunar lobster linux-headers-6.2.0-20 post-
  installation error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ended with a dialog box:

  Could not install 'linux-headers-6.2.0-20-generic'

  The upgrade will continue but the 'linux-headers-6.2.0-20-generic'
  package may not be in a working state. Please consider submitting a
  bug report about it.

  installed linux-headers-6.2.0-20-generic package post-installation
  script subprocess returned error exit status 1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 
08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash
   644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 
08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 21 08:09:44 2023
  InstallationDate: Installed on 2021-01-04 (836 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-kitty
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Pierre C. Dussault]

Bump. Still an issue. I am running on a ASUS ROG G751J. For me it has
some weird behaviour depending on if I open the lid after suspend, or if
I just wake it using keyboard and mouse and leave the lid closed (using
a external monitor).

-- 
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:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-kernel-headers package in Ubuntu:
  Confirmed
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: 

Re: [Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use

[Michal C]

I am running LG Gram 16Z90Q (Intel I5) with PopOS and kernel 6.0.6 and I
don't have this issue. Battery lasts half a day, it does not get hot
whether plugged in or not. I had stability issues with Ubuntu, although I
was running the newest release, not the LTS version and I did not have much
time to dig into what is causing it. Then I figured System76 guys are
building OS for laptops so maybe they already did the necessary tricks. And
I fell in love with their tiling windows manager.
The only things that do not work are fingerprint reader and the screen
brightness buttons (they work with huge lag).

śr., 22 lut 2023 o 01:55 Kai-Heng Feng <1987...@bugs.launchpad.net>
napisał(a):

> Please give latest mainline kernel a try:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987829
>
> Title:
>   LG Gram 12gen high CPU use when USB-C/TB is in use
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux package in Fedora:
>   New
>
> Bug description:
>   LG Gram laptop 17Z90Q with a Core i7-1260P CPU.
>
>   Whenever an external monitor is connected to USB-C/Thunderbolt 4,
>   average load goes above 3.0 and the machine is getting very hot.
>
>   Output from top -H shows a lot of kworker CPU usage:
>
>   top - 11:45:06 up 33 min,  2 users,  load average: 3,30, 3,08, 2,79
>   Threads: 1442 total,   2 running, 1440 sleeping,   0 stopped,   0 zombie
>   %Cpu(s):  0,1 us,  3,7 sy,  0,0 ni, 96,1 id,  0,0 wa,  0,0 hi,  0,1 si,
> 0,0 st
>   MiB Mem :  15684,6 total,   8510,2 free,   2580,8 used,   4593,6
> buff/cache
>   MiB Swap:   3815,0 total,   3815,0 free,  0,0 used.  11326,9 avail
> Mem
>
>   PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+
> WCHAN  COMMAND
>  7766 root  20   0   0  0  0 R  19,8   0,0   0:56.05
> worker_th+ kworker/0:2-events
>   196 root  20   0   0  0  0 D  15,8   0,0   1:18.12
> ec_guard   kworker/u32:2+USBC000:00-con0
> 10237 root  20   0   0  0  0 I  12,9   0,0   0:26.44
> worker_th+ kworker/0:0-events
>  1027 root  20   0   0  0  0 I   6,6   0,0   0:43.30
> worker_th+ kworker/1:3-events
> 10971 root  20   0   0  0  0 I   4,0   0,0   0:00.20
> worker_th+ kworker/15:0-events
>   175 root  20   0   0  0  0 I   2,3   0,0   0:03.24
> worker_th+ kworker/11:1-events
>  2410 root  20   0   0  0  0 I   1,7   0,0   0:05.49
> worker_th+ kworker/9:3-events
>
>   Perf shows a lot of time spent inside
>   handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read.
>
>   Additionally, kernel log is getting spammed with these lines every 4
>   seconds (but also without any USB-C device attached):
>
>   [  223.514304] ACPI Error: No handler for Region [XIN1]
> (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130)
>   [  223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no
> handler (20210730/exfldio-261)
>
>   [  223.514337]
>  Initialized Local Variables for Method [_TMP]:
>   [  223.514339]   Local0: 21495082Integer
> 0034
>
>   [  223.514349] No Arguments are initialized for method [_TMP]
>
>   [  223.514354] ACPI Error: Aborting method
>   \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST)
>   (20210730/psparse-529)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: linux-image-5.15.0-46-generic 5.15.0-46.49
>   ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
>   Uname: Linux 5.15.0-46-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  me 1678 F pulseaudio
>/dev/snd/controlC1:  me 1678 F pulseaudio
>   CRDA: N/A
>   CasperMD5CheckResult: pass
>   Date: Fri Aug 26 11:57:05 2022
>   InstallationDate: Installed on 2022-08-25 (1 days ago)
>   InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
> (20220809.1)
>   MachineType: LG Electronics 17Z90Q-G.AA78N
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic
> root=UUID=e2f96916-a67c-432e-b687-730071271216 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:
>linux-restricted-modules-5.15.0-46-generic N/A
>linux-backports-modules-5.15.0-46-generic  N/A
>linux-firmware
>  20220329.g

[Kernel-packages] [Bug 2005689] [NEW] Upgrade Error

[Michael C Donow]

Public bug reported:

Fails on software channels hangs at 150 of 184.

Error string
W:Updating from such a repository can't be done securely, and is therefore 
disabled by default., W:See apt-secure(8) manpage for repository creation and 
user configuration details., E:The repository 
'http://us.archive.ubuntu.com/ubuntu yakkety Release' does not have a Release 
file., W:Updating from such a repository can't be done securely, and is 
therefore disabled by default., W:See apt-secure(8) manpage for repository 
creation and user configuration details., E:The repository 
'http://us.archive.ubuntu.com/ubuntu yakkety-updates Release' does not have a 
Release file.

Please advise.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-137-generic 5.4.0-137.154
ProcVersionSignature: Ubuntu 5.4.0-137.154-generic 5.4.218
Uname: Linux 5.4.0-137-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sans   1710 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb  4 09:38:21 2023
HibernationDevice: RESUME=UUID=2793f083-2d10-4efc-b4b0-4bae5fc7f07a
InstallationDate: Installed on 2017-03-27 (2139 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 3938:1032 MOSART Semi. 2.4G RF Keyboard & Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Shuttle Inc. DH110SE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-137-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-137-generic N/A
 linux-backports-modules-5.4.0-137-generic  N/A
 linux-firmware 1.187.35
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2023-02-04 (0 days ago)
dmi.bios.date: 01/05/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.03
dmi.board.asset.tag: Default string
dmi.board.name: FS110SE
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.03:bd01/05/2018:svnShuttleInc.:pnDH110SE:pvrV1.0:rvnShuttleInc.:rnFS110SE:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: D
dmi.product.name: DH110SE
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  Upgrade Error

Status in linux package in Ubuntu:
  New

Bug description:
  Fails on software channels hangs at 150 of 184.

  Error string
  W:Updating from such a repository can't be done securely, and is therefore 
disabled by default., W:See apt-secure(8) manpage for repository creation and 
user configuration details., E:The repository 
'http://us.archive.ubuntu.com/ubuntu yakkety Release' does not have a Release 
file., W:Updating from such a repository can't be done securely, and is 
therefore disabled by default., W:See apt-secure(8) manpage for repository 
creation and user configuration details., E:The repository 
'http://us.archive.ubuntu.com/ubuntu yakkety-updates Release' does not have a 
Release file.

  Please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-137-generic 5.4.0-137.154
  ProcVersionSignature: Ubuntu 5.4.0-137.154-generic 5.4.218
  Uname: Linux 5.4.0-137-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sans   1710 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  4 09:38:21 2023
  HibernationDevice: RESUME=UUID=2793f083-2d10-4efc-b4b0-4bae5fc7f07a
  InstallationDate: Installed on 2017-03-27 (2139 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 

[Kernel-packages] [Bug 2000633] [NEW] nvidia-kernel-source-470 470.161.03-0ubuntu0.22.04.1: nvidia kernel module failed to build

[C]

Public bug reported:

Automatic bug report happened after reboot after install of NVIDIA
drivers from GUI

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-kernel-source-470 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
DKMSKernelVersion: 5.15.0-56-generic
Date: Wed Dec 28 13:06:44 2022
InstallationDate: Installed on 2015-08-20 (2687 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageVersion: 470.161.03-0ubuntu0.22.04.1
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: nvidia-graphics-drivers-470
Title: nvidia-kernel-source-470 470.161.03-0ubuntu0.22.04.1: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  nvidia-kernel-source-470 470.161.03-0ubuntu0.22.04.1: nvidia kernel
  module failed to build

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

Bug description:
  Automatic bug report happened after reboot after install of NVIDIA
  drivers from GUI

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-kernel-source-470 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DKMSKernelVersion: 5.15.0-56-generic
  Date: Wed Dec 28 13:06:44 2022
  InstallationDate: Installed on 2015-08-20 (2687 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageVersion: 470.161.03-0ubuntu0.22.04.1
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: nvidia-graphics-drivers-470
  Title: nvidia-kernel-source-470 470.161.03-0ubuntu0.22.04.1: 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/nvidia-graphics-drivers-470/+bug/2000633/+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 1989210] [NEW] Upgrade Error

[Michael C Donow]

Public bug reported:

E:The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-updates
Release' does not have a Release file.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-125-generic 5.4.0-125.141
ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
Uname: Linux 5.4.0-125-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sans   1714 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  9 09:30:05 2022
HibernationDevice: RESUME=UUID=2793f083-2d10-4efc-b4b0-4bae5fc7f07a
InstallationDate: Installed on 2017-03-27 (1991 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 3938:1032 MOSART Semi. 2.4G RF Keyboard & Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Shuttle Inc. DH110SE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-125-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-125-generic N/A
 linux-backports-modules-5.4.0-125-generic  N/A
 linux-firmware 1.187.33
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2022-09-09 (0 days ago)
dmi.bios.date: 01/05/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.03
dmi.board.asset.tag: Default string
dmi.board.name: FS110SE
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.03:bd01/05/2018:svnShuttleInc.:pnDH110SE:pvrV1.0:rvnShuttleInc.:rnFS110SE:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: D
dmi.product.name: DH110SE
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  Upgrade Error

Status in linux package in Ubuntu:
  New

Bug description:
  E:The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-updates
  Release' does not have a Release file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-125-generic 5.4.0-125.141
  ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
  Uname: Linux 5.4.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sans   1714 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  9 09:30:05 2022
  HibernationDevice: RESUME=UUID=2793f083-2d10-4efc-b4b0-4bae5fc7f07a
  InstallationDate: Installed on 2017-03-27 (1991 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 3938:1032 MOSART Semi. 2.4G RF Keyboard & Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. DH110SE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-125-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-125-generic N/A
   linux-backports-modules-5.4.0-125-generic  N/A
   linux-firmware 1.187.33
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-09-09 (0 days ago)
  dmi.bios.date: 01/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.03
  dmi.board.asset.tag: Default string
  dmi.board.name: FS110SE
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)

[Roxnny A Barrios C]

Hello, I currently have the same problem with Kernel 5.15 when
installing Ubuntu 22.04.

My laptop is an Hp ENVY x360 Convertible 15-eu0xxx.

I have secure boot disabled in the bios and I have been unable to
install Ubuntu 22.04.

In version 20.04 a successful installation was made but it is not
installed with the wireless network drivers.

If I try to update the kernel while it is in version 20.04 after the
installation I start to have boot problems.

So far I haven't tried the installation again and I really hope that the
problem will be solved as soon as possible.

** Attachment added: "these are the logs from the ubuntu terminal when the 
installation process is running.  I accessed it by pressing esc."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+attachment/5607744/+files/Ubuntu%20kernel%205.15%20Hp%20ENVY%20x360%20Convertible%2015-eu0xxx.mp4

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

Title:
  Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7
  3700U)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY
  X360 notebook (Ryzen 7 3700U).

  Model:
  HP ENVY X360
  13-ar0777ng
  9YN58EA#ABD

  After a few minutes the screen simply switches to black. No
  possibility to get a console by pressing CTRL-ALT-F1, F2, ...

  I removed the boot options "quiet splash" and recorded the boot via video.
  (just ask if you need the full video)
  I attach a significantly looking screenshot from that video, showing a kernel 
bug message.

  
  Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel.
  But suspend to memory isn't working.
  Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+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 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008

[c]

Thank you Tim, when this kernel can be released?

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

Title:
  BUG: kernel NULL pointer dereference, address: 0008

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  Hi,

  On one of the main US Ubuntu Archive servers (banjo), we decided to
  reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so,
  ran into this kernel panic:

  | [  350.776585] BUG: kernel NULL pointer dereference, address: 
0008
  | [  350.783674] #PF: supervisor read access in kernel mode
  | [  350.788846] #PF: error_code(0x) - not-present page
  | [  350.794019] PGD 0 P4D 0
  | [  350.796631] Oops:  [#1] SMP NOPTI
  | [  350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic 
#138~18.04.1-Ubuntu
  | [  350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 
Gen10, BIOS A40 02/10/2022
  | [  350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0
  | [  350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 
00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 
40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83
  | [  350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246
  | [  350.847324] RAX:  RBX: 897618739c80 RCX: 
0007
  | [  350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 
897605c85580
  | [  350.861682] RBP: 9a958cce8878 R08: 0178 R09: 
89763e407800
  | [  350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 
897607afb0b0
  | [  350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 
89762688b400
  | [  350.883219] FS:  () GS:89763ec0() 
knlGS:
  | [  350.891358] CS:  0010 DS:  ES:  CR0: 80050033
  | [  350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 
00340ee0
  | [  350.904319] Call Trace:
  | [  350.906787]  
  | [  350.908824]  tcp_v6_syn_recv_sock+0x8d/0x710
  | [  350.913259]  ? ip6_route_output_flags_noref+0xd0/0x110
  | [  350.918435]  tcp_get_cookie_sock+0x48/0x140
  | [  350.922688]  cookie_v6_check+0x5a2/0x700
  | [  350.926714]  tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.930589]  ? tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.934589]  tcp_v6_rcv+0xa16/0xa60
  | [  350.938102]  ip6_protocol_deliver_rcu+0xd8/0x4d0
  | [  350.942750]  ip6_input+0x41/0xb0
  | [  350.946000]  ip6_sublist_rcv_finish+0x42/0x60
  | [  350.950385]  ip6_sublist_rcv+0x235/0x260
  | [  350.954333]  ? __netif_receive_skb_core+0x19d/0xc60
  | [  350.959245]  ipv6_list_rcv+0x110/0x140
  | [  350.963018]  __netif_receive_skb_list_core+0x157/0x260
  | [  350.968192]  ? build_skb+0x17/0x80
  | [  350.971615]  netif_receive_skb_list_internal+0x187/0x2a0
  | [  350.976961]  gro_normal_list.part.131+0x1e/0x40
  | [  350.981519]  napi_complete_done+0x94/0x120
  | [  350.985700]  mlx5e_napi_poll+0x178/0x630 [mlx5_core]
  | [  350.990697]  net_rx_action+0x140/0x3e0
  | [  350.994475]  __do_softirq+0xe4/0x2da
  | [  350.998079]  irq_exit+0xae/0xb0
  | [  351.001239]  do_IRQ+0x59/0xe0
  | [  351.004228]  common_interrupt+0xf/0xf
  | [  351.007913]  
  | [  351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440
  | [  351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 
00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 
ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4
  | [  351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: 
ffd6
  | [  351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 
001f
  | [  351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: 

  | [  351.055997] RBP: 9a958026fe88 R08: 0002 R09: 
0002f680
  | [  351.063176] R10: 9a958026fe18 R11: 0115 R12: 
8976274c3800
  | [  351.070355] R13: 0001 R14: 84b66bb8 R15: 
0051abe96150
  | [  351.077540]  ? cpuidle_enter_state+0x98/0x440
  | [  351.081930]  ? menu_select+0x377/0x600
  | [  351.085706]  cpuidle_enter+0x2e/0x40
  | [  351.089310]  call_cpuidle+0x23/0x40
  | [  351.092821]  do_idle+0x1f6/0x270
  | [  351.096069]  cpu_startup_entry+0x1d/0x20
  | [  351.100024]  start_secondary+0x166/0x1c0
  | [  351.103977]  secondary_startup_64+0xa4/0xb0
  | [  351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 
ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf 
ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr 
ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 

[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008

[c]

Thank you, Andrea. We're trying to repro it, but it's not so far. Can
you create a proposed kernel, which includes this fix? Once we can
reproduce it, will let you know asap. But we can prepare the proposal
kernel in the meantime.

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

Title:
  BUG: kernel NULL pointer dereference, address: 0008

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  Hi,

  On one of the main US Ubuntu Archive servers (banjo), we decided to
  reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so,
  ran into this kernel panic:

  | [  350.776585] BUG: kernel NULL pointer dereference, address: 
0008
  | [  350.783674] #PF: supervisor read access in kernel mode
  | [  350.788846] #PF: error_code(0x) - not-present page
  | [  350.794019] PGD 0 P4D 0
  | [  350.796631] Oops:  [#1] SMP NOPTI
  | [  350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic 
#138~18.04.1-Ubuntu
  | [  350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 
Gen10, BIOS A40 02/10/2022
  | [  350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0
  | [  350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 
00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 
40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83
  | [  350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246
  | [  350.847324] RAX:  RBX: 897618739c80 RCX: 
0007
  | [  350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 
897605c85580
  | [  350.861682] RBP: 9a958cce8878 R08: 0178 R09: 
89763e407800
  | [  350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 
897607afb0b0
  | [  350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 
89762688b400
  | [  350.883219] FS:  () GS:89763ec0() 
knlGS:
  | [  350.891358] CS:  0010 DS:  ES:  CR0: 80050033
  | [  350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 
00340ee0
  | [  350.904319] Call Trace:
  | [  350.906787]  
  | [  350.908824]  tcp_v6_syn_recv_sock+0x8d/0x710
  | [  350.913259]  ? ip6_route_output_flags_noref+0xd0/0x110
  | [  350.918435]  tcp_get_cookie_sock+0x48/0x140
  | [  350.922688]  cookie_v6_check+0x5a2/0x700
  | [  350.926714]  tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.930589]  ? tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.934589]  tcp_v6_rcv+0xa16/0xa60
  | [  350.938102]  ip6_protocol_deliver_rcu+0xd8/0x4d0
  | [  350.942750]  ip6_input+0x41/0xb0
  | [  350.946000]  ip6_sublist_rcv_finish+0x42/0x60
  | [  350.950385]  ip6_sublist_rcv+0x235/0x260
  | [  350.954333]  ? __netif_receive_skb_core+0x19d/0xc60
  | [  350.959245]  ipv6_list_rcv+0x110/0x140
  | [  350.963018]  __netif_receive_skb_list_core+0x157/0x260
  | [  350.968192]  ? build_skb+0x17/0x80
  | [  350.971615]  netif_receive_skb_list_internal+0x187/0x2a0
  | [  350.976961]  gro_normal_list.part.131+0x1e/0x40
  | [  350.981519]  napi_complete_done+0x94/0x120
  | [  350.985700]  mlx5e_napi_poll+0x178/0x630 [mlx5_core]
  | [  350.990697]  net_rx_action+0x140/0x3e0
  | [  350.994475]  __do_softirq+0xe4/0x2da
  | [  350.998079]  irq_exit+0xae/0xb0
  | [  351.001239]  do_IRQ+0x59/0xe0
  | [  351.004228]  common_interrupt+0xf/0xf
  | [  351.007913]  
  | [  351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440
  | [  351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 
00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 
ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4
  | [  351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: 
ffd6
  | [  351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 
001f
  | [  351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: 

  | [  351.055997] RBP: 9a958026fe88 R08: 0002 R09: 
0002f680
  | [  351.063176] R10: 9a958026fe18 R11: 0115 R12: 
8976274c3800
  | [  351.070355] R13: 0001 R14: 84b66bb8 R15: 
0051abe96150
  | [  351.077540]  ? cpuidle_enter_state+0x98/0x440
  | [  351.081930]  ? menu_select+0x377/0x600
  | [  351.085706]  cpuidle_enter+0x2e/0x40
  | [  351.089310]  call_cpuidle+0x23/0x40
  | [  351.092821]  do_idle+0x1f6/0x270
  | [  351.096069]  cpu_startup_entry+0x1d/0x20
  | [  351.100024]  start_secondary+0x166/0x1c0
  | [  351.103977]  secondary_startup_64+0xa4/0xb0
  | [  351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 
ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf 

[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008

[c]

@arighi Is this fix in latest proposal of Azure kernel as well? We have
customers met the same issue. We can ask customer to try the fix.

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

Title:
  BUG: kernel NULL pointer dereference, address: 0008

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  Hi,

  On one of the main US Ubuntu Archive servers (banjo), we decided to
  reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so,
  ran into this kernel panic:

  | [  350.776585] BUG: kernel NULL pointer dereference, address: 
0008
  | [  350.783674] #PF: supervisor read access in kernel mode
  | [  350.788846] #PF: error_code(0x) - not-present page
  | [  350.794019] PGD 0 P4D 0
  | [  350.796631] Oops:  [#1] SMP NOPTI
  | [  350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic 
#138~18.04.1-Ubuntu
  | [  350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 
Gen10, BIOS A40 02/10/2022
  | [  350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0
  | [  350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 
00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 
40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83
  | [  350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246
  | [  350.847324] RAX:  RBX: 897618739c80 RCX: 
0007
  | [  350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 
897605c85580
  | [  350.861682] RBP: 9a958cce8878 R08: 0178 R09: 
89763e407800
  | [  350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 
897607afb0b0
  | [  350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 
89762688b400
  | [  350.883219] FS:  () GS:89763ec0() 
knlGS:
  | [  350.891358] CS:  0010 DS:  ES:  CR0: 80050033
  | [  350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 
00340ee0
  | [  350.904319] Call Trace:
  | [  350.906787]  
  | [  350.908824]  tcp_v6_syn_recv_sock+0x8d/0x710
  | [  350.913259]  ? ip6_route_output_flags_noref+0xd0/0x110
  | [  350.918435]  tcp_get_cookie_sock+0x48/0x140
  | [  350.922688]  cookie_v6_check+0x5a2/0x700
  | [  350.926714]  tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.930589]  ? tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.934589]  tcp_v6_rcv+0xa16/0xa60
  | [  350.938102]  ip6_protocol_deliver_rcu+0xd8/0x4d0
  | [  350.942750]  ip6_input+0x41/0xb0
  | [  350.946000]  ip6_sublist_rcv_finish+0x42/0x60
  | [  350.950385]  ip6_sublist_rcv+0x235/0x260
  | [  350.954333]  ? __netif_receive_skb_core+0x19d/0xc60
  | [  350.959245]  ipv6_list_rcv+0x110/0x140
  | [  350.963018]  __netif_receive_skb_list_core+0x157/0x260
  | [  350.968192]  ? build_skb+0x17/0x80
  | [  350.971615]  netif_receive_skb_list_internal+0x187/0x2a0
  | [  350.976961]  gro_normal_list.part.131+0x1e/0x40
  | [  350.981519]  napi_complete_done+0x94/0x120
  | [  350.985700]  mlx5e_napi_poll+0x178/0x630 [mlx5_core]
  | [  350.990697]  net_rx_action+0x140/0x3e0
  | [  350.994475]  __do_softirq+0xe4/0x2da
  | [  350.998079]  irq_exit+0xae/0xb0
  | [  351.001239]  do_IRQ+0x59/0xe0
  | [  351.004228]  common_interrupt+0xf/0xf
  | [  351.007913]  
  | [  351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440
  | [  351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 
00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 
ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4
  | [  351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: 
ffd6
  | [  351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 
001f
  | [  351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: 

  | [  351.055997] RBP: 9a958026fe88 R08: 0002 R09: 
0002f680
  | [  351.063176] R10: 9a958026fe18 R11: 0115 R12: 
8976274c3800
  | [  351.070355] R13: 0001 R14: 84b66bb8 R15: 
0051abe96150
  | [  351.077540]  ? cpuidle_enter_state+0x98/0x440
  | [  351.081930]  ? menu_select+0x377/0x600
  | [  351.085706]  cpuidle_enter+0x2e/0x40
  | [  351.089310]  call_cpuidle+0x23/0x40
  | [  351.092821]  do_idle+0x1f6/0x270
  | [  351.096069]  cpu_startup_entry+0x1d/0x20
  | [  351.100024]  start_secondary+0x166/0x1c0
  | [  351.103977]  secondary_startup_64+0xa4/0xb0
  | [  351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 
ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf 
ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr 
ib_iser rdma_cm 

[Kernel-packages] [Bug 488849] Re: memory eaten: poll_schedule_timeout

[c]

yep not me too, but me to  over six months of it now and still trying to fix 
problem 
the only bit of usefull information i have is changing your log in manager to 
gdm3 stops most of the blue screens crashes  and cant login problems

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

Title:
  memory eaten: poll_schedule_timeout

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  on Karmic 32 bits: the memory is progressively eatened and semm to
  never be freed.

  there is nothing in the logs, but when i open "monitor system", in the
  process tab:

  - every process ended with : poll_schedule_timeout
  - randomly, some of those are in "futex_wait_queue_me" state, then failed in 
"poll_schedule_timeout"

  It's the first time that i have this problem on a upto date system,
  but googling around, i've found lots of related links on other kernel
  or distro. Some patch seen on linuxhq / lkml / kerneltrap

  This has happen with these process running:
  -boinc 6.10.17
  - firefox 3.5.5
  - pulseaudio 0.9.19-0ubuntu4

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   oem2695 F...m pulseaudio
   /dev/snd/controlC0:  oem2695 F pulseaudio
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 19'
 Mixer name : 'Realtek ALC882'
 Components : 'HDA:10ec0882,1043e601,00100101'
 Controls  : 44
 Simple ctrls  : 25
  CheckboxSubmission: 0e856621e764f27871668a8d860c3158
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Thu Nov 26 17:46:36 2009
  DistroRelease: Ubuntu 9.10
  HibernationDevice: RESUME=UUID=f4216733-a2b7-4818-9852-9bb41d54d87c
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia
  Package: linux-image 2.6.31.15.28
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic 
root=UUID=9e61e83e-bca9-43cf-aa90-5a68892213fa ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  RelatedPackageVersions:
   linux-backports-modules-2.6.31-15-generic N/A
   linux-firmware 1.25
  RfKill:
   
  SourcePackage: linux-meta
  Uname: Linux 2.6.31-15-generic i686
  WpaSupplicantLog:
   
  XsessionErrors:
   (gnome-settings-daemon:2732): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2732): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (nautilus:2765): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (polkit-gnome-authentication-agent-1:2777): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:3449): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd07/10/2008:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/488849/+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 1942133] Re: Nvidia driver packages prevent suspend due to leftover Systemd units

[John C.]

** Tags added: nvidia

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

Title:
  Nvidia driver packages prevent suspend due to leftover Systemd units

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed

Bug description:
  When the nvidia driver packages are uninstalled, they leave some
  symlinks that prevent suspend.

  I whink that, when attempting to suspend, the error is logged as this
  (edited):

  ModemManager[3287]:   [sleep-monitor] inhibit failed: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  upowerd[5771]: Could not acquire inhibitor lock: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  dbus-daemon[2888]: [system] Activating via systemd: service 
name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' 
requested by ':1.53' (uid=1000 pid=8227 
comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined")
  systemd[1]: systemd-logind.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
  systemd[1]: systemd-logind.service: Scheduled restart job, restart 
counter is at 7.
  systemd[1]: Stopped Login Service.
  systemd[1]: Condition check resulted in Load Kernel Module drm being 
skipped.
  systemd[1]: Starting Login Service...

  I've deleted the problematic symlinks while trying to solving the
  problem, however, they should be these:

  
/etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service
  /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service
  
/etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service
  
/etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service

  I've briefly checked before removing them; at least a couple of them
  were masked, but they were still causing the problem.

  I don't see any reason why they should hang around the systemd
  configuration once the packages are purged. Additionally, this is a
  problem that is not easy to diagnose.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-driver-470 (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CurrentDesktop: MATE
  Date: Mon Aug 30 21:10:52 2021
  LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1942133/+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 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

[Tiago M. C.]

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1967702

  [Impact]

  Blind system administrators rely on the speakup accessibility feature
  to be able to use screen readers in text mode, like "espeakup".

  Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time,
  although in recent releases it keeps being disabled. In Hirsute and
  Impish, it was accidentally disabled due to it moving from
  drivers/staging/ to drivers/accessibility/, and it was re-added by Tim
  Gardner in LP1942459.

  When it was recently re-enabled, the patch was never applied to
  ubuntu-unstable, and thus was never picked up by Jammy.

  We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and
  ubuntu-unstable.

  [Fix]

  We need to enable the following configuration items:

  CONFIG_ACCESSIBILITY=y
  CONFIG_SPEAKUP=m

  and the additional modules:

  CONFIG_SPEAKUP_SYNTH_ACNTSA=m
  CONFIG_SPEAKUP_SYNTH_APOLLO=m
  CONFIG_SPEAKUP_SYNTH_AUDPTR=m
  CONFIG_SPEAKUP_SYNTH_BNS=m
  CONFIG_SPEAKUP_SYNTH_DECEXT=m
  CONFIG_SPEAKUP_SYNTH_DECTLK=m
  CONFIG_SPEAKUP_SYNTH_DUMMY=m
  CONFIG_SPEAKUP_SYNTH_LTLK=m
  CONFIG_SPEAKUP_SYNTH_SOFT=m
  CONFIG_SPEAKUP_SYNTH_SPKOUT=m
  CONFIG_SPEAKUP_SYNTH_TXPRT=m

  [Testcase]

  Install the speakup accessibility tool:

  $ sudo apt install espeakup

  Check journalctl to see if it is able to load kernel modules:

  systemd[1]: Starting Software speech output for Speakup...
  modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory 
/lib/modules/5.15.0-25-generic
  systemd[1]: espeakup.service: Control process exited, code=exited, 
status=1/FAILURE
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.
  systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped Software speech output for Speakup.
  systemd[1]: espeakup.service: Start request repeated too quickly.
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.

  We should see espeakup.service start correctly, instead of failing to
  load speakup_soft:

  systemd[1]: Starting Software speech output for Speakup...
  kernel: input: Speakup as /devices/virtual/input/input5
  kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123)
  kernel: speakup 3.1.6: initialized
  kernel: synth name on entry is: (null)
  kernel: synth probe
  kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122)
  kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121)
  systemd[1]: Started Software speech output for Speakup.

  You can also try load the modules manually:

  $ sudo modprobe speakup_soft

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test

  If you install the test kernel, the speakup modules should load
  successfully.

  [Where problems could occur]

  We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x,
  and this shouldn't have any affect on config items being turned on,
  since it simply enables the speakup submenu to be shown.

  Enabling CONFIG_SPEAKUP* should not have any impact on users that
  don't use screen reader accessibility software, as it will only be
  loaded by users of espeakup.

  If a regression were to occur, users could unload the speakup modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+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 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

[Tiago M. C.]

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1967702

  [Impact]

  Blind system administrators rely on the speakup accessibility feature
  to be able to use screen readers in text mode, like "espeakup".

  Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time,
  although in recent releases it keeps being disabled. In Hirsute and
  Impish, it was accidentally disabled due to it moving from
  drivers/staging/ to drivers/accessibility/, and it was re-added by Tim
  Gardner in LP1942459.

  When it was recently re-enabled, the patch was never applied to
  ubuntu-unstable, and thus was never picked up by Jammy.

  We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and
  ubuntu-unstable.

  [Fix]

  We need to enable the following configuration items:

  CONFIG_ACCESSIBILITY=y
  CONFIG_SPEAKUP=m

  and the additional modules:

  CONFIG_SPEAKUP_SYNTH_ACNTSA=m
  CONFIG_SPEAKUP_SYNTH_APOLLO=m
  CONFIG_SPEAKUP_SYNTH_AUDPTR=m
  CONFIG_SPEAKUP_SYNTH_BNS=m
  CONFIG_SPEAKUP_SYNTH_DECEXT=m
  CONFIG_SPEAKUP_SYNTH_DECTLK=m
  CONFIG_SPEAKUP_SYNTH_DUMMY=m
  CONFIG_SPEAKUP_SYNTH_LTLK=m
  CONFIG_SPEAKUP_SYNTH_SOFT=m
  CONFIG_SPEAKUP_SYNTH_SPKOUT=m
  CONFIG_SPEAKUP_SYNTH_TXPRT=m

  [Testcase]

  Install the speakup accessibility tool:

  $ sudo apt install espeakup

  Check journalctl to see if it is able to load kernel modules:

  systemd[1]: Starting Software speech output for Speakup...
  modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory 
/lib/modules/5.15.0-25-generic
  systemd[1]: espeakup.service: Control process exited, code=exited, 
status=1/FAILURE
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.
  systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped Software speech output for Speakup.
  systemd[1]: espeakup.service: Start request repeated too quickly.
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.

  We should see espeakup.service start correctly, instead of failing to
  load speakup_soft:

  systemd[1]: Starting Software speech output for Speakup...
  kernel: input: Speakup as /devices/virtual/input/input5
  kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123)
  kernel: speakup 3.1.6: initialized
  kernel: synth name on entry is: (null)
  kernel: synth probe
  kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122)
  kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121)
  systemd[1]: Started Software speech output for Speakup.

  You can also try load the modules manually:

  $ sudo modprobe speakup_soft

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test

  If you install the test kernel, the speakup modules should load
  successfully.

  [Where problems could occur]

  We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x,
  and this shouldn't have any affect on config items being turned on,
  since it simply enables the speakup submenu to be shown.

  Enabling CONFIG_SPEAKUP* should not have any impact on users that
  don't use screen reader accessibility software, as it will only be
  loaded by users of espeakup.

  If a regression were to occur, users could unload the speakup modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+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 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

[Tiago M. C.]

Hi Matthew! Fix that was applied in Linux/5.15.0-28.29 kernel resolved
the issue. 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/1967702

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1967702

  [Impact]

  Blind system administrators rely on the speakup accessibility feature
  to be able to use screen readers in text mode, like "espeakup".

  Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time,
  although in recent releases it keeps being disabled. In Hirsute and
  Impish, it was accidentally disabled due to it moving from
  drivers/staging/ to drivers/accessibility/, and it was re-added by Tim
  Gardner in LP1942459.

  When it was recently re-enabled, the patch was never applied to
  ubuntu-unstable, and thus was never picked up by Jammy.

  We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and
  ubuntu-unstable.

  [Fix]

  We need to enable the following configuration items:

  CONFIG_ACCESSIBILITY=y
  CONFIG_SPEAKUP=m

  and the additional modules:

  CONFIG_SPEAKUP_SYNTH_ACNTSA=m
  CONFIG_SPEAKUP_SYNTH_APOLLO=m
  CONFIG_SPEAKUP_SYNTH_AUDPTR=m
  CONFIG_SPEAKUP_SYNTH_BNS=m
  CONFIG_SPEAKUP_SYNTH_DECEXT=m
  CONFIG_SPEAKUP_SYNTH_DECTLK=m
  CONFIG_SPEAKUP_SYNTH_DUMMY=m
  CONFIG_SPEAKUP_SYNTH_LTLK=m
  CONFIG_SPEAKUP_SYNTH_SOFT=m
  CONFIG_SPEAKUP_SYNTH_SPKOUT=m
  CONFIG_SPEAKUP_SYNTH_TXPRT=m

  [Testcase]

  Install the speakup accessibility tool:

  $ sudo apt install espeakup

  Check journalctl to see if it is able to load kernel modules:

  systemd[1]: Starting Software speech output for Speakup...
  modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory 
/lib/modules/5.15.0-25-generic
  systemd[1]: espeakup.service: Control process exited, code=exited, 
status=1/FAILURE
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.
  systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped Software speech output for Speakup.
  systemd[1]: espeakup.service: Start request repeated too quickly.
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.

  We should see espeakup.service start correctly, instead of failing to
  load speakup_soft:

  systemd[1]: Starting Software speech output for Speakup...
  kernel: input: Speakup as /devices/virtual/input/input5
  kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123)
  kernel: speakup 3.1.6: initialized
  kernel: synth name on entry is: (null)
  kernel: synth probe
  kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122)
  kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121)
  systemd[1]: Started Software speech output for Speakup.

  You can also try load the modules manually:

  $ sudo modprobe speakup_soft

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test

  If you install the test kernel, the speakup modules should load
  successfully.

  [Where problems could occur]

  We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x,
  and this shouldn't have any affect on config items being turned on,
  since it simply enables the speakup submenu to be shown.

  Enabling CONFIG_SPEAKUP* should not have any impact on users that
  don't use screen reader accessibility software, as it will only be
  loaded by users of espeakup.

  If a regression were to occur, users could unload the speakup modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+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 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function

[Tiago M. C.]

Thank you very much Matthew!

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

Title:
  Enable speakup kernel modules to allow the speakup screen reader to
  function

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1967702

  [Impact]

  Blind system administrators rely on the speakup accessibility feature
  to be able to use screen readers in text mode, like "espeakup".

  Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time,
  although in recent releases it keeps being disabled. In Hirsute and
  Impish, it was accidentally disabled due to it moving from
  drivers/staging/ to drivers/accessibility/, and it was re-added by Tim
  Gardner in LP1942459.

  When it was recently re-enabled, the patch was never applied to
  ubuntu-unstable, and thus was never picked up by Jammy.

  We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and
  ubuntu-unstable.

  [Fix]

  We need to enable the following configuration items:

  CONFIG_ACCESSIBILITY=y
  CONFIG_SPEAKUP=m

  and the additional modules:

  CONFIG_SPEAKUP_SYNTH_ACNTSA=m
  CONFIG_SPEAKUP_SYNTH_APOLLO=m
  CONFIG_SPEAKUP_SYNTH_AUDPTR=m
  CONFIG_SPEAKUP_SYNTH_BNS=m
  CONFIG_SPEAKUP_SYNTH_DECEXT=m
  CONFIG_SPEAKUP_SYNTH_DECTLK=m
  CONFIG_SPEAKUP_SYNTH_DUMMY=m
  CONFIG_SPEAKUP_SYNTH_LTLK=m
  CONFIG_SPEAKUP_SYNTH_SOFT=m
  CONFIG_SPEAKUP_SYNTH_SPKOUT=m
  CONFIG_SPEAKUP_SYNTH_TXPRT=m

  [Testcase]

  Install the speakup accessibility tool:

  $ sudo apt install espeakup

  Check journalctl to see if it is able to load kernel modules:

  systemd[1]: Starting Software speech output for Speakup...
  modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory 
/lib/modules/5.15.0-25-generic
  systemd[1]: espeakup.service: Control process exited, code=exited, 
status=1/FAILURE
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.
  systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped Software speech output for Speakup.
  systemd[1]: espeakup.service: Start request repeated too quickly.
  systemd[1]: espeakup.service: Failed with result 'exit-code'.
  systemd[1]: Failed to start Software speech output for Speakup.

  We should see espeakup.service start correctly, instead of failing to
  load speakup_soft:

  systemd[1]: Starting Software speech output for Speakup...
  kernel: input: Speakup as /devices/virtual/input/input5
  kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 123)
  kernel: speakup 3.1.6: initialized
  kernel: synth name on entry is: (null)
  kernel: synth probe
  kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 122)
  kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 121)
  systemd[1]: Started Software speech output for Speakup.

  You can also try load the modules manually:

  $ sudo modprobe speakup_soft

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test

  If you install the test kernel, the speakup modules should load
  successfully.

  [Where problems could occur]

  We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x,
  and this shouldn't have any affect on config items being turned on,
  since it simply enables the speakup submenu to be shown.

  Enabling CONFIG_SPEAKUP* should not have any impact on users that
  don't use screen reader accessibility software, as it will only be
  loaded by users of espeakup.

  If a regression were to occur, users could unload the speakup modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+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 1967702] [NEW] Accessibility features have been disabled, modules like speakup_soft and others are missing

[Tiago M. C.]

Public bug reported:

>From very old versions of Kernel for Ubuntu until version 5.13, accessibility 
>features were enabled, allowing blind users to use screen readers in text 
>mode, such as "speakup" via "espeakup" package.
In Kernels 5.15 packages for Ubuntu 22.04 beta, such as 
"linux-image-5.15.0-23-generic", accessibility features are disabled (no 
justification for such occurrence was listed in the file 
"changelog.Debian.gz"), with this the espeakup application doesn't work, it 
depends on the missing speakup_soft module.
Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file 
"/boot/config-5.13.0-39-generic", the line
CONFIG_ACCESSIBILITY=y
and the following lines are also missing:
#
# Speakup console speech
#
CONFIG_SPEAKUP=m
CONFIG_SPEAKUP_SYNTH_ACNTSA=m
CONFIG_SPEAKUP_SYNTH_APOLLO=m
CONFIG_SPEAKUP_SYNTH_AUDPTR=m
CONFIG_SPEAKUP_SYNTH_BNS=m
CONFIG_SPEAKUP_SYNTH_DECTLK=m
CONFIG_SPEAKUP_SYNTH_DECEXT=m
CONFIG_SPEAKUP_SYNTH_LTLK=m
CONFIG_SPEAKUP_SYNTH_SOFT=m
CONFIG_SPEAKUP_SYNTH_SPKOUT=m
CONFIG_SPEAKUP_SYNTH_TXPRT=m
CONFIG_SPEAKUP_SYNTH_DUMMY=m
# end of Speakup console speech

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-23-generic 5.15.0-23.23
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tiago  1259 F pulseaudio
 /dev/snd/pcmC0D0p:   tiago  1259 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Apr  3 22:05:39 2022
InstallationDate: Installed on 2022-04-03 (0 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220330)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 3583
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-23-generic N/A
 linux-backports-modules-5.15.0-23-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2021
dmi.bios.release: 1.17
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.0
dmi.board.name: 0KD03P
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy

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

Title:
  Accessibility features have been disabled, modules like speakup_soft
  and others are missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From very old versions of Kernel for Ubuntu until version 5.13, accessibility 
features were enabled, allowing blind users to use screen readers in text mode, 
such as "speakup" via "espeakup" package.
  In Kernels 5.15 packages for Ubuntu 22.04 beta, such as 
"linux-image-5.15.0-23-generic", accessibility features are disabled (no 
justification for such occurrence was listed in the file 
"changelog.Debian.gz"), with this the espeakup application doesn't work, it 
depends on the missing speakup_soft module.
  Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file 
"/boot/config-5.13.0-39-generic", the line
  CONFIG_ACCESSIBILITY=y
  and the following lines are also missing:
  #
  # Speakup console speech
  #
  CONFIG_SPEAKUP=m
  CONFIG_SPEAKUP_SYNTH_ACNTSA=m
  CONFIG_SPEAKUP_SYNTH_APOLLO=m
  CONFIG_SPEAKUP_SYNTH_AUDPTR=m
  CONFIG_SPEAKUP_SYNTH_BNS=m
  CONFIG_SPEAKUP_SYNTH_DECTLK=m
  CONFIG_SPEAKUP_SYNTH_DECEXT=m
  CONFIG_SPEAKUP_SYNTH_LTLK=m
  CONFIG_SPEAKUP_SYNTH_SOFT=m
  CONFIG_SPEAKUP_SYNTH_SPKOUT=m
  CONFIG_SPEAKUP_SYNTH_TXPRT=m
  CONFIG_SPEAKUP_SYNTH_DUMMY=m
  # end of Speakup console speech

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tiago   

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Guillaume C.]

Thank you very much! Works for me on ThinkPad E15 Gen 2.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  On some thinkpads we may get a kernel panic at boot, because the
  elantech driver (trakcpad) can trigger out-of-bounds access in the
  stack.

  [Test case]

  Simply boot the kernel on one of the affected systems (e.g., Thinkpad
  E14 Gen2).

  [Fix]

  Prevent the stack out of bound access by applying the following
  upstream commit (from linux-next):

  1d72d9f960cc ("Input: elantech - fix stack out of bound access in
  elantech_change_report_id()")

  [Regression potential]

  The fix is touching the elantech driver, so we could only see
  regressions with this specific trackpad/mouse driver.

  [Original bug report]

  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1543919] Re: Remove EISA support from main kernel image and make it M (modular)

[B. C. Schmerker]

I've an emachines®/acer® EL1210-09 (Advance Micro Devices Inc. Athlon
LE-1620 (P/N ADH1620IAA5DH); nVIDIA® nForce® 780a SLI with planar C77 a2
GPU; nVIDIA® GF119 a1 GPU on PCIe 2.0 x16 slot).  The system DMesg
predictably detects no EISA resources on probing platform eisa.0, so
EISA.c and related headers can be compiled as a module with no effect on
my system's kernel initialization.  AFAIK, Intel PCI has replaced EISA
on all x86 and x86_64 systems built after 2000.  The following redact
from /var/log/dmesg.0 on 17 July 2021 illustrates typical info:

[0.00] kernel: Linux version 5.8.0-59-generic (buildd@lcy01-amd64-022) 
(gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 
2.34) #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 (Ubuntu 
5.8.0-59.66~20.04.1-generic 5.8.18)
[0.00] kernel: Command line: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic 
root=UUID=c4248af1-a4cf-49a2-ba18-4de2c65c815c ro acpi_force_32bit_fadt_addr 
acpi_rev_override check_enable_amd_mmconf pcie_bus_tune=off pcie_aspm=off 
pci_ports=native intremap=off agp=off nohugeiomap parport=0 hashdist=0
...
[0.212298] kernel: EISA bus registered
...
[1.006643] kernel: platform eisa.0: Probing EISA bus 0
[1.006715] kernel: platform eisa.0: EISA: Cannot allocate resource for 
mainboard
[1.006779] kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
[1.006855] kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
[1.006917] kernel: platform eisa.0: EISA: Detected 0 cards

I concur on the feasibility of offloading EISA from Kernel core and
building a Module EISA.ko.

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

Title:
  Remove EISA support from main kernel image and make it M (modular)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (This is a sort of RfC. )

  I have a PC that still has the good old PCI ports, but I am 100% sure that 
the active use of EISA dates back yet more 10 years.
  In other words, boards that _only_ support EISA date back 25 years now, while 
those that provide *one* EISA slot date back roughly 15 years (one of the 
Elitegroup K7 series comes to mind, from about 2001/02).

  So the EISA support *should* be provided, as we should even support ancient 
hardware (Linux principle :))
  However, why the EISA support is *compiled in* is beyond me.

  For instance, it creates lots of totally unnecessary noise in dmesg:

  [0.08] EISA bus registered
  [1.598316] platform eisa.0: Probing EISA bus 0
  [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1  
(repeated 10 times, i=i+1)
  [1.598368] platform eisa.0: EISA: Detected 0 cards

  For a 1997 mainboard, this would make perfect sense.
  But it is very probable that said mainboard would require linux-image-extra 
nonetheless to support some days-of-yore chipset.

  So why not leave it as a *module*, while removing its support from
  main kernel image once and for all?

  Your turn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+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 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station

[simone-c]

Lenovo X1 Extreme Gen2
Docking Lenovo Thunderbolt 3 Gen2

Was getting similar random disconnects every 2-5 minutes:

[125028.443102] pcieport :05:01.0: pciehp: Slot(1): Link Down
[125028.443108] pcieport :05:01.0: pciehp: Slot(1): Card not present
[125028.443122] pcieport :08:04.0: can't change power state from D3cold to 
D0 (config space inaccessible)
[125028.444133] xhci_hcd :09:00.0: remove, state 1
[125028.444151] usb usb6: USB disconnect, device number 1
[125028.444156] usb 6-2: USB disconnect, device number 2
[125028.444162] usb 6-2.1: USB disconnect, device number 3
[125028.444167] usb 6-2.1.2: USB disconnect, device number 5
[125028.444369] xhci_hcd :09:00.0: xHCI host controller not responding, 
assume dead
..
.

Fixed by connecting two power supplies to both laptop and docking
(2x135W).

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

Title:
  xHCI host controller not responding, assume dead via USB-C docking
  station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C 
(https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the 
laptop from the docking station, the USB Hub disconnects all the local laptop 
USB ports and they are unusable.
  If I try to re-attach the laptop to the docking station nothing change, the 
ports (docking and laptop) are still disconnected, the hdmi/lan/power is 
working good. Sometimes it happens also when the laptop is docked and I'm 
working.

  The issue seems similar of the bug 1766076:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076

  but here no thunderbolt, it's a ryzen cpu.
  As written in the bug 1766076, the only way to have the USB in working 
condition is unbinding/binding the xhci or using the unit/systemd workaround 
described on post 83 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with 
some modification, sometimes is still not working at all.

  The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu
  18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs
  installed from kernel.org) and on Fedora 31 too. In Windows everything
  is working fine.

  The bios and firmware of the docking station are updated to the last
  one (1 month ago).

  The dmesg when I undock the laptop:

  [  305.299725] usb 2-1: USB disconnect, device number 2
  [  305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 
77]
  [  305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] 
[master: 8e933bad]
  [  305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] 
[master: 8e933bad]
  [  305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] 
[master: 8e933bad]
  [  305.362012] r8169 :03:00.0 enp3s0f0: Link is Down
  [  305.464627] usb 3-4: USB disconnect, device number 2
  [  305.464642] usb 3-4.2: USB disconnect, device number 3
  [  305.472691] usb 2-4: USB disconnect, device number 4
  [  305.472704] usb 2-4.2: USB disconnect, device number 5
  [  305.472712] usb 2-4.2.4: USB disconnect, device number 7
  [  306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  ...hundreds of line - the same
  [  310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop 
endpoint command.
  [  310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  hundreds of line - the same
  [  310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, 
assume dead
  [  310.532379] xhci_hcd :05:00.3: HC died; cleaning up
  [  310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure 
endpoint command
  [  310.670248] usb 2-4.3: USB disconnect, device number 6
  [  310.834039] usb 2-4.5: USB disconnect, device number 8
  [  310.835017] usb 2-2: USB disconnect, device number 10

  When I re-attach the latop to the docking:

  [  343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow 
control rx/tx
  [  344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 
77]
  [  344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] 
[master: 8e933bad]
  [  344.365857] [drm] DM_MST: added

[Kernel-packages] [Bug 1907445] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

[arm-c]

Ok.  The best solution for this is posted here on ask ubuntu.  The issue
is with the LTS update, it did not include the updated bcmwl file when
it switches the Kernel to the HWE version.  This is the link to where I
found the solution I used and it solves my problem.

I chose option one.
https://askubuntu.com/a/1305819/42310

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  Wifi disappear on Macbook Pro 15"

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-32-generic
  Date: Tue Dec  8 18:14:41 2020
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
 error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-05-07 (215 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu5
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1907445/+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 1907445] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

[arm-c]

I just ran updates on my laptop... got error message:

Error while applying changes
pk-client-error-quark:  Error while installing package: installed 
bcmwl-kernel-source package post-installation script subprocess returned error 
exit status 10 (313)

I lost all of my wifi card in my MacBook Air.


RECOVERY:  For those like me, recovery can be a challenge.  I didn't see how to 
get back to a older kernel while working through rEFInd boot manager but 
what got me out of this issue was.

- Open Additional drivers (Super Menu, type 'Drivers' and select).
- After scan for "Proprietery Drivers in Use"... switch option to "do not use 
this device" and apply.
- Reboot and hopefully your Wifi is restored.  

I then ran all updates (sudo apt update & sudo apt upgrade).  I went
back to additional drivers and tried reinstalling... got error... but it
appears to have taken... even after reboot.

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  Wifi disappear on Macbook Pro 15"

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-32-generic
  Date: Tue Dec  8 18:14:41 2020
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
 error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-05-07 (215 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu5
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1907445/+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 1715861] Re: r592 & r852 IRQ: DMA errors cause excessive log file entries

[Ryan C. Underwood]

Still happens in kernel 5.8.

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

Title:
  r592 & r852 IRQ: DMA errors cause excessive log file entries

Status in linux package in Ubuntu:
  Expired

Bug description:
   -- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
  than a day. --

  Typical excessive syslog entry is attached (hostname redacted). I am not 
making hardware changes at the times these entries are made. Entires are of the 
form:
  Sep  7 20:05:55  kernel: [14098.011547] r592: IRQ: card added
  Sep  7 20:05:55  kernel: [14098.011548] r592: IRQ: DMA error

  followed by 38 lines of trace information

  The laptop reports itself as having the problematic Ricoh devices. Relevant 
hwinfo attached. grepped extract follows
Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"

  WORKAROUND: Blacklist devices by adding the following lines at the end
  of /etc/modprobe.d/blacklist.conf

  # Stop errors filling up log - see
  # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
  # Blacklist Ricoh card reader
  blacklist r592
  blacklist r852

  This stops messages from appearing in /var/log/kern.log and
  /var/log/syslog. The Ricoh cardreader built into the laptop still
  reads SD cards after such blacklisting.

  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  pgrb   2220 F pulseaudio
   /dev/snd/controlC1:  pgrb   2220 F pulseaudio
   /dev/snd/controlC0:  pgrb   2220 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
  InstallationDate: Installed on 2017-09-05 (3 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 0769BMG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 
root=/dev/mapper/herd-root ro 
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET24WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 0769BMG
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715861/+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 1890913] Re: init is using 100% of processor

[John C.]

I am experiencing this same problem and I can confirm that when I mask the
apport-autoreport.service the problem stops.

I am on Ubuntu 20.10 with Kernel 5.8.0-18-generic. I also have Ubuntu 20.04
with Kernel 5.8.0-05-generic and
can confirm the problem does not happen there

John

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

Title:
  init is using 100% of processor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  the `sbin/init splash` process is using more than 100% of processor
  after boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246-2ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7
  Uname: Linux 5.8.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Aug  8 22:14:37 2020
  InstallationDate: Installed on 2019-11-01 (280 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 2349KEG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic 
root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2019
  dmi.bios.release: 2.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349KEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349KEG
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+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 1882419] Re: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"

[Vincent C]

l: [ 1380.069197]  ? 
kthread_create_worker_on_cpu+0x20/0x20
  May  1 22:53:47 allen-laptop kernel: [ 1380.069200]  ret_from_fork+0x2e/0x38
  May  1 22:53:47 allen-laptop kernel: [ 1380.069202] Code: 85 f6 75 ea 8d 65 
f4 89 f8 5b 5e 5f 5d c3 8b 93 c4 02 00 00 81 c3 d4 02 00 00 50 85 d2 0f 45 da 
53 68 f4 4f 35 f8 e8 c3 21 d9 db <0f> 0b 83 c4 0c 8d 65 f4 bf fb ff ff ff 89 f8 
5b 5e 5f 5d c3 8d
  May  1 22:53:47 allen-laptop kernel: [ 1380.069224] ---[ end trace 
3b15919b5f18d41d ]---

  $ dmesg | egrep 'iwl|firm'
  [4.325964] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [   29.140771] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, in-tree:s
  [   29.140773] iwl3945: Copyright(c) 2003-2011 Intel Corporation
  [   29.140773] iwl3945: hw_scan is disabled
  [   29.140832] iwl3945 :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   29.200843] iwl3945 :03:00.0: Tunable channels: 11 802.11bg, 13 
802.11a channels
  [   29.200846] iwl3945 :03:00.0: Detected Intel Wireless WiFi Link 3945ABG
  [   29.251637] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
  [  179.894551] iwl3945 :03:00.0: loaded firmware version 15.32.2.9
  [  182.473316] iwl3945 :03:00.0: Enabling power save might cause firmware 
crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-101-generic 4.15.0-101.102
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic i686
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  allen  1523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 15:48:01 2020
  HibernationDevice: RESUME=UUID=b2e0a997-adf9-4d21-b68a-e58293980474
  InstallationDate: Installed on 2013-04-29 (2595 days ago)
  InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
  MachineType: LENOVO 7733BW8
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=c01a551c-583f-4fe3-8866-0f89a6aa5934 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-101-generic N/A
   linux-backports-modules-4.15.0-101-generic  N/A
   linux-firmware  1.173.18
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-30 (647 days ago)
  dmi.bios.date: 08/15/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC4WW (2.24 )
  dmi.board.name: 7733BW8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC4WW(2.24):bd08/15/2008:svnLENOVO:pn7733BW8:pvrThinkPadR61:rvnLENOVO:rn7733BW8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad R61
  dmi.product.name: 7733BW8
  dmi.product.version: ThinkPad R61
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882419/+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 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode

[C-alexandre-pires]

I've installed https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/
and the problem seems to have been solved. My laptop is a HP-Pavilion-
Laptop-15-cw1xxx, CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx.

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

Title:
  [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad
  L340-17API when in battery mode

Status in linux package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Xubuntu 20.04 shows black screen instead of login
  screen upon boot on Lenovo Ideapad L340-17API. It is not possible to
  chvt to text terminal when boot is stuck on black screen.

  Booting with 'nomodeset' kernel option works properly but is not an
  option (e.g. screen brightness is not adjustable in this case).

  Another workaround is to ssh to laptop and run systemctl restart
  display-manager.service. After 5-10 seconds upon executing this
  command perfectly working login screen appears.

  Check dmesg. There is apparently related messages from amdgpu driver:

  ...
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done
  апр 05 20:46:45 kernel: [drm] Skip scheduling IBs!
  апр 05 20:46:45 kernel: [ cut here ]
  апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at 
include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched]
  апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher 
af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec >
  апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G  
 OE 5.4.0-21-generic #25-Ubuntu
  апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 
07/11/2019
  апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched]
  апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 
[gpu_sched]
  апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 
48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf 
<0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c
  апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246
  апр 05 20:46:45 kernel: RAX:  RBX: 0001 RCX: 

  апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: 

  апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 
0004
  апр 05 20:46:45 kernel: R10:  R11: 0001 R12: 
8cc9ac463c00
  апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 
8cc9a6fc9140
  апр 05 20:46:45 kernel: FS:  () GS:8cc9b88c() 
knlGS:
  апр 05 20:46:45 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 
003406e0
  апр 05 20:46:45 kernel: Call Trace:
  апр 05 20:46:45 kernel:  amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu]
  апр 05 20:46:45 kernel:  amdgpu_job_timedout+0x103/0x130 

[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[C . Hintermüller]

I do observe the exactly same on a HP elitebook 840 G6 with the phone
pickup and hangup keys and other HP fancy keys i usually do not need.
They either mapp to left_ctrl left_meta or left_ctrl elft_alt.

Event: time 1594376396.025858, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1594376396.025858, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1594376396.025858, -- SYN_REPORT 
Event: time 1594376396.026015, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38
Event: time 1594376396.026015, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
Event: time 1594376396.026015, -- SYN_REPORT 
Event: time 1594376396.026120, type 4 (EV_MSC), code 4 (MSC_SCAN), value 65
Event: time 1594376396.026120, -- SYN_REPORT 

Event: time 1594376622.906330, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38
Event: time 1594376622.906330, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
Event: time 1594376622.906330, -- SYN_REPORT 
Event: time 1594376622.906498, type 4 (EV_MSC), code 4 (MSC_SCAN), value 66
Event: time 1594376622.906498, -- SYN_REPORT 
Event: time 1594376622.906682, type 4 (EV_MSC), code 4 (MSC_SCAN), value db
Event: time 1594376622.906682, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0
Event: time 1594376622.906682, -- SYN_REPORT 


Checking the scanvalue it turns out that pressing left_alt and left_ctrl 
produce the same individual key codes as returned for one key press of the 
special HP keys. 

 
Event: time 1594376291.093583, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38
Event: time 1594376291.093583, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
Event: time 1594376291.093583, -- SYN_REPORT 
Event: time 1594376291.240595, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38
Event: time 1594376291.240595, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
Event: time 1594376291.240595, -- SYN_REPORT 
Event: time 1594376295.981981, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1594376295.981981, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1594376295.981981, -- SYN_REPORT 
Event: time 1594376296.095764, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1594376296.095764, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0
Event: time 1594376296.095764, -- SYN_REPORT 


Looking at the scans it seems as if these special keys would produce three 
keystrokes at the same time  

code 0x1d, 0x38, 0x65
code 0x38, 0x66, 0xdb

The codes 0x65 and 0x66 seem to be ignored by the kernel or udev and
thus the keypress is seems to be shortened to

code 0x1d, 0x38 -> which maps to  and this is fatal in my
case cause directly underneath the phone hangup button with too little
space in between is the backspace button located. Yes!!! whenever i hit
inbetween the two keys the X-Server thinks I requested him to zap.

Looking at the event code table printed by evtest it seems as if the
code 101 = 0x65 is not used or mapped.

I tried to make an appropriate udev rule to map 0x65 and 0x66 to some
key but this is not applied thus i still stuck with having to too close
keys acting as ctrl alt bksp which is the good old Xorg zap combination
which i do not want to disable.

But whatever i try exempt reboot yet to map missing codes to keys does
not work. neither udev method nor setkeycodes in xorg works. nor reboot.

It is a bit unluckily annoying the situation, at least i know to
watchout when hitting backspace key not to accidentially also hit phone
hangup key.

I'm using kernel 5.3.0-40-lowlatency which is currently the latest
packaged by ubuntu hwe

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in linux package in Ubuntu:
  Triaged

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  

[Kernel-packages] [Bug 1752194] Re: Intel GPU tools crash with "Couldn't map MMIO region"

[simone-c]

Ubuntu 18, Intel(R) UHD Graphics 620

$ sudo intel_gpu_top 
(intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function 
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:832) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:832) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
  #0 [_init+0x7b87]
  #1 [_init+0x5420]
  #2 [_init+0xe85]
  #3 [__libc_start_main+0xe7]
  #4 [_init+0x1c92]
Test (null) failed.
 DEBUG 
(intel_gpu_top:832) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function 
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:832) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:832) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:832) igt-core-INFO: Stack trace:
(intel_gpu_top:832) igt-core-INFO:   #0 [_init+0x7b87]
(intel_gpu_top:832) igt-core-INFO:   #1 [_init+0x5420]
(intel_gpu_top:832) igt-core-INFO:   #2 [_init+0xe85]
(intel_gpu_top:832) igt-core-INFO:   #3 [__libc_start_main+0xe7]
(intel_gpu_top:832) igt-core-INFO:   #4 [_init+0x1c92]
  END  
FAIL (-1.000s)

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

Title:
  Intel GPU tools crash with "Couldn't map MMIO region"

Status in intel-gpu-tools package in Ubuntu:
  Confirmed

Bug description:
  Trying to run anything in intel-gpu-tools (tested intel_gpu_top, 
intel_gpu_time and intel_backlight) on my laptop (which has hybrid graphics, 
GTX 760m (proprietary nvidia driver not installed right now) + Intel 4th gen 
iGPU) as root yields the following output:
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function 
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not 
permitted
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
  Stack trace:
    #0 [_init+0x1753f]
    #1 [_init+0xc978]
    #2 [_init+0x118d]
    #3 [__libc_start_main+0xf1]
    #4 [_init+0x1fba]
    #5 [+0x1fba]
  Test (null) failed.
   DEBUG 
  (intel_gpu_top:23021) intel-chipset-DEBUG: Test requirement passed: pci_dev
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function 
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not 
permitted
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
  (intel_gpu_top:23021) igt-core-INFO: Stack trace:
  (intel_gpu_top:23021) igt-core-INFO:   #0 [_init+0x1753f]
  (intel_gpu_top:23021) igt-core-INFO:   #1 [_init+0xc978]
  (intel_gpu_top:23021) igt-core-INFO:   #2 [_init+0x118d]
  (intel_gpu_top:23021) igt-core-INFO:   #3 [__libc_start_main+0xf1]
  (intel_gpu_top:23021) igt-core-INFO:   #4 [_init+0x1fba]
  (intel_gpu_top:23021) igt-core-INFO:   #5 [+0x1fba]
    END  
  FAIL (-1.000s)

  Happens under bot Wayland and XOrg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: intel-gpu-tools 1.20-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 00:30:15 2018
  InstallationDate: Installed on 2015-11-25 (825 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to artful on 2017-11-01 (118 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1752194/+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 1870189] Re: initramfs does not get loaded

[Robert C Jennings]

Speaking of cloud-images generally I propose the following:

* Images in the ubuntu-cpc project by default should boot with an initramfs.
  * Revert the livecd-rootfs change which "Unconditionally set 
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an initramfs
  * Set GRUB_FORCE_PARTUUID as part of livefs-rootfs:live-build/functions 
replace_kernel() as this is used by the ubuntu-cpc project for each image that 
ships an optimized kernel intended to boot without initramfs.

Steve, I agree with everything you said in comment #21 about removing
not this functionality from Azure images.  I think there is room to
improve the experience for users that change their kernel and encounter
this behavior.  The panic/reboot behavior is unexpected and the mapping
of GRUB_FORCE_PARTUUID to initramfs-less boot is non-obvious to the end
user.  I don't immediately have suggestions to smooth this rough edge
but I feel that we need to take some time on this before completely
closing this bug out.

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

Title:
  initramfs does not get loaded

Status in cloud-images:
  New
Status in grub2 package in Ubuntu:
  Won't Fix
Status in linux-azure package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Triaged

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install

[J C Nash]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185 has link to
a kernel image that seems to fix the issue in at least my case. I am not
experienced enough in this arena to be sure if it is a duplicate.


JN

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

Title:
  5.3.0-53 Kernel system falis to reboot after install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cant post the requested terminal outputs because I can't install the 
kernel, but here is the system information: 
  System:Host: LM Kernel: 5.3.0-51-generic x86_64 bits: 64 compiler: gcc v: 
7.5.0 
 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 
19.3 Tricia 
 base: Ubuntu 18.04 bionic 
  Machine:   Type: Desktop Mobo: ASRock model: A300M-STX serial:  UEFI: 
American Megatrends 
 v: P3.60 date: 10/28/2019 
  Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: 
 charge: 55% 
 status: Discharging 
  CPU:   Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega 
Graphics bits: 64 
 type: MCP arch: Zen rev: 1 L2 cache: 2048 KiB 
 flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
bogomips: 28803 
 Speed: 1600 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1600 
2: 1600 3: 4000 
 4: 1600 
  Graphics:  Device-1: AMD Picasso driver: amdgpu v: kernel bus ID: 04:00.0 
chip ID: 1002:15d8 
 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa 
 resolution: 1920x1080~60Hz 
 OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.0-51-generic LLVM 
9.0.0) v: 4.5 Mesa 19.2.8 
 direct render: Yes 
  Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip 
ID: 1002:15de 
 Device-2: AMD vendor: ASRock driver: snd_hda_intel v: kernel bus 
ID: 04:00.6 
 chip ID: 1022:15e3 
 Sound Server: ALSA v: k5.3.0-51-generic 
  Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: 
iwlwifi v: kernel 
 bus ID: 02:00.0 chip ID: 8086:24fb 
 IF: wlp2s0 state: down mac:  
 Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: ASRock 
 driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 
10ec:8168 
 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:Local Storage: total: 350.27 GiB used: 18.08 GiB (5.2%) 
 ID-1: /dev/nvme0n1 vendor: Toshiba model: RD400 size: 238.47 GiB 
speed: 31.6 Gb/s 
 lanes: 4 serial:  
 ID-2: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 
GiB speed: 6.0 Gb/s 
 serial:  temp: 39 C 
  Partition: ID-1: / size: 233.26 GiB used: 10.51 GiB (4.5%) fs: ext4 dev: 
/dev/nvme0n1p2 
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
 Hub: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 
05e3:0608 
 Device-1: 1-3.1:3 info: Intel type: Bluetooth driver: btusb rev: 
2.0 chip ID: 8087:0aa7 
 Hub: 1-3.2:4 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 
05e3:0608 
 Device-2: 1-3.2.2:5 info: Logitech Illuminated Keyboard type: 
Keyboard,Mouse 
 driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c318 
 Device-3: 1-3.2.3:6 info: Logitech Unifying Receiver type: 
Mouse,HID 
 driver: logitech-djreceiver,usbhid rev: 2.0 chip ID: 046d:c52f 
 Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip 
ID: 1d6b:0003 
 Hub: 3-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 chip 
ID: 1d6b:0002 
 Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 chip 
ID: 1d6b:0003 
  Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Repos: No active apt repos in: /etc/apt/sources.list 
 Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable 
main
 Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
 1: deb [arch=amd64] http: //dl.google.com/linux/earth/deb/ stable 
main
 Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
 1: deb http: //mirror.clarkson.edu/linuxmint/packages tricia main 
upstream import backport
 2: deb http: //archive.linux.duke.edu/ubuntu bionic main 
restricted universe multiverse
 3: deb http: //archive.linux.duke.edu/ubuntu bionic-updates main 
restricted universe multiverse
 4: deb http: //archive.linux.duke.edu/ubuntu bionic-backports main 
restricted universe multiverse
 5

[Kernel-packages] [Bug 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx

[J C Nash]

Sorry. Meant 994 kernel booted and shut down OK. But I have 5.3.0-53
available to boot if some diagnostics are needed, though I plan to stay
on 51 until the dust settles.

JN

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

Title:
  fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I reset the previous kernel to be able to post, because it is very difficult 
to work like this, this happens randomly, intermittently with each application 
or without having anything open. It happened from the last update to kernel 
5.3, I suppose that it is the very new laptop since in another partition I have 
Kali and it happens the same. I appreciate your help, I list the 
characteristics of this laptop :roll:
  

  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz
  System:
  Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64
  compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic
  Machine:
  Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A
  serial: 
  Mobo: HP model: 84A2 v: 84.24 serial:  UEFI: AMI v: F.42
  date: 07/03/2019
  Battery:
  ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%)
  model: Hewlett-Packard Primary status: Charging
  CPU:
  Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx
  bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 19962
  Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398
  3: 1490 4: 1441
  Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
  vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0
  Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
  OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0)
  v: 4.5 Mesa 19.2.8 direct render: Yes
  Audio:
  Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
  bus ID: 04:00.1
  Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5
  Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
  bus ID: 04:00.6
  Sound Server: ALSA v: k5.0.0-32-generic
  Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0
  IF: eno1 state: down mac: 
  Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000
  bus ID: 03:00.0
  Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370]
  type: USB driver: rt2800usb bus ID: 1-3:3
  IF: wlxacf1df084ac8 state: up mac: 
  Drives:
  Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%)
  ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610
  size: 931.51 GiB
  Partition:
  ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5
  Sensors:
  System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C
  Fan Speeds (RPM): N/A
  Info:
  Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%)
  Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20
  inxi: 3.0.32

  
/
  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: yes
  Hard blocked: no
  1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  
/
  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state
  SecureBoot disabled
  Platform is in Setup Mode

  Ps: I also don't have wifi and bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx

[J C Nash]

I installed 
  linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb 
then 
  linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb
(because of dependency, has to be that order), and then rebooted and 
selected the 994 version (I have vmlinuz-5.3.0-51-generic as default, and 
can also choose -53- if desired).

It booted fine, and shut down seemingly correctly.

Do you want me to run any diagnostics or logs?

JN

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

Title:
  fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I reset the previous kernel to be able to post, because it is very difficult 
to work like this, this happens randomly, intermittently with each application 
or without having anything open. It happened from the last update to kernel 
5.3, I suppose that it is the very new laptop since in another partition I have 
Kali and it happens the same. I appreciate your help, I list the 
characteristics of this laptop :roll:
  

  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz
  System:
  Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64
  compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic
  Machine:
  Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A
  serial: 
  Mobo: HP model: 84A2 v: 84.24 serial:  UEFI: AMI v: F.42
  date: 07/03/2019
  Battery:
  ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%)
  model: Hewlett-Packard Primary status: Charging
  CPU:
  Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx
  bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 19962
  Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398
  3: 1490 4: 1441
  Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
  vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0
  Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
  OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0)
  v: 4.5 Mesa 19.2.8 direct render: Yes
  Audio:
  Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
  bus ID: 04:00.1
  Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5
  Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
  bus ID: 04:00.6
  Sound Server: ALSA v: k5.0.0-32-generic
  Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0
  IF: eno1 state: down mac: 
  Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000
  bus ID: 03:00.0
  Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370]
  type: USB driver: rt2800usb bus ID: 1-3:3
  IF: wlxacf1df084ac8 state: up mac: 
  Drives:
  Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%)
  ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610
  size: 931.51 GiB
  Partition:
  ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5
  Sensors:
  System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C
  Fan Speeds (RPM): N/A
  Info:
  Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%)
  Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20
  inxi: 3.0.32

  
/
  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: yes
  Hard blocked: no
  1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  
/
  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state
  SecureBoot disabled
  Platform is in Setup Mode

  Ps: I also don't have wifi and bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx

[J C Nash]

I'm running Linux Mint 19.3 Mate. I'm willing to put up a VirtualBox VM in 
20.04,
but really can't do a reinstall right now, as there's about a weeks' worth of 
custom updates. (I write application software for numerical stuff, but can't
pretend knowledge of kernel / module level stuff.)

However, am willing to try what I can.

Prof. J C Nash

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

Title:
  fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I reset the previous kernel to be able to post, because it is very difficult 
to work like this, this happens randomly, intermittently with each application 
or without having anything open. It happened from the last update to kernel 
5.3, I suppose that it is the very new laptop since in another partition I have 
Kali and it happens the same. I appreciate your help, I list the 
characteristics of this laptop :roll:
  

  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz
  System:
  Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64
  compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic
  Machine:
  Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A
  serial: 
  Mobo: HP model: 84A2 v: 84.24 serial:  UEFI: AMI v: F.42
  date: 07/03/2019
  Battery:
  ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%)
  model: Hewlett-Packard Primary status: Charging
  CPU:
  Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx
  bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 19962
  Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398
  3: 1490 4: 1441
  Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
  vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0
  Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
  OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0)
  v: 4.5 Mesa 19.2.8 direct render: Yes
  Audio:
  Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
  bus ID: 04:00.1
  Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5
  Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
  bus ID: 04:00.6
  Sound Server: ALSA v: k5.0.0-32-generic
  Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0
  IF: eno1 state: down mac: 
  Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000
  bus ID: 03:00.0
  Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370]
  type: USB driver: rt2800usb bus ID: 1-3:3
  IF: wlxacf1df084ac8 state: up mac: 
  Drives:
  Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%)
  ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610
  size: 931.51 GiB
  Partition:
  ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5
  Sensors:
  System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C
  Fan Speeds (RPM): N/A
  Info:
  Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%)
  Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20
  inxi: 3.0.32

  
/
  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: yes
  Hard blocked: no
  1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  
/
  ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state
  SecureBoot disabled
  Platform is in Setup Mode

  Ps: I also don't have wifi and bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1877007] Re: The chromium package broken

[C de-Avillez]

Adjusting package to chromium-browser.

Thank you for opening this bug and helping make Ubuntu better. Can you
please tell us what is wrong? You opened a bug against a browser, set
the package to the Linux kernel, and did not give us any explanations on
what would be broken.



** Package changed: linux (Ubuntu) => chromium-browser (Ubuntu)

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => 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/1877007

Title:
  The chromium package broken

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  he following packages will be upgraded:
chromium-browser
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/48.3 kB of archives.
  After this operation, 230 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  Preconfiguring packages ...
  (Reading database ... 410692 files and directories currently installed.)
  Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ==> Installing the chromium snap

  Progress: [ 14%]
  [..]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norah  2690 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 08:47:12 2020
  HibernationDevice: RESUME=UUID=ae9d7101-3e17-4133-ac4b-c4b858d77858
  InstallationDate: Installed on 2017-09-02 (976 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 90E8CTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M05KT54A
  dmi.board.name: SKYBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NOK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrM05KT54A:bd02/24/2016:svnLENOVO:pn90E8CTO1WW:pvrYangTianM4900c-00:rvnLENOVO:rnSKYBAY:rvrNOK:cvnLENOVO:ct3:cvr:
  dmi.product.family: YangTianM4900c-00
  dmi.product.name: 90E8CTO1WW
  dmi.product.sku: LENOVO_MT_90E8_BU_LENOVO_FM_YangTianM4900c-00
  dmi.product.version: YangTianM4900c-00
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877007/+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 1873809] Re: disk-kvm.img aren't UEFI bootable

[Robert C Jennings]

@colin-king, Can we get that config option added for this kernel?

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

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

Title:
  disk-kvm.img aren't UEFI bootable

Status in cloud-images:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  The `disk-kvm.img` images which are to be preferred when run under
  virtualization, completely fail to boot under UEFI.

  This is a critical issue as those are the images that LXD is now
  pulling by default.

  User report on the LXD side: https://github.com/lxc/lxd/issues/7224

  Note that the non optimized images boot just fine (disk1.img).

  
  I've reproduced this issue with:
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda 
focal-server-cloudimg-amd64-disk-kvm.img -m 1G

  
  On the graphical console, you'll see EDK2 load (TianoCore) followed by basic 
boot messages and then a message from grub (error: can't find command 
`hwmatch`).
  Those also appear on successful boots of other images so I don't think 
there's anything concerning that. However it'll hang indefinitely and eat up 
all your CPU.

  Switching to the text console view (serial0), you'll see the same
  issue as that LXD report:

  BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found
  BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  error: can't find command `hwmatch'.
  e X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 
 
  ExceptionData - 
  RIP  - 3FF2DA12, CS  - 0038, RFLAGS - 00200202
  RAX  - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF
  RBX  - 0398, RSP - 3FF1C638, RBP - 3FF34360
  RSI  - 3FF343B8, RDI - 1000
  R8   - 3E80F108, R9  - 3E815B98, R10 - 0065
  R11  - 2501, R12 - 0004, R13 - 3E80F100
  R14  - , R15 - 
  DS   - 0030, ES  - 0030, FS  - 0030
  GS   - 0030, SS  - 0030
  CR0  - 80010033, CR2 - , CR3 - 3FC01000
  CR4  - 0668, CR8 - 
  DR0  - , DR1 - , DR2 - 
  DR3  - , DR6 - 0FF0, DR7 - 0400
  GDTR - 3FBEEA98 0047, LDTR - 
  IDTR - 3F2D8018 0FFF,   TR - 
  FXSAVE_STATE - 3FF1C290
   Find image based on IP(0x3FF2DA12) 
/build/edk2-dQLD17/edk2-0~20191122.bd85bf54/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll
 (ImageBase=3FF1E000, EntryPoint=3FF30781) 


  If booting in a SecureBoot enabled environment, you instead get a
  `Access Denied` at kernel loading time, indicating that the kernel
  binary isn't a normal signed kernel. That has the same result (boot
  hangs) but without the crash message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873809/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic

[Robert C Jennings]

** Tags added: champagne

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

Title:
  depmod ERROR during Setting up linux-modules-5.4.0-17-generic

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Deploy Focal on a KVM ndoe, enable proposed
  2. Run sudo apt dist-upgrade

  The console will be flushed with:
  Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ...
  Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ...
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin'
  
  Setting up apt-utils (1.9.12) ...
  Setting up libselinux1-dev:amd64 (3.0-1build2) ...
  Setting up libglib2.0-0:amd64 (2.64.0-1) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  4 08:29 seq
   crw-rw 1 root audio 116, 33 Mar  4 08:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar  4 09:06:42 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-5.4
  StagingDrivers: exfat
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

Daniel.. anything else i should try to equip you with more info to debug
this?

Thanks.

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

1.  Added to /etc/X11/Xwrapper.config : needs_root_rights = yes (as instructed 
in bug 1716857.
2. Open terminal, input "sudo apt install nvidia-driver-390".
3. After installation complete, input "systemctl reboot" to reboot.
4. Screen went blank on reboot, cursor blinking at around the top left corner.
5. Pressed Alt Ctrl F2 to bring up tty2, then input "sudo apt-get remove 
--purge nvidia-*" to remove nvidia driver.
6. After removal complete, input "systemctl reboot" to reboot.
7. Reboot OK. System OK with Nouveau driver.
8. Ran journalctl to generate attached  

Summary: bug 1716857 didn't help.

** Attachment added: "boot-1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331457/+files/boot-1.txt

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

to add, after step 4:

4a.  i waited a little longer and noticed a jagged dialogue window
popped up (attached).  i tried to input my password, but neither mouse
nor keyboard was functional.   i waited again, and later proceeded to
resume at step 5.

** Attachment added: "dialogue box.jpeg"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331458/+files/dialogue%20box.jpeg

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

thanks in advance

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

** Attachment added: "boot-5.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331433/+files/boot-5.txt

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

** Attachment added: "boot-4.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331432/+files/boot-4.txt

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

** Attachment added: "boot-3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331431/+files/boot-3.txt

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

** Attachment added: "boot-2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331430/+files/boot-2.txt

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[C Chan]

Thanks Daniel... i did what you requested.   Following is a recap of the
process, FYI:

1. System running Nouveau driver.  All OK.  
2. Open terminal, input "sudo apt install nvidia-driver-390".
3. After installation complete, input "systemctl reboot" to reboot.
4. Screen went blank on reboot, cursor blinking at around the top left corner.
5. Pressed Alt Ctrl F2 to bring up tty2, then input "sudo apt-get remove 
--purge nvidia-*" to remove nvidia driver.
6. After removal complete, input "systemctl reboot" to reboot.
7. Reboot OK.  System OK with Nouveau driver.
8. Ran journalctl 5 times to generate the attached 5 files.

Here are the 5 journals.

Thanks.

** Attachment added: "boot-1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331429/+files/boot-1.txt

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System failed to boot when nvidia-390 was installed

[C Chan]

2 of 5

** Attachment added: "boot-2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331177/+files/boot-2.txt

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

Title:
  System failed to boot when nvidia-390 was installed

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System failed to boot when nvidia-390 was installed

[C Chan]

4 of 5

** Attachment added: "boot-4.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331179/+files/boot-4.txt

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

Title:
  System failed to boot when nvidia-390 was installed

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System failed to boot when nvidia-390 was installed

[C Chan]

3 of 5

** Attachment added: "boot-3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331178/+files/boot-3.txt

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

Title:
  System failed to boot when nvidia-390 was installed

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System failed to boot when nvidia-390 was installed

[C Chan]

5 of 5

** Attachment added: "boot-5.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331180/+files/boot-5.txt

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

Title:
  System failed to boot when nvidia-390 was installed

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1864781] Re: System failed to boot when nvidia-390 was installed

[C Chan]

1st attachment of 5(1 of 5)


** Attachment added: "boot-1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331176/+files/boot-1.txt

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

Title:
  System failed to boot when nvidia-390 was installed

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+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 1764246] Re: kdump kernel panics on Bionic

[C de-Avillez]

I had two up-to-date Azure instances (16.04 and 18.04) where Linux-
crashdump was installed. Both failed, with the following being shown at
the end of the serial console:

[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[   18.407975] Out of memory: Kill process 496 (cloud-init) score 127 or 
sacrifice child
[   18.417791] Killed process 496 (cloud-init) total-vm:66840kB, 
anon-rss:12720kB, file-rss:0kB, shmem-rss:0kB
[FAILED] Failed to start Initial cloud-init job (pre-networking).
See 'systemctl status cloud-init-local.service' for details.
[  OK  ] Reached target Network (Pre).
 Starting Network Service...
[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
 Starting Wait for Network to be Configured...
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[   37.269354] Out of memory: Kill process 657 (snap) score 40 or sacrifice 
child
[   37.282042] Killed process 657 (snap) total-vm:95160kB, anon-rss:4008kB, 
file-rss:0kB, shmem-rss:0kB
[* ] (2 of 3) A start job is running for… to be Configured (32s / no 
limit)[   47.413761] Out of memory: Kill process 656 (snap) score 41 or 
sacrifice child
[   47.422837] Killed process 656 (snap) total-vm:242624kB, anon-rss:4072kB, 
file-rss:0kB, shmem-rss:0kB
[  OK  ] Found device Virtual_Disk 1.
 Starting File System Check on /dev/disk/cloud/azure_resource-part1...
[ ***  ] (3 of 3) A start job is running for…re_resource-part1 (44s / no 
limit)[   56.870810] Out of memory: Kill process 662 (snap) score 41 or 
sacrifice child
[   56.887294] Killed process 662 (snap) total-vm:242880kB, anon-rss:4116kB, 
file-rss:0kB, shmem-rss:0kB
[  OK  ] Started File System Check Daemon to report status.
[   71.643108] Out of memory: Kill process 660 (snap) score 42 or sacrifice 
child
[   71.652187] Killed process 660 (snap) total-vm:242880kB, anon-rss:4220kB, 
file-rss:0kB, shmem-rss:0kB
[  OK  ] Started File System Check on /dev/disk/cloud/azure_resource-part1.
[ TIME ] Timed out waiting for device dev-disk-by\x2dlabel-UEFI.device.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File Systems.
[  OK  ] Started Emergency Shell.
[  OK  ] Reached target Emergency Mode.
[  114.872426] Out of memory: Kill process 655 (snap) score 49 or sacrifice 
child
[  114.881579] Killed process 655 (snap) total-vm:243936kB, anon-rss:4844kB, 
file-rss:0kB, shmem-rss:0kB
 Starting Tell Plymouth To Write Out Runtime Data...
 Starting Create Volatile Files and Directories...
 Starting AppArmor initialization...
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):

So, no more kernel panics, but
  (1) still no kdump saved;
  (2) the servers end waiting for user intervention (which is quite bad for a 
cloud instance).

Both servers had a cmdline with "crashkernel=512M-:192M". I edited
/etc/default/grub.d/kdump-tools.cfg, changed crashkernel to 256M, and
ran update-grub.

Re-tested, and it worked.

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

Title:
  kdump kernel panics on Bionic

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

Bug description:
  The kdump/crashdump kernel is panicing during boot on Bionic.

  1) Install the daily Bionic server or desktop ISO
  2) apt install linux-crashdump, say yes to kdump being enabled
  3) Reboot so as to boot with the correct kernel parameter
  4) Run:
  root@bionic-server:~# echo 1 > /proc/sys/kernel/sysrq 
  root@bionic-server:~# echo c > /proc/sysrq-trigger 
  5) Observe that the crashdump kernel panics before booting with an 
out-of-memory error. Log below.

  If I replace the bionic image with the artful cloud image, and repeat
  steps 2-4, the crashdump kernel boots and successfully stores the
  vmcore.

  The full log:

  [   54.424512] sysrq: SysRq : Trigger a crash
  [   54.427899] BUG: unable to handle kernel NULL pointer dereference at 

  [   54.433915] IP: sysrq_handle_crash+0x16/0x20
  [   54.437157] PGD 0 P4D 0 
  [   54.439292] Oops: 0002 [#1] SMP PTI
  [   54.444571] Modules linked in: snd_hda_codec_generic crct10dif_pclmul 
crc32_pclmul snd_hda_intel ghash_clmulni_intel snd_hda_codec snd_hda_core 
snd_hwdep input_leds joydev snd_pcm serio_raw snd_timer snd soundcore 
qemu_fw_cfg mac_hid sch_fq_codel 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 l

[Kernel-packages] [Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT

[Robert C Jennings]

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

Title:
  Xenial images won't reboot if disk size is > 2TB when using GPT

Status in cloud-init:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
  CPC team has recently converted Xenial images to use GPT instead of
  MBR.  However, after booting an instance that has a disk size of 2049
  GB or higher, we hang on the next subsequent boot (Logs indicate it
  hanging on "Booting Hard Disk 0".

  This works on Bionic, but what makes it strange is that they have the
  same kernel revision - 4.15.0-1-37.

  patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp
  ii  linux-gcp4.15.0.1037.51   
 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers
  ii  linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1   
 amd64Header files related to Linux kernel version 4.15.0

  To reproduce:

  1) Create an image with a disk size of 3072 using a serial that has GPT
  gcloud compute instances create test-3072-xenial --image 
daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel 
--boot-disk-size 3072

  Reboot the instance

  2) It will hang on reboot and you cannot connect

  3) Please note that later serials have the GPT change reverted.

  You can replace xenial with bionic in the above commands to get a
  bionic instance instead.


  To test this out in a more slower fashion:

  
  1) Create an image with a disk size of 2048 using a serial that has GPT
  gcloud compute instances create test-2048-xenial --image 
daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel 
--boot-disk-size 2048

  2) Resize the disk to 3072

  3) Issue growpart /dev/sda 1

  4) Issue resize2fs /dev/sda1

  5) Issue rsize2fs /dev/sda1 instead

  On the second resize2fs, it tries to resize again, but on a working
  instance, it says there's nothing to resize.

  
  I've tried starting from a Xenial instance and doing a do-release-upgrade to 
get to bionic and then doing the growpart/resize2fs, but the issue still shows 
up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1840686/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[B. C. Schmerker]

Update:  Issue worked around with nVIDIA® geForce® driver 340.107 for
C77 GPU in MCP78 northbridge (package:nvidia-340).  Repeating report to
Bug 1776616.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

[B. C. Schmerker]

Update:  nVIDIA® geForce® driver 340.107 for the C77 GPU (package:
nvidia-340) got to a successful power-down.  Be advised that Packages
nvidia-n are to be reserved for nVIDIA® nFORCE® MCP chipsets such as the
MCP78 northbridge my EL1210-09; intel®, AMD®, and VIA® chipsets require
different solutions.

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

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

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[B. C. Schmerker]

Update:  acpi=off only got me to a timestamped kernel message
"reboot:System halted".  acpi=force had no effect.  Repeating report to
Bug 1776616, which is specifically relevant to Kernel 4.15-n-generic on
xubuntu™ 18.04-LTS.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

[B. C. Schmerker]

I encountered this issue installing xubuntu™ 18.04-LTS on an
emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon®
LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a
Shuttle® PSU upgrade (PC631 in for stock 220W LITEON®) and the
planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an
msi® N610GT-MD1GD3/LP half-height video display adapter. I normally use:

GRUB_CMDLINE_LINUX_DEFAULT="debug"

in /etc/default/grub, which is how I confirmed the issue: Depending on
shutdown or reboot option, the system halts at "Starting reboot..." or
"Starting power-off...", forcing a manual power-down.  Additionally:

GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=force"

had no effect, and:

GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=off"

only got me to a timestamped "reboot:System halted".  Will report back
after checking effect of nVIDIA® geForce® driver package for C77 GPU
(part of nF720 chipset).

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

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

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[B. C. Schmerker]

This hang on shutdown and/or reboot is NOT confined to portables.  I
encountered the issue installing xubuntu™ 18.04-LTS on an
emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon®
LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a
Shuttle® PSU upgrade (PC631 in for stock 220W LITEON®) and the
planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an
msi® N610GT-MD1GD3/LP half-height video display adapter.  I normally
use:

GRUB_CMDLINE_LINUX_DEFAULT="debug"

in /etc/default/grub, which is how I confirmed the issue:  Depending on
shutdown or reboot option, the system halts at "Starting reboot..." or
"Starting power-off...", forcing a manual power-down.  Will report back
after testing:

GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=off"

and:

GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=force"

I'd rather save the C77 geForce® driver set (provided to Canonical Ltd.
by nVidia Corporation) for the nFORCE® 720 as a last resort, as it
affects Kernel behavior in both startup and shutdown.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

[Daniel C]

** Attachment removed: "dmesg output after Wi-Fi crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279667/+files/wifi-crash-2019-07-28.txt

** Attachment added: "dmesg output after Wi-Fi crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279668/+files/wifi-crash-2019-07-28.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/1818881

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  firmware:   ath10k/QCA9887/hw1.0/board.bin
  firmware:   ath10k/QCA9887/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/board-2.bin
  firmware:   ath10k/QCA988X/hw2.0/board.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-4.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-3.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-2.bin
  license:Dual BSD/GPL
  description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB 
devices
  author: Qualcomm Atheros
  srcversion: 

[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing

[Daniel C]

I still hit this issue a few times per week, usually after resuming from
suspend.

I've attached the dmesg output from the most recent one (today). In this
instance, although the Wi-Fi was not working, I was still able to
interact with the system and shut it down cleanly. That's not always the
case - sometimes the running system is corrupted and I can't even
shutdown cleanly but have to do a hard power-off with the power button.

This is with all the latest updates applied on 19.04.

Kernel: Linux daniel-XPS-13-9380 5.0.0-21-generic #22-Ubuntu SMP Tue Jul
2 13:27:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Is there anything in the pipeline that will help with this? Any contacts
at Dell, or Qualcomm / Atheros?

This is after all a certified Ubuntu laptop.

** Attachment added: "dmesg output after Wi-Fi crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279667/+files/wifi-crash-2019-07-28.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/1818881

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  

[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

[Daniel C]

Hi Thomas, that sounds very similar to what we are seeing over in bug
1827790.

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+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 1828101] Re: [linux-azure] Disk Partition Issue

[Robert C Jennings]

This is as expected, the root partition in the registered image will not
match the size of the disk that is deployed.  It will be large enough to
contain the root partition and provide some blank space.  This is by
design and allows VMs to be started with variable size disks.  This is
seen early in boot before cloud-init runs and because the disk from the
image builder is smaller it will leave the gpt backup table in the
middle of the deployed disk, but this is safe.  One of the early cloud-
init modules is growpart[1] and there's good documentation in the link
for that module, but by default that module will grow the partition for
the root filesystem to fill the disk and then grow the filesystem to
fill that partition.  In doing this the gpt backup table will be moved
to a location correct for the root disk size at deployemtn; this is why
you don't see the warning after reboot.  In addition to giving
flexibility for launching with different size root disks the user can
instruct cloud-init not to resize the root filesystem[2][3] and instead
use the unused space to create other partitions and filesystems[4].


[1] https://git.launchpad.net/cloud-init/tree/cloudinit/config/cc_growpart.py
[2] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart
[3] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#resizefs
[4] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#disk-setup

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

Title:
  [linux-azure] Disk Partition Issue

Status in linux-azure package in Ubuntu:
  New

Bug description:
  In testing with the “Canonical UbuntuServer 19.04 latest” image from
  the Azure Marketplace, we’re seeing these lines output in dmesg:

  lisa@LISAv2-OneVM8NIC-v-stlups-AQ63-20190507075423-role-0:~$ dmesg | grep GPT
  [   17.228278] GPT:Primary header thinks Alt. header is not at the end of the 
disk.
  [   17.237240] GPT:4612095 != 62914559
  [   17.259079] GPT:Alternate GPT header not at the end of the disk.
  [   17.259080] GPT:4612095 != 62914559
  [   17.259080] GPT: Use GNU Parted to correct GPT errors.

  It looks like maybe the disk partition structure in the image isn’t
  quite correct.  Linux continues to boot, and the reported errors don’t
  cause any obvious problems, but it seems like this is something that
  should be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828101/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

Tested on my machine and yes it appears to be fixed.

Thank you to those who made it happen and thank you Andreas for letting
us know.

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

The same for me, 4.4.0-141 does not help.

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

4.4.0-140 does not solve the problem for me either (had to revert back
to 4.4.0-138).

The first time I tried 4.4.0-140 the system locked up, but there was no
kernel crash stacktrace and I was able to use the Magic SysRq key
combination to avoid a hardware reboot.

The second time I tried 4.4.0-140 the system locked up, but I was not able to 
use Magic SysRq to avoid a hardware reboot.
Yet the kernel crash logging changed, producing about three different 
stacktraces over the span of about 30 seconds (before the logs froze).

Unfortunately the crash logs did not persist to disk.

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

Yes, it only started occurring within the last few weeks/month.

I can confirm that booting the previous (but still installed) kernel,
fixes the problem.

$ uname -a
Linux metabox 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

That kernel works for me, so the issue must be in the "139" version.

I did not try the latest upstream kernel because I have NVIDIA drivers
and Virtualbox installed and I'd rather not go through the hassle of
uninstalling all custom modules, if I can avoid it.

Do you still need me to try the latest upstream?

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1803929/+attachment/5214102/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214100/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214099/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214103/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214098/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214095/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1803929/+attachment/5214090/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1803929/+attachment/5214101/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1803929/+attachment/5214094/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214097/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214092/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

apport information

** Tags added: apport-collected

** Description changed:

  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  
  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  
  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".
  
  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.
  
  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX
  
  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).
  
- I can't get a textual copy of the kernel bug log (because I have to do a
- hard reset to regain control of the system and the output doesn't get
- flushed to disk), but I did manage to get a photo of some of it (please
- refer to attachment).
+ I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
+  /dev/snd/controlC1:  matt   2754 F pulseaudio
+  /dev/snd/controlC0:  matt   2754 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
+ InstallationDate: Installed on 2016-04-23 (940 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ MachineType: Notebook N150SD/N155SD
+ NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-139-generic N/A
+  linux-backports-modules-4.4.0-139-generic  N/A
+  linux-firmware 1.157.20
+ Tags:  xenial
+ Uname: Linux 4.4.0-139-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 03/31/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.03.05
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: N150SD/N155SD
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
+ dmi.product.name: N150SD/N155SD
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: Notebook

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214089/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  

[Kernel-packages] [Bug 1803929] ProcCpuinfoMinimal.txt

[Matt C]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214096/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1803929/+attachment/5214093/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Matt C]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214091/+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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] [NEW] Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

Public bug reported:

lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04

uname -a
Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

Steps (1) to reproduce:
1) Plug in a USB3 hard drive.
2) Right click on launcher icon.
3) Select "Safely Remove".

After finding this: https://askubuntu.com/a/532691
...the following steps also reproduce the problem.

Steps (2) to reproduce:
1) Plugin in a USB3 hard drive.
2) udisksctl unmount -b /dev/sdXY
3) udisksctl power-off -b /dev/sdX

System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

I can't get a textual copy of the kernel bug log (because I have to do a
hard reset to regain control of the system and the output doesn't get
flushed to disk), but I did manage to get a photo of some of it (please
refer to attachment).

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


** Tags: xenial

** Attachment added: "stack-trace.jpg"
   
https://bugs.launchpad.net/bugs/1803929/+attachment/5214085/+files/stack-trace.jpg

** Attachment removed: "stack-trace.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+attachment/5214085/+files/stack-trace.jpg

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do
  a hard reset to regain control of the system and the output doesn't
  get flushed to disk), but I did manage to get a photo of some of it
  (please refer to attachment).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

** Attachment added: "stack-trace.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+attachment/5214086/+files/stack-trace.jpg

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do
  a hard reset to regain control of the system and the output doesn't
  get flushed to disk), but I did manage to get a photo of some of it
  (please refer to attachment).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

[Ryan C. Underwood]

This should be bisectable, but I don't think anyone has done it yet...

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1799083] Re: virtual console unavailable with upgrade of cosmic or Ubuntu 18.10

[C Peters II]

The issue is happening again.

Yesterday I removed the test kernels and upon booting up today the
virtual terminal (VT) were missing (running both kernel package
v4.18.0-10-11 and 4.15.0-36.39).  Tried adding NAutoVTs=4 in
/etc/systemd/logind.conf and VT's are working again...

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

Title:
  virtual console unavailable with upgrade of cosmic or Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual terminal Alt F1-F6 will not display a login prompt.  Kernel
  package 4.18.0-10.11

  Using the older release kernel package 4.15.0-33.36, the virtual
  terminals work as normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cp 2209 F pulseaudio
   /dev/snd/controlC0:  cp 2209 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sun Oct 21 15:00:23 2018
  HibernationDevice: RESUME=UUID=c8402f14-cff8-4ea7-b7c0-e290ac74c235
  InstallationDate: Installed on 2018-04-21 (183 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=8943f032-77a1-4075-83a8-648f2115f371 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 01/16/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.asset.tag: 20KYFS1L
  dmi.board.name: 0692FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 20KYFS1L
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/16/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799083/+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 1799083] Re: virtual console unavailable with upgrade of cosmic or Ubuntu 18.10

[C Peters II]

> Did this issue start happening after an update/upgrade?

Yes, it happened after the upgrade to Ubuntu 18.10.   The subject of the bug 
report was "virtual console unavailable with upgrade of cosmic or Ubuntu 
18.10".  The logs included in my original bug report showed "UpgradeStatus: 
Upgraded to cosmic on 2018-10-20 (1 days ago)".
 
> Was there a prior kernel version where you were not having this particular 
> problem?

Yes.  My bug report said "Using the older release kernel package 4.15.0-33.36, 
the virtual terminals work as normal."
 
> Would it be possible for you to test the latest upstream kernel?

Yes.  I tested kernel v4.19-rc8 and kernel v4.19.

After the initial upgrade of Ubuntu 18.10 I noticed the problem
immediately because I often login to the virtual terminal so that I can
killall chrome or killall firefox when the laptop becomes sluggish from
running out of memory.  I searched online and bug reports and tried a
few things attempting to resolve the issue.  I also compared cat
/proc/cmdline of the two kernels running and a few other things which
didn't help.

Another thing I tried after finding some info on either stack exchange
or the Ubuntu forums was to uncomment #NAutoVTs=6
/etc/systemd/logind.conf and after checking the logind.conf(5) man page
I changed it to NAutoVTs=4.  It seemed to do nothing with the new kernel
4.18.0-10.11, and the 4.15.0-33.36 kernel displayed tty 1-4 and 6, but
not tty5.  so I changed the file back..   Then here's where things make
even less sense, tty 1-6 all work now.  One thing that was odd is I did
a pstree -ap and only tty1 showed up, then logged into tty1, went back
to the graphical Lubuntu terminal and all 6 tty's or agetty processes
were active.  It seems that if agetty tty1 is spawned the others
activate when I enter alt-F2 etc...

So this doesn't make a lot of sense because reverting the only change
made in /etc/systemd/logind.conf seems to have fixed the problem running
kernel package v4.18.0-10.


Kernel testing:
v4.19-rc8 
Virtual terminals were working.

kernel v4.19
Virtual terminals were not working.  Furthermore the login.conf change didn't 
seem to fix the issue.

kernel v4.18.0-10
Virtual terminals are working.


In other words the results are somewhat confusing because it seems to be 
producing random results.  It's not clear that the bug is in the kernel, it 
could be systemd, agetty, system libraries or an interaction of the various 
components.

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

Title:
  virtual console unavailable with upgrade of cosmic or Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual terminal Alt F1-F6 will not display a login prompt.  Kernel
  package 4.18.0-10.11

  Using the older release kernel package 4.15.0-33.36, the virtual
  terminals work as normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cp 2209 F pulseaudio
   /dev/snd/controlC0:  cp 2209 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sun Oct 21 15:00:23 2018
  HibernationDevice: RESUME=UUID=c8402f14-cff8-4ea7-b7c0-e290ac74c235
  InstallationDate: Installed on 2018-04-21 (183 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=8943f032-77a1-4075-83a8-648f2115f371 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 01/16/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.asset.tag: 20KYFS1L
  dmi.board.name: 0692FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 20KYFS1L
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/16/2012:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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