[Kernel-packages] [Bug 1878635] [NEW] Intel Titan Ridge TB3 USB Controller prevents system from suspending

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The dmesg log states the following:
PM: Device :0f:00.0 failed to suspend async: error -110

When checking lspci this points to the following device:
0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller 
[Titan Ridge 2C 2018] (rev 06)
which is the integrated Thunderbolt 3 Controller of the ITX Motherboard.

I will still try suspending without a Thunderbolt 3 Dock attached.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  spyfly 2424 F pulseaudio
 /dev/snd/controlC3:  spyfly 2424 F pulseaudio
 /dev/snd/controlC1:  spyfly 2424 F pulseaudio
 /dev/snd/controlC2:  spyfly 2424 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 14 17:09:55 2020
HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2
InstallationDate: Installed on 2018-09-06 (616 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.78
dmi.board.name: X570 Phantom Gaming-ITX/TB3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal
-- 
Intel Titan Ridge TB3 USB Controller prevents system from suspending
https://bugs.launchpad.net/bugs/1878635
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1878635] Re: Intel Titan Ridge TB3 USB Controller prevents system from suspending

[Kai-Heng Feng]

** Package changed: powermgmt-base (Ubuntu) => linux (Ubuntu)

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

Title:
  Intel Titan Ridge TB3 USB Controller prevents system from suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The dmesg log states the following:
  PM: Device :0f:00.0 failed to suspend async: error -110

  When checking lspci this points to the following device:
  0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  which is the integrated Thunderbolt 3 Controller of the ITX Motherboard.

  I will still try suspending without a Thunderbolt 3 Dock attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spyfly 2424 F pulseaudio
   /dev/snd/controlC3:  spyfly 2424 F pulseaudio
   /dev/snd/controlC1:  spyfly 2424 F pulseaudio
   /dev/snd/controlC2:  spyfly 2424 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 17:09:55 2020
  HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2
  InstallationDate: Installed on 2018-09-06 (616 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.78
  dmi.board.name: X570 Phantom Gaming-ITX/TB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878635/+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 1878782] Re: Bluetooth is on but scanned devices are not showing.

[Daniel van Vugt]

While the problem is happening please run:

  rfkill > rfkill.txt

in a terminal and then attach the resulting file here.

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

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

Title:
  Bluetooth is on but scanned devices are not showing.

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth in spite of being switched on, shows the same image as when
  it is off in the paired devices menu. I cannot access my paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 13:48:16 2020
  InstallationDate: Installed on 2020-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1TCN27WW(V2.08)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
  dmi.product.family: ideapad 110-15ISK
  dmi.product.name: 80UD
  dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
  dmi.product.version: Lenovo ideapad 110-15ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878782/+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 1878670] Re: Gnome crash frequently

[Daniel van Vugt]

OK then. Let's ignore the Gnome part and make this bug just about the
kernel crash (which is *probably* what you also see in Gnome).


** Summary changed:

- Gnome crash frequently
+ i915 crashes hsw_power_well_enable

** No longer affects: gnome-shell (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/1878670

Title:
  i915 crashes hsw_power_well_enable

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

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Harald Leinders]

I can confirm THAT also:

root@Scotty:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu
I: The initramfs will attempt to resume from /dev/sdc3
I: (UUID=0d56817f-d127-457b-b6e1-5fd642a9520b)
I: Set the RESUME variable to override this.

So this doesn't has to do anything with 3rd-Party-PPA's because I don't
have any. It's after a fresh install.

BUT update-initramfs doesn't throw any error anymore and runs through to
the end. There are only the warnings left.

The system works well with this, after a reboot there are no problems
despite these warnings:

root@Scotty:/boot# ll
insgesamt 189597
drwxr-xr-x  4 root root 4096 Mai 18 08:08 ./
drwxr-xr-x 20 root root 4096 Mai 16 17:27 ../
-rw-r--r--  1 root root   237718 Apr 20 18:33 config-5.4.0-26-generic
-rw-r--r--  1 root root   237718 Apr 29 15:34 config-5.4.0-29-generic
drwx--  3 root root  512 Jan  1  1970 efi/
drwxr-xr-x  4 root root 4096 Mai 16 17:33 grub/
lrwxrwxrwx  1 root root   27 Mai 16 17:33 initrd.img -> 
initrd.img-5.4.0-29-generic
-rw-r--r--  1 root root 80142634 Mai 16 17:31 initrd.img-5.4.0-26-generic
-rw-r--r--  1 root root 80142137 Mai 18 08:08 initrd.img-5.4.0-29-generic
lrwxrwxrwx  1 root root   27 Mai 16 17:25 initrd.img.old -> 
initrd.img-5.4.0-26-generic
-rw-r--r--  1 root root   182704 Feb 14 00:09 memtest86+.bin
-rw-r--r--  1 root root   184380 Feb 14 00:09 memtest86+.elf
-rw-r--r--  1 root root   184884 Feb 14 00:09 memtest86+_multiboot.bin
-rw---  1 root root  4736015 Apr 20 18:33 System.map-5.4.0-26-generic
-rw---  1 root root  4736015 Apr 29 15:34 System.map-5.4.0-29-generic
lrwxrwxrwx  1 root root   24 Mai 16 17:33 vmlinuz -> 
vmlinuz-5.4.0-29-generic
-rw-r--r--  1 root root 11657976 Apr 23 09:55 vmlinuz-5.4.0-26-generic
-rw---  1 root root 11657976 Apr 29 15:54 vmlinuz-5.4.0-29-generic
lrwxrwxrwx  1 root root   24 Mai 16 17:33 vmlinuz.old -> 
vmlinuz-5.4.0-26-generic
root@Schrotty:/boot# uname -a
Linux Scotty 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
root@Scotty:/boot# date
Mo 18. Mai 08:14:51 CEST 2020

The initrd.img-5.4.0-29-generic was built successfully an works well and
the amdgpu is loaded, if it works or not.

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New

Bug description:
  SRU Justification

  Impact: amdgpu references firmware files in modinfo which have not
  been supplied to linux-firmware. This causes update-initramfs to
  generate "Possible missing firmware" warnings.

  Fix: Since the firmware is not available, all we can do is remove the
  files from modinfo.

  Test Case: Confirm that update-initramfs no longer produces the
  warnings.

  Regression Potential: Low. If someone had managed to obtain these
  files they will no longer be added to the initramfs, potentially
  causing regressions for these users. This would be an atypical
  situation.

  ---

  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu

  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+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 1878635] Re: Intel Titan Ridge TB3 USB Controller prevents system from suspending

[Sebastian Heiden]

** Package changed: linux (Ubuntu) => powermgmt-base (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/1878635

Title:
  Intel Titan Ridge TB3 USB Controller prevents system from suspending

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  The dmesg log states the following:
  PM: Device :0f:00.0 failed to suspend async: error -110

  When checking lspci this points to the following device:
  0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  which is the integrated Thunderbolt 3 Controller of the ITX Motherboard.

  I will still try suspending without a Thunderbolt 3 Dock attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spyfly 2424 F pulseaudio
   /dev/snd/controlC3:  spyfly 2424 F pulseaudio
   /dev/snd/controlC1:  spyfly 2424 F pulseaudio
   /dev/snd/controlC2:  spyfly 2424 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 17:09:55 2020
  HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2
  InstallationDate: Installed on 2018-09-06 (616 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.78
  dmi.board.name: X570 Phantom Gaming-ITX/TB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1878635/+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 1878271] Re: rpi: no uboot or kernel boot mesages on console during boot on core20

[Juerg Haefliger]

** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)

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

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

Title:
  rpi: no uboot or kernel boot mesages on console during boot on core20

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi source package in Focal:
  New

Bug description:
  I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu-
  core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see
  uboot prompt on screen, as well as kernel boot messages - as well as
  on serial. I see all of this coming over serial, but nothing on the
  screen until the system is completely booted.

  Current kernel version and snaps in this image are:
  $ uname -a
  Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

  $ snap list
  Name   VersionRev   Tracking Publisher   Notes
  core20 20 635   latest/beta  canonical✓  base
  pi 20-1   5820/beta  canonical✓  gadget
  pi-kernel  5.4.0-1011.11  154   20/beta  canonical✓  kernel
  snapd  2.45   7780  latest/beta  canonical✓  snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1878271/+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 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel

[John Scott]

Used the patch link and instructions above for 5.6.13. Worked like a
charm. Thanks satmandu.

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

Title:
  bcmwl kernel module does not build with 5.6.0 kernel

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Focal:
  Triaged

Bug description:
  After kernel update to 5.6.0-1007-oem wifi stopped working.
  Turned out dkms is unable to build the bcmwl module.

  The make log shows:

  ubuntu@ubuntu-inspiron-5482:~$ cat 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
  ons 15 apr 2020 09:19:05 CEST
  make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
AR  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_reg_map’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: 
error: implicit declaration of function ‘ioremap_nocache’; did you mean 
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 |  return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
|  ^~~
|  ioremap_cache
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: 
warning: returning ‘int’ from a function with return type ‘void *’ makes 
pointer from integer without a cast [-Wint-conversion]
949 |  return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
  In file included from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_set_auth_type’:
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
 warning: this statement may fall through [-Wimplicit-fallthrough=]
 52 |  if (wl_dbg_level & WL_DBG_DBG) {   \
| ^
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
 note: in expansion of macro ‘WL_DBG’
816 |   WL_DBG(("network eap\n"));
|   ^~
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
 note: here
817 |  default:
|  ^~~
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_attach’:
  /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]
593 |  if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) 
== NULL) {
|^~~
|ioremap_cache
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: 
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a 
cast [-Wint-conversion]
593 |  if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) 
== NULL) {
|  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_pci_probe’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: 
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 |  if ((val & 0xff00) != 0)
|  ^~
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: 
note: ...this statement, but the latter is misleadingly indented as if it were 
guarded by the ‘if’
782 |   bar1_size = pci_resource_len(pdev, 2);
|   ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: 
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 |   bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
|   ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_reg_proc_entry’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: 
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
   3376 |  if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops, 
wl)) == NULL) {
|  ^~~~
|

[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

[Kleber Sacilotto de Souza]

Testcase completed successfully with bionic/linux-hwe-5.0
5.0.0-48.52~18.04.1 - generic .

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

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

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-signed-oracle-5.0 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-aws source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-signed-oracle-5.0 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-aws source package in Disco:
  New
Status in linux-gcp source package in Disco:
  New
Status in linux-signed-oracle-5.0 source package in Disco:
  New
Status in linux source package in Eoan:
  Fix Committed
Status in linux-aws source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux-signed-oracle-5.0 source package in Eoan:
  New

Bug description:
  [Impact]
  Running seccomp kernel selftests will fail.

  [Test case]
  Run linux/tools/testing/selftests/seccomp/seccomp_bpf.

  On failure:

  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  On success:

  [ RUN  ] global.user_notification_basic
  [   OK ] global.user_notification_basic

  
  [Regression potential]
  The test is checking that the given structure which the kernel will write to 
is all zeroes. It's doing it because it wants userspace to have the possibility 
in the future to give data there indicating support for an extension that might 
be developed in the future. As the test is there right now, not applying the 
breaking uABI fix might cause us to miss applications that would break in 
future kernels. As the backport for that is prone for more regression 
potential, we are deciding to revert the new test.

  ==

  Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64)

  [ RUN  ] global.user_notification_basic
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic

  This cannot be reproduced with the kselftest in older kernel, probably
  a test case issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16
  ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21
  Uname: Linux 5.0.0-1011-oracle x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Mon Feb 10 05:17:54 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle-5.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+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 1836708] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]

[Christian Ehrhardt ]

We assigned Andy back in last summer as he was working/talking about it.
But I have the assumption here it might be the case that everyone else thinks 
"sure, this is on Andy I'll do nothing" and therefore overall nothing happens 
on this.

Also I have checked the org-chart again and since this is new kernel
-dev for Groovy (It was Eoan and Focal, but I've given up on the past -
let us focus only on the way forward) I think we'd better subscribe
sforshe and fginther to this.

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu Eoan)

** Changed in: linux (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

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

Title:
  Please package libbpf (which is done out of the kernel src) in Debian
  [for 19.10]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  Debian packages libbpf and so far does so out of the kernel source [1].
  There is some movement to separate that from the kernel source [2] but this 
isn't ready yet. So far it is just a sync of the subtree out of the kernel 
sources.

  Since we do not share our kernel packaging we will not get this for-free 
without doing anything.
  If there will be an ITP about it in Debian I'll let you know and we can abort 
this, but unless that really happens I wanted to ask if you could as well build 
the libbpf* packages for 19.10 and onward?

  Note: this is not the same bpf lib as [3] despite the similarity in
  names.

  Reasoning:
  BPF becomes more and more important in general and is used in the kernel for 
many things. In the case that brought it to my attention it will be a PMD of 
DPDK that will need it to control XDP [4]. And XDP in general is an interesting 
and rising feature for network acceleration - I'd think it would be helpful to 
have this package around in Ubuntu.

  
  ---

  
  FYI here the package info from buster as of today
  root@d10-buster:~# apt-cache show libbpf-dev libbpf4.19
  Package: libbpf-dev
  Source: linux
  Version: 4.19.28-2
  Installed-Size: 350
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Depends: libbpf4.19 (= 4.19.28-2)
  Description-en: eBPF helper library (development files)
   libbpf is a library for loading eBPF programs and reading and manipulating
   eBPF objects from user-space.
  Description-md5: b8834dcec31d23cd9577fbae4ac6a867
  Multi-Arch: same
  Homepage: https://www.kernel.org/
  Tag: devel::library, role::devel-lib
  Section: libdevel
  Priority: optional
  Filename: pool/main/l/linux/libbpf-dev_4.19.28-2_amd64.deb
  Size: 262268
  MD5sum: 2ab356bbbc421ac44f4106b6cf234f17
  SHA256: f567734a69bc472f2f5a546ace4ad3abf42d69f09d2613bca52a411d78179718

  Package: libbpf4.19
  Source: linux
  Version: 4.19.28-2
  Installed-Size: 318
  Maintainer: Debian Kernel Team 
  Architecture: amd64
  Depends: libc6 (>= 2.26), libelf1 (>= 0.131)
  Description-en: eBPF helper library (shared library)
   libbpf is a library for loading eBPF programs and reading and manipulating
   eBPF objects from user-space.
  Description-md5: 320aac663a5bd3caf223c7aa27857113
  Multi-Arch: same
  Homepage: https://www.kernel.org/
  Tag: role::shared-lib
  Section: libs
  Priority: optional
  Filename: pool/main/l/linux/libbpf4.19_4.19.28-2_amd64.deb
  Size: 259924
  MD5sum: bbb27965530e4101d43b7226fd563840
  SHA256: 18fdf5da4a90c8f42dedb8db510324d09d28f11eb2fa1b364508b14a95d5179b

  
  ---

  
  [1]: https://packages.debian.org/sid/libbpf-dev
  [2]: https://github.com/libbpf/libbpf
  [3]: https://github.com/iovisor/bcc
  [4]: https://www.iovisor.org/technology/xdp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836708/+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 1879284] [NEW] Cannot access shell in subiquity installer during automatic installation

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.

Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

Cloud-config:
#cloud-config
autoinstall:
  version: 1
  reporting:
remote:
  type: webhook
  endpoint: http://t35lp37.lnxne.boe:8080/log/
  refresh-installer:
update: yes
  apt:
primary:
- arches: [s390x]
  uri: http://us.ports.ubuntu.com/ubuntu-ports
  identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
  keyboard: {layout: us, variant: ''}
  locale: en_US
  ssh:
allow-pw: true
authorized-keys: []
install-server: true
  storage:
version: 1
layout:
  name: direct

The message I get when I log on to shell with installer and its
generated password is:

the installer running on /dev/tty1 will perform the autoinstall

This gives no indication on how can I switch to tty1 or where is it even
located.

One more issue is that if I run VM terminal with 'term conmode 3270'
first, VM console is assigned the tty1, but it displays the same
message:

Ubuntu 20.04 LTS ubuntu-server 3270/tty1 
 
 
the installer running on /dev/tty1 will perform the autoinstall  
 

I still get the logs through webhook, but they are not that detailed.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-185916 severity-high 
targetmilestone-inin---
-- 
Cannot access shell in subiquity installer during automatic installation
https://bugs.launchpad.net/bugs/1879284
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1879153] Re: amdgpu prevents poweroff

[Sebastien Bacher]

The log suggests it hits kernel errors

** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => linux (Ubuntu)

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

Title:
  amdgpu prevents poweroff

Status in linux package in Ubuntu:
  New

Bug description:
  Turning off Kubuntu 20.04 stops short of actually powering off the
  machine.

  The monitors goes into suspend mode, but PC is still powered on and I
  have to hold the power button in to turn it off.

  I initially suspected an ACPI problem, but I found these two errors in
  /var/log/syslog after turning the computer on again:

  May 16 02:46:53 desktop kernel: [475329.688676] [ cut here 
]
  May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 
dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm 
xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc 
rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio 
snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm
  May 16 02:46:53 desktop kernel: [475329.688783]  mac80211 intel_cstate 
libarc4 snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt 
btusb snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev 
input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac 
cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd 
gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea 
sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core 
libahci wmi video pinctrl_cannonlake pinctrl_intel
  May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg 
Tainted: GW 5.4.0-29-generic #33-Ubuntu
  May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte 
Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 
03/14/2019
  May 16 02:46:53 desktop kernel: [475329.688879] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 
48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 
a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 
85 56 01 00
  May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 
EFLAGS: 00010202
  May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 
978c9de001b8 RCX: 
  May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 
978c9de001b8 RDI: 9791c8d5
  May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: 
bd3c81567554 R09: 
  May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: 
 R12: 0001
  May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 
9791c8d5 R15: 978c9de001b8
  May 16 02:46:53 desktop kernel: [475329.66] FS:  7fe19eb9ca80() 
GS:9791ddb0() knlGS:
  May 16 02:46:53 desktop kernel: [475329.67] CS:  0010 DS:  ES:  
CR0: 80050033
  May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 
00088a80c006 CR4: 003606e0
  May 16 02:46:53 desktop kernel: [475329.68] Call Trace:
  May 16 02:46:53 desktop kernel: [475329.688959]  
dcn20_pipe_control_lock.part.0+0x112/0x1f0 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689026]  
dcn20_pipe_control_lock+0x1c/0x20 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689087]  
dc_stream_set_cursor_position+0x128/0x160 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689152]  
handle_cursor_update.isra.0+0x226/0x300 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689217]  

[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
- 2. Add second disk to it
- 3. Run pvcreate /dev/vdb
- 4. Run vgextend ubuntu-vg /dev/vdb
- 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 2. Remove demsetup
+ 3. Add second disk to it
+ 4. Run pvcreate /dev/vdb
+ 5. Run vgextend ubuntu-vg /dev/vdb
+ 6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
- 2. Remove demsetup
- 3. Add second disk to it
- 4. Run pvcreate /dev/vdb
- 5. Run vgextend ubuntu-vg /dev/vdb
- 6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 2. Add second disk to it
+ 3. Run pvcreate /dev/vdb
+ 4. Run vgextend ubuntu-vg /dev/vdb
+ 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 
+ Reboot and check that it still boots.
+ 
+ 6. Remove demsetup
+ 
+ Reboot and check that it fails to boot
+ 
+ 7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
- 6. Remove demsetup
+ 6. Remove mdadm
  
  Reboot and check that it fails to boot
  
  7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
  6. Remove mdadm
- 
- Reboot and check that it fails to boot
- 
  7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
+ 
+ 8. Downgrade lvm2 to release
+ 
+ Reboot and check that it fails to boot
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1879286] [NEW] Netplan configuration fails to apply in subiquity installer

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.

Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

#cloud-config
autoinstall:
  version: 1
  reporting:
remote:
  type: webhook
  endpoint: http://t35lp37.lnxne.boe:8080/log/
  refresh-installer:
update: yes
  apt:
primary:
- arches: [s390x]
  uri: http://us.ports.ubuntu.com/ubuntu-ports
  identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
  keyboard: {layout: us, variant: ''}
  locale: en_US
  network:
ethernets:
  encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
nameservers:
  addresses: [172.18.0.1]
version: 2
  ssh:
allow-pw: true
authorized-keys: []
install-server: true
  storage:
version: 1
layout:
  name: direct


I get the following otuput on the webhook:
curtin start subiquity/Welcome/apply_autoinstall_config:
curtin finish subiquity/Welcome/apply_autoinstall_config:
curtin finish subiquity/Welcome: completed
curtin start subiquity/Refresh/apply_autoinstall_config:
curtin start subiquity/Refresh/check_for_update:
curtin finish subiquity/Network/apply_config: Command '['netplan', 'apply']' 
returned non-zero exit status 1.
curtin start subiquity/Error/1589791025.945954323.network_fail/add_info:
curtin start subiquity/Error/1589791025.951922417.ui/add_info:
curtin finish subiquity/Error/1589791025.951922417.ui/add_info: written to 
/var/crash/1589791025.951922417.ui.crash

Configuration seems to be working fine when applied on a manually
installed system.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-185917 severity-high 
targetmilestone-inin2004
-- 
Netplan configuration fails to apply in subiquity installer
https://bugs.launchpad.net/bugs/1879286
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

sorry, working on verifying it, got distracted by other stuff.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to VM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1878970] [NEW] 3 times the system crashed and I had to do a hard reboot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590.

I've just bought a monitor AOC 22B1H and I'm using as a second monitor
plugged in HDMI.

For 3 times the system crashed and I had to do a hard reboot for no
reason apparently.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 15:02:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics [1028:0957]
   Subsystem: Dell GP108M [GeForce MX250] [1028:0957]
InstallationDate: Installed on 2020-05-04 (11 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 5590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=1a490b05-de14-4d4f-8795-c0fe269ac8cb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 0XRXN9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/15/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5590
dmi.product.sku: 0957
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu
-- 
3 times the system crashed and I had to do a hard reboot
https://bugs.launchpad.net/bugs/1878970
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1879010] Re: Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink

[Daniel van Vugt]

1. Please tell us the model of speaker you are having trouble with.

2. Please confirm that you can select higher quality mode in Settings,
and that it works.

** Tags added: a2dp

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

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

Title:
  Bluetooth speaker defaults to lower quality (HSP/HFP) instead of
  higher quality (A2DP) sink

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This seems identical to this bug:
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was
  suggested to open a new bug as the other one was closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 16:13:24 2020
  InstallationDate: Installed on 2020-05-06 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:8D:5A:D8:BA:43  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1126282 acl:178 sco:0 events:156624 errors:0
TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879010/+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 1879075] [NEW] Bluetooth sound card not detected.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

not connecting to my Bluetooth headphones. same problem on my desktop
computor. all worked ok with 18.04 .sometimes it will connect but after
a few seconds it will disconnect, if i remove the device, and then add
it, i can get it to connect, but YouTube video stalls with no sound, if
i disconnect the headphones, the video plays.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chris  1501 F pulseaudio
 /dev/snd/controlC0:  chris  1501 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 17:06:19 2020
InstallationDate: Installed on 2020-05-04 (12 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Grumpy_PK
dmi.board.vendor: PK
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-43
dmi.product.sku: 
dmi.product.version: V1.06
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal
-- 
Bluetooth sound card not detected. 
https://bugs.launchpad.net/bugs/1879075
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg

[Guillermo]

I am running Nvidia 440, and i have the same problem. :(

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

Title:
  NVIDIA settings won't write to /etc/xorg

Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-settings source package in Disco:
  In Progress

Bug description:
  I tried running it with root (`sudo nvidia-settings`) and without.

  I also generated an xorg file with `nvidia-xconfig`, and do the same
  thing, but it still won't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-settings 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr  3 00:33:48 2019
  InstallationDate: Installed on 2019-04-02 (0 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1879276] [NEW] Esata port is dead after boot, impossible to hotplug external drive

[Raphael Raccuia]

Public bug reported:

Esata doesn't work after boot: when hotplug an external drive, nothing happens, 
no dmesg or syslog.
It works perfectly when booting on the external HDD itself, and it mounts after 
boot if plugging on grub prompt.
Works on 4.15.3

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


** Tags: esata

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373302/+files/version.log

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

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive

[Raphael Raccuia]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+attachment/5373303/+files/lspci-vnvn.log

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

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
- 1. Install server with subiquity to VM
+ 1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

[Ubuntu Kernel Bot]

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

apport-collect 1879276

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

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

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

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

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

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1879153] [NEW] amdgpu prevents poweroff

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Turning off Kubuntu 20.04 stops short of actually powering off the
machine.

The monitors goes into suspend mode, but PC is still powered on and I
have to hold the power button in to turn it off.

I initially suspected an ACPI problem, but I found these two errors in
/var/log/syslog after turning the computer on again:

May 16 02:46:53 desktop kernel: [475329.688676] [ cut here 
]
May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 
dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm 
xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc 
rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio 
snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm
May 16 02:46:53 desktop kernel: [475329.688783]  mac80211 intel_cstate libarc4 
snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt btusb 
snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev 
input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac 
cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd 
gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea 
sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core 
libahci wmi video pinctrl_cannonlake pinctrl_intel
May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg 
Tainted: GW 5.4.0-29-generic #33-Ubuntu
May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte 
Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 
03/14/2019
May 16 02:46:53 desktop kernel: [475329.688879] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 
48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 
a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 
85 56 01 00
May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 
EFLAGS: 00010202
May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 
978c9de001b8 RCX: 
May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 
978c9de001b8 RDI: 9791c8d5
May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: 
bd3c81567554 R09: 
May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: 
 R12: 0001
May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 
9791c8d5 R15: 978c9de001b8
May 16 02:46:53 desktop kernel: [475329.66] FS:  7fe19eb9ca80() 
GS:9791ddb0() knlGS:
May 16 02:46:53 desktop kernel: [475329.67] CS:  0010 DS:  ES:  
CR0: 80050033
May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 
00088a80c006 CR4: 003606e0
May 16 02:46:53 desktop kernel: [475329.68] Call Trace:
May 16 02:46:53 desktop kernel: [475329.688959]  
dcn20_pipe_control_lock.part.0+0x112/0x1f0 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689026]  
dcn20_pipe_control_lock+0x1c/0x20 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689087]  
dc_stream_set_cursor_position+0x128/0x160 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689152]  
handle_cursor_update.isra.0+0x226/0x300 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689217]  
amdgpu_dm_commit_cursors.isra.0+0x60/0x80 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689281]  
amdgpu_dm_commit_planes.constprop.0+0x66d/0xa00 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689283]  ? __kmalloc_node+0x259/0x320
May 16 02:46:53 desktop kernel: [475329.689347]  ? 
dc_resource_state_copy_construct+0x11a/0x150 [amdgpu]
May 16 02:46:53 desktop kernel: [475329.689414]  

[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan

[Kai-Chuan Hsieh]

@hui.wang

Hello,

do you know when the package be SRUed?

Thanks,

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

Title:
  linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  some ubuntu eoan/bionic users reported that the audio driver failed
  to initialize, then the audio didn't work. I checked the dmesg, found
  the sof driver planed to load sof-cfl.ri, but there is no this
  firmware under eoan or bionic.

  [Fix]
  I consulted with Intel audio team, they told me that the coffeelake
  platform could share the firmware with cnl/whl platoforms, so we could
  build a symbol link sof-cfl->sof-cnl.

  [Test Case]
  A couple of ubuntu users already tested it on Dell and Asus coffeelake
  laptops, it worked well.

  
  [Regression Risk]
  Low, users already tested it, and Intel audio team confirmed it is safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1875263/+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 1878432] Re: rpi3a+ does not boot with core20

[Michael Vogt]

** Changed in: snapd
   Status: Incomplete => Won't Fix

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

Title:
  rpi3a+ does not boot with core20

Status in pi2-kernel-snap:
  New
Status in snapd:
  Won't Fix
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Focal:
  Invalid

Bug description:
  MMC:   mmc@7e202000: 0, mmcnr@7e30: 1
  Loading Environment from FAT... *** Warning - bad CRC, using default 
environment
  RPI3a+ on core 20 from 
http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the 
previous - 20200512.3) are not booting. This is for both arm64 and armhf. This 
is the serial log for as far as it gets:

  In:serial
  Out:   serial
  Err:   serial
  Net:   No ethernet found.
  starting USB...
  Bus usb@7e98: scanning bus usb@7e98 for devices... 5 USB Device(s) 
found
 scanning usb for storage devices... 1 Storage Device(s) found
  ## Warning: Input data exceeds 1048576 bytes - truncated
  ## Info: input data size = 1048578 = 0x12
  Hit any key to stop autoboot:  0 
  switch to partitions #0, OK
  mmc0 is current device
  Scanning mmc 0:1...
  Found U-Boot script /boot.scr
  4638 bytes read in 2 ms (2.2 MiB/s)
  ## Executing script at 0240
  4096 bytes read in 3 ms (1.3 MiB/s)
  8378005 bytes read in 363 ms (22 MiB/s)
  Total of 1 halfword(s) were the same
  Decompressing kernel...
  Uncompressed size: 25905664 = 0x18B4A00
  33637043 bytes read in 1448 ms (22.2 MiB/s)
  Booting Ubuntu (with booti) from mmc 0:...
  ## Flattened Device Tree blob at 0260
 Booting using the fdt blob at 0x260
 Using Device Tree in place at 0260, end 0260a065

  Starting kernel ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+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 1874286] Re: Add debian/rules targets to compile/run kernel selftests

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  Add debian/rules targets to compile/run kernel selftests

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

Bug description:
  [Impact]
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in
  order to be able to detect such breaks.

  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:

  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests

  [Regression Potential]
  None. This only adds new rules targets that will not break any existing 
targets.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874286/+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 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

[Sebastien Bacher]

the screenshots listing the card not working could be bug #1859308 which
seems a GUI issue

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  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=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df1xxx
  dmi.product.sku: 7UT64UA#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1878970] Re: 3 times the system crashed and I had to do a hard reboot

[Sebastien Bacher]

** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)

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

Title:
  3 times the system crashed and I had to do a hard reboot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590.

  I've just bought a monitor AOC 22B1H and I'm using as a second monitor
  plugged in HDMI.

  For 3 times the system crashed and I had to do a hard reboot for no
  reason apparently.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 15:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:0957]
 Subsystem: Dell GP108M [GeForce MX250] [1028:0957]
  InstallationDate: Installed on 2020-05-04 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 5590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=1a490b05-de14-4d4f-8795-c0fe269ac8cb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/15/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/1878970/+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 1879075] Re: Bluetooth sound card not detected.

[Sebastien Bacher]

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Bluetooth sound card not detected.

Status in linux package in Ubuntu:
  New

Bug description:
  not connecting to my Bluetooth headphones. same problem on my desktop
  computor. all worked ok with 18.04 .sometimes it will connect but
  after a few seconds it will disconnect, if i remove the device, and
  then add it, i can get it to connect, but YouTube video stalls with no
  sound, if i disconnect the headphones, the video plays.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1501 F pulseaudio
   /dev/snd/controlC0:  chris  1501 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 17:06:19 2020
  InstallationDate: Installed on 2020-05-04 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879075/+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 1879284] [NEW] Cannot access shell in subiquity installer during automatic installation

[bugproxy]

Public bug reported:

I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.

Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

Cloud-config:
#cloud-config
autoinstall:
  version: 1
  reporting:
remote:
  type: webhook
  endpoint: http://t35lp37.lnxne.boe:8080/log/
  refresh-installer:
update: yes
  apt:
primary:
- arches: [s390x]
  uri: http://us.ports.ubuntu.com/ubuntu-ports
  identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
  keyboard: {layout: us, variant: ''}
  locale: en_US
  ssh:
allow-pw: true
authorized-keys: []
install-server: true
  storage:
version: 1
layout:
  name: direct

The message I get when I log on to shell with installer and its
generated password is:

the installer running on /dev/tty1 will perform the autoinstall

This gives no indication on how can I switch to tty1 or where is it even
located.

One more issue is that if I run VM terminal with 'term conmode 3270'
first, VM console is assigned the tty1, but it displays the same
message:

Ubuntu 20.04 LTS ubuntu-server 3270/tty1 
 
 
the installer running on /dev/tty1 will perform the autoinstall  
 

I still get the logs through webhook, but they are not that detailed.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-185916 severity-high 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-185916 severity-high
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  Cannot access shell in subiquity installer during automatic
  installation

Status in linux package in Ubuntu:
  New

Bug description:
  I'm installing Ubuntu 20.04 with a nocloud-net installation source on
  a z/VM guest. I'm currently limited to seeing installation output only
  through webhook reporter, because I cannot access shell on the target
  system during installation.

  Kernel command-line:
  cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

  Cloud-config:
  #cloud-config
  autoinstall:
version: 1
reporting:
  remote:
type: webhook
endpoint: http://t35lp37.lnxne.boe:8080/log/
refresh-installer:
  update: yes
apt:
  primary:
  - arches: [s390x]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
  realname: user, username: user}
keyboard: {layout: us, variant: ''}
locale: en_US
ssh:
  allow-pw: true
  authorized-keys: []
  install-server: true
storage:
  version: 1
  layout:
name: direct

  The message I get when I log on to shell with installer and its
  generated password is:

  the installer running on /dev/tty1 will perform the autoinstall

  This gives no indication on how can I switch to tty1 or where is it
  even located.

  One more issue is that if I run VM terminal with 'term conmode 3270'
  first, VM console is assigned the tty1, but it displays the same
  message:

  Ubuntu 20.04 LTS ubuntu-server 3270/tty1 
   
   
  the installer running on /dev/tty1 will perform the autoinstall  
   

  I still get the logs through webhook, but they are not that detailed.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1874055] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From niklas.schne...@ibm.com 2020-05-18 05:20 EDT---
My patch for this issue is now available publicly on the fixes branch of the 
public s390 repository on kernel.org.

https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=fixes=f058599e22d59e594e5aae1dc10560568d8f4a8b

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

Title:
  [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO
  instructions are available

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  One of the PCI enhancements on Z15 are the enhanced PCI load/store
  instructions which can be executed directly from user space code. When
  these instructions are available and preexisting user space code still
  uses the old s390_pci_mmio_write/read system calls, the system calls
  fail with an "Unable to handle kernel pointer dereference in virtual
  kernel address space" in the kernel.  This issue affects distributions
  which have the enablement for Z15 PCI enhancements and where customers
  run workloads which accesses PCI adapters from user space, e.g. RDMA
  applications.  To solve this, the system call implementation needs to
  be enhanced to provide to execute enhanced PCI load/store instructions
  on behalf of the user space application making use of the mappings
  into its virtual address space

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874055/+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 1879153] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1879153

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

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

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

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

** Tags added: 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/1879153

Title:
  amdgpu prevents poweroff

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Turning off Kubuntu 20.04 stops short of actually powering off the
  machine.

  The monitors goes into suspend mode, but PC is still powered on and I
  have to hold the power button in to turn it off.

  I initially suspected an ACPI problem, but I found these two errors in
  /var/log/syslog after turning the computer on again:

  May 16 02:46:53 desktop kernel: [475329.688676] [ cut here 
]
  May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 
dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm 
xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc 
rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio 
snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm
  May 16 02:46:53 desktop kernel: [475329.688783]  mac80211 intel_cstate 
libarc4 snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt 
btusb snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev 
input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac 
cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd 
gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea 
sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core 
libahci wmi video pinctrl_cannonlake pinctrl_intel
  May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg 
Tainted: GW 5.4.0-29-generic #33-Ubuntu
  May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte 
Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 
03/14/2019
  May 16 02:46:53 desktop kernel: [475329.688879] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 
48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 
a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 
85 56 01 00
  May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 
EFLAGS: 00010202
  May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 
978c9de001b8 RCX: 
  May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 
978c9de001b8 RDI: 9791c8d5
  May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: 
bd3c81567554 R09: 
  May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: 
 R12: 0001
  May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 
9791c8d5 R15: 978c9de001b8
  May 16 02:46:53 desktop kernel: [475329.66] FS:  7fe19eb9ca80() 
GS:9791ddb0() knlGS:
  May 16 02:46:53 desktop kernel: [475329.67] CS:  0010 DS:  ES:  
CR0: 80050033
  May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 
00088a80c006 CR4: 003606e0
  May 

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

[Ubuntu Kernel Bot]

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

apport-collect 1879075

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

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

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

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

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

Title:
  Bluetooth sound card not detected.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  not connecting to my Bluetooth headphones. same problem on my desktop
  computor. all worked ok with 18.04 .sometimes it will connect but
  after a few seconds it will disconnect, if i remove the device, and
  then add it, i can get it to connect, but YouTube video stalls with no
  sound, if i disconnect the headphones, the video plays.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1501 F pulseaudio
   /dev/snd/controlC0:  chris  1501 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 17:06:19 2020
  InstallationDate: Installed on 2020-05-04 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879075/+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 1879290] [NEW] pc: no message on the screen for ~30s on fast HW

[Michael Vogt]

Public bug reported:

The boot on real HW (ARock B450, Ryzen, NVME 240Gb) takes a long time
without any visible feedback.

Video: https://photos.app.goo.gl/RmaLviXNorjeh5BP7
With grub debug: https://photos.app.goo.gl/PJuXdxp8uedr7fWp9
(google photos has degraded quality quite a bit, may upload the originals if 
too bad)

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


** Tags: uc20

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

Title:
  pc: no message on the screen for ~30s on fast HW

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  The boot on real HW (ARock B450, Ryzen, NVME 240Gb) takes a long time
  without any visible feedback.

  Video: https://photos.app.goo.gl/RmaLviXNorjeh5BP7
  With grub debug: https://photos.app.goo.gl/PJuXdxp8uedr7fWp9
  (google photos has degraded quality quite a bit, may upload the originals if 
too bad)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1879290/+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 1878007] [NEW] Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron
7373. When the screen is turned off (so, the suspend or screen lock
features are affected), the system freeze and I need to force the laptop
turn off and on again. There are some cases when it turn off the screen
without issues, but most of the time it freezes. Even "SysRq REISUB"
does not work for rebooting when system crash. I can reproduce the issue
using `xset dpms force off`.

Initially this bug report was filled thinking it was a suspend issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144

Syslog or systemd journal does not provide any error information about
the crash.

"lsb_release -rd" output:
Description: Ubuntu 20.04 LTS
Release: 20.04

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


** Tags: bot-comment
-- 
 Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off
https://bugs.launchpad.net/bugs/1878007
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1827752] Re: Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when using Ubuntu 19.04

[JORGETECH]

Changed the issue to "Fix Released" since it was most likely a hardware
fault. The laptop needed an RMA since it was shutting off at random,
after returning from RMA the hibernation issue also disappeared.

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

Title:
  Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when
  using Ubuntu 19.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu 19.04 this laptop no longer suspends to RAM
  correctly (and it would resume by itself in previous versions of
  Ubuntu). It does not matter if the lid is closed or trying to suspend
  from GUI/CLI, the laptop tries to suspend but immediately resumes back
  to the lock screen.

  Below I attached the information necessary to debug such problem
  followed from the wiki, this logs were made using the Linux mainline
  non-daily kernel 5.0.12 from the Ubuntu kernel repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827752/+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 1827752] Re: Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when using Ubuntu 19.04

[JORGETECH]

Most likely a hardware fault (or the issue was solved recently in the
kernel)

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

Title:
  Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when
  using Ubuntu 19.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu 19.04 this laptop no longer suspends to RAM
  correctly (and it would resume by itself in previous versions of
  Ubuntu). It does not matter if the lid is closed or trying to suspend
  from GUI/CLI, the laptop tries to suspend but immediately resumes back
  to the lock screen.

  Below I attached the information necessary to debug such problem
  followed from the wiki, this logs were made using the Linux mainline
  non-daily kernel 5.0.12 from the Ubuntu kernel repository.

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

[Raphael Raccuia]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1879276/+attachment/5373345/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1873352] Re: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2

[Kai-Heng Feng]

4.15.0-42 is a bit old. Maybe try the latest one like 4.15.0-99?

** Changed in: linux (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/1873352

Title:
  unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage
  count = 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  We recently encountered an issue when trying to stop nova instances.

  | Apr 16 09:35:10 ginzel kernel: [6925958.071665]
  unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage
  count = 2

  When I try to stop manually the qemu process, it errors
  """
  ballot@ginzel:~$ sudo virsh destroy instance-000718af 

  setlocale: No such file or directory  
   
  error: Failed to destroy domain instance-000718af 
   
  error: Failed to terminate process 20953 with SIGKILL: Device or resource busy
  """

  The qemu process is in D state because of this
  """
  libvirt+ 20953 12.9  0.5 9001400 2925908 ? DApr15  84:25 
/usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine 
pc-i440fx-trusty,accel=kvm,usb=off -cpu 
EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t
  opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime 
mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack 
Foundati
  on,product=OpenStack 
Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4
 -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/q
  emu/instance-000718af.monitor,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global 
kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device 
pii
  x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
 -device virtio-blk-pci,scsi=off,bus=pci.0
  ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev 
tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 
-chardev f
  
ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log
 -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 
-device isa-serial,chardev=charserial1,i
  d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device 
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
  ballot@ginzel:~$ sudo cat /proc/20953/sta 
   
  stack   statstatm   status
  """

  and we can see the stack of the process
  """
  ballot@ginzel:~$ sudo cat /proc/20953/stack 
  [<0>] msleep+0x2d/0x40  
  [<0>] netdev_run_todo+0x11c/0x320 
   
  [<0>] rtnl_unlock+0xe/0x10
  [<0>] tun_chr_close+0x28/0x30   
  [<0>] __fput+0xea/0x220   
   
  [<0>] fput+0xe/0x10   
   
  [<0>] task_work_run+0x9d/0xc0 
   
  [<0>] exit_to_usermode_loop+0xc0/0xd0 
   
  [<0>] do_syscall_64+0x115/0x130 
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
   
  [<0>] 0x
  """

  Will attach the relevant files
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 27 05:43 seq
   crw-rw 1 root audio 116, 33 Jan 27 05:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HPE ProLiant DL385 Gen10
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 
console=ttyS0,115200
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   

[Kernel-packages] [Bug 1879276] ProcModules.txt

[Raphael Raccuia]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373343/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1872634] Re: Webcam Z-Star 305b doesn't work in Ubuntu (again)

[Kai-Heng Feng]

It's hard to say it's a kernel bug. Can you please try some live distro
like Ubuntu 20.04?

** Changed in: linux (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/1872634

Title:
  Webcam Z-Star 305b doesn't work in Ubuntu (again)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My webcam Z-Star 305b was supposed to work out of the box [1], but it
  doesn't work in bionic. It only shows a black screen.

  I've read lots of threads and tried some suggestions, but
  unsuccessfully.

  At present, I'm using bionic x86_64 with kernel 5.3.0-46-generic,
  before that I tried it with 4.15.0-96 and some previous versions.

  lsmod |grep gspca output is:

  gspca_zc3xx57344  0
  gspca_main 24576  2 gspca_zc3xx
  videobuf2_vmalloc  20480  1 gspca_main
  videobuf2_v4l2 24576  1 gspca_main
  videobuf2_common   49152  2 gspca_main,videobuf2_v4l2
  videodev  208896  5 
gspca_main,gspca_zc3xx,videobuf2_v4l2,videobuf2_common

  lsusb output is:

  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 0ac8:305b Z-Star Microelectronics Corp. ZC0305 Webcam
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I tried several ubuntu-version to figure out if the error was
  introduced recently into the kernel but couldn't find any working
  version

  I've tried cheese, vlc and guvcview.

  I've tried LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so
  cheese which made change cheese change it's error message and vlc to
  not work at all.

  I would appreciate any help, because I'm completely lost. :-(

  Thanks in advance!

  ---
  1) 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/media/v4l-drivers/gspca-cardlist.rst
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ber3172 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=UUID=b7611db7-52e5-47c1-93e1-069bb4336a8f
  InstallationDate: Installed on 2018-04-20 (724 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: LENOVO 2429NL6
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/mint-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA2WW (2.62 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2429NL6
  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.modalias: 
dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2429NL6:pvrThinkPadT530:rvnLENOVO:rn2429NL6:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 2429NL6
  dmi.product.sku: LENOVO_MT_2429
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872634/+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 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1874502] Re: Bionic update: upstream stable patchset 2020-04-23

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1874286] Re: Add debian/rules targets to compile/run kernel selftests

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1871688] Re: LIO hanging in iscsit_free_session and iscsit_stop_session

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1872415] Re: [Lenovo ideapad FLEX 6-14IKB] Laptop/Tablet lose trackpad on flipping to tablet mode.

[Kai-Heng Feng]

Is it really controlled by kernel?

** Changed in: linux (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/1872415

Title:
  [Lenovo ideapad FLEX 6-14IKB] Laptop/Tablet lose trackpad on flipping
  to tablet mode.

Status in linux package in Ubuntu:
  Incomplete
Status in xfce4 package in Ubuntu:
  New

Bug description:
  I am on a Lenovo Flex 14 laptop that includes a 360-degree hinge for
  flipping the screen to tablet mode. Upon flipping the screen to tablet
  mode the trackpad seems to be disabled but after returning the screen
  to 90 degrees or laptop mode the trackpad is not re-enabled.

  The only way the trackpad seems to be able to be re-enabled is by
  restarting the system. Logging out and back does not fix the problem.

  The laptop keyboard and touchscreen still work after flipping to
  360-degrees and back to 90 degrees/laptop, but, again, the trackpad is
  not working after doing this operation of flipping the screen.

  Tested on Xubuntu 20.04 and Ubuntu 20.04, which are both in beta.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 13 03:19:05 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:398c]
 Subsystem: Lenovo GM108M [GeForce MX130] [17aa:398c]
  InstallationDate: Installed on 2020-04-07 (5 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200407)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:2426 Syntek Integrated Camera
   Bus 001 Device 003: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81EM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=f33b718b-a02d-47b1-9d8a-a0704da0f02d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 6-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr7QCN43WW:bd11/28/2019:svnLENOVO:pn81EM:pvrLenovoideapadFLEX6-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX6-14IKB:
  dmi.product.family: ideapad FLEX 6-14IKB
  dmi.product.name: 81EM
  dmi.product.sku: LENOVO_MT_81EM_BU_idea_FM_ideapad FLEX 6-14IKB
  dmi.product.version: Lenovo ideapad FLEX 6-14IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/1872415/+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 1877123] Re: 4.15.0-100.101 breaks userspace builds due to a bug in the headers /usr/include/linux/swab.h of linux-libc-dev

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1873043] Re: Bionic update: upstream stable patchset 2020-04-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1869644] Re: add_key05 from ubuntu_ltp_syscalls failed

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1874124] Re: Add hw timestamps to received skbs in peak_canfd

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1879286] [NEW] [UBUNTU 20.04] Netplan configuration fails to apply in subiquity installer

[bugproxy]

Public bug reported:

I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.

Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

#cloud-config
autoinstall:
  version: 1
  reporting:
remote:
  type: webhook
  endpoint: http://t35lp37.lnxne.boe:8080/log/
  refresh-installer:
update: yes
  apt:
primary:
- arches: [s390x]
  uri: http://us.ports.ubuntu.com/ubuntu-ports
  identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
  keyboard: {layout: us, variant: ''}
  locale: en_US
  network:
ethernets:
  encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
nameservers:
  addresses: [172.18.0.1]
version: 2
  ssh:
allow-pw: true
authorized-keys: []
install-server: true
  storage:
version: 1
layout:
  name: direct


I get the following otuput on the webhook:
curtin start subiquity/Welcome/apply_autoinstall_config:
curtin finish subiquity/Welcome/apply_autoinstall_config:
curtin finish subiquity/Welcome: completed
curtin start subiquity/Refresh/apply_autoinstall_config:
curtin start subiquity/Refresh/check_for_update:
curtin finish subiquity/Network/apply_config: Command '['netplan', 'apply']' 
returned non-zero exit status 1.
curtin start subiquity/Error/1589791025.945954323.network_fail/add_info:
curtin start subiquity/Error/1589791025.951922417.ui/add_info:
curtin finish subiquity/Error/1589791025.951922417.ui/add_info: written to 
/var/crash/1589791025.951922417.ui.crash

Configuration seems to be working fine when applied on a manually
installed system.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-185917 severity-high 
targetmilestone-inin2004

** Tags added: architecture-s39064 bugnameltc-185917 severity-high
targetmilestone-inin2004

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU 20.04] Netplan configuration fails to apply in subiquity
  installer

Status in linux package in Ubuntu:
  New

Bug description:
  I'm installing Ubuntu 20.04 with a nocloud-net installation source on
  a z/VM guest. I'm currently limited to seeing installation output only
  through webhook reporter, because I cannot access shell on the target
  system during installation.

  Kernel command-line:
  cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

  #cloud-config
  autoinstall:
version: 1
reporting:
  remote:
type: webhook
endpoint: http://t35lp37.lnxne.boe:8080/log/
refresh-installer:
  update: yes
apt:
  primary:
  - arches: [s390x]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
  realname: user, username: user}
keyboard: {layout: us, variant: ''}
locale: en_US
network:
  ethernets:
encbdf0:
  addresses: [172.18.76.38/15]
  gateway4: 172.18.0.1
  nameservers:
addresses: [172.18.0.1]
  version: 2
ssh:
  allow-pw: true
  authorized-keys: []
  install-server: true
storage:
  version: 1
  layout:
name: direct

  
  I get the following otuput on the webhook:
  curtin start subiquity/Welcome/apply_autoinstall_config:
  curtin finish subiquity/Welcome/apply_autoinstall_config:
  curtin finish subiquity/Welcome: completed
  curtin start subiquity/Refresh/apply_autoinstall_config:
  curtin start subiquity/Refresh/check_for_update:
  curtin finish subiquity/Network/apply_config: Command '['netplan', 'apply']' 
returned non-zero exit status 1.
  curtin start subiquity/Error/1589791025.945954323.network_fail/add_info:
  curtin start subiquity/Error/1589791025.951922417.ui/add_info:
  curtin finish subiquity/Error/1589791025.951922417.ui/add_info: written to 

[Kernel-packages] [Bug 1879286] Re: [UBUNTU 20.04] Netplan configuration fails to apply in subiquity installer

[Heinz-Werner Seeck]

** Summary changed:

- Netplan configuration fails to apply in subiquity installer
+ [UBUNTU 20.04] Netplan configuration fails to apply in subiquity installer

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

Title:
  [UBUNTU 20.04] Netplan configuration fails to apply in subiquity
  installer

Status in linux package in Ubuntu:
  New

Bug description:
  I'm installing Ubuntu 20.04 with a nocloud-net installation source on
  a z/VM guest. I'm currently limited to seeing installation output only
  through webhook reporter, because I cannot access shell on the target
  system during installation.

  Kernel command-line:
  cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

  #cloud-config
  autoinstall:
version: 1
reporting:
  remote:
type: webhook
endpoint: http://t35lp37.lnxne.boe:8080/log/
refresh-installer:
  update: yes
apt:
  primary:
  - arches: [s390x]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
  realname: user, username: user}
keyboard: {layout: us, variant: ''}
locale: en_US
network:
  ethernets:
encbdf0:
  addresses: [172.18.76.38/15]
  gateway4: 172.18.0.1
  nameservers:
addresses: [172.18.0.1]
  version: 2
ssh:
  allow-pw: true
  authorized-keys: []
  install-server: true
storage:
  version: 1
  layout:
name: direct

  
  I get the following otuput on the webhook:
  curtin start subiquity/Welcome/apply_autoinstall_config:
  curtin finish subiquity/Welcome/apply_autoinstall_config:
  curtin finish subiquity/Welcome: completed
  curtin start subiquity/Refresh/apply_autoinstall_config:
  curtin start subiquity/Refresh/check_for_update:
  curtin finish subiquity/Network/apply_config: Command '['netplan', 'apply']' 
returned non-zero exit status 1.
  curtin start subiquity/Error/1589791025.945954323.network_fail/add_info:
  curtin start subiquity/Error/1589791025.951922417.ui/add_info:
  curtin finish subiquity/Error/1589791025.951922417.ui/add_info: written to 
/var/crash/1589791025.951922417.ui.crash

  Configuration seems to be working fine when applied on a manually
  installed system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879286/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

verified in bionic

Did all the steps (install vm, create pv, extend pv, remove dmadm,
upgrade).

It booted after the upgrade to 2.02.176-4.1ubuntu3.18.04.3, and it
failed again following a downgrade to the 2.02.176-4.1ubuntu3.18.04.2
from updates pocket.

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

** Tags removed: id-5d0ba914f340e31a8e9f2cf1 removal-candidate
** Tags added: id-5d0ba914f340e31a8e9f2cf

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1867882] Re: After upgrade to the latest kernel, fan gets very loud and always on whenever on AC power

[Kai-Heng Feng]

"intel_pstate=disable" doesn't seem good. Please remove all unnecessary
kernel parameter first.

** Changed in: linux (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/1867882

Title:
  After upgrade to the latest kernel, fan gets very loud and always on
  whenever on AC power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to the latest kernel, fan gets very loud and always ON
  whenever on AC power. I tried to use battery power and my fan work
  just fine, sometimes ON on heavy tasks and then OFF again, but on AC
  power even on idle, the fan is ON and gets quite loud. Happened after
  I've updated to the latest kernel yesterday.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 14:13:41 2020
  InstallationDate: Installed on 2019-09-05 (194 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silviya   10639 F pulseaudio
   /dev/snd/pcmC0D0p:   silviya   10639 F...m pulseaudio
  CRDA:
   global
   country ID: DFS-JP
(2402 - 2482 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice:
   
  InstallationDate: Installed on 2019-09-05 (254 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b722 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 062a:5918 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550VXK
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=b8377b73-320f-4e42-b7ee-2dbede2d0d7e ro quiet splash video=SVIDEO-1:d 
libata.force=noncq pci=nomsi pci=noaer acpi_enforce_resources=lax 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550VXK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550VXK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550VXK.302:bd01/19/2017:svnASUSTeKCOMPUTERINC.:pnX550VXK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550VXK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550VXK
  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/1867882/+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 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/

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

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

Title:
   Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off

Status in linux package in Ubuntu:
  New

Bug description:
  This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron
  7373. When the screen is turned off (so, the suspend or screen lock
  features are affected), the system freeze and I need to force the
  laptop turn off and on again. There are some cases when it turn off
  the screen without issues, but most of the time it freezes. Even
  "SysRq REISUB" does not work for rebooting when system crash. I can
  reproduce the issue using `xset dpms force off`.

  Initially this bug report was filled thinking it was a suspend issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144

  Syslog or systemd journal does not provide any error information about
  the crash.

  "lsb_release -rd" output:
  Description: Ubuntu 20.04 LTS
  Release: 20.04

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

[Raphael Raccuia]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373339/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373335/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373344/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373340/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

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

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

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

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive

[Raphael Raccuia]

apport information

** Tags added: apport-collected tara

** Description changed:

  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.14
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  raphael1888 F pulseaudio
+  /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
+  /dev/snd/controlC0:  raphael1888 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
+ InstallationDate: Installed on 2018-03-17 (793 days ago)
+ InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
+ MachineType: TOSHIBA TECRA A50-A
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-51-generic N/A
+  linux-backports-modules-5.3.0-51-generic  N/A
+  linux-firmware1.173.18
+ Tags:  tara
+ Uname: Linux 5.3.0-51-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
+ _MarkForUpload: True
+ dmi.bios.date: 04/18/2018
+ dmi.bios.vendor: TOSHIBA
+ dmi.bios.version: Version 5.10
+ dmi.board.asset.tag: 00
+ dmi.board.name: TECRA A50-A
+ dmi.board.vendor: TOSHIBA
+ dmi.board.version: Version A0
+ dmi.chassis.asset.tag: 00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: TOSHIBA
+ dmi.chassis.version: Version 1.0
+ dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
+ dmi.product.family: 00
+ dmi.product.name: TECRA A50-A
+ dmi.product.sku: PT641E
+ dmi.product.version: PT641E-00600GS4
+ dmi.sys.vendor: TOSHIBA

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/537/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:

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

[Raphael Raccuia]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1879276/+attachment/5373334/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1879276/+attachment/5373346/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1879276/+attachment/5373338/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373336/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1879276/+attachment/5373337/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373341/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Raphael Raccuia]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1879276/+attachment/5373342/+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/1879276

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  New

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1879299] [NEW] enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x LPAR / zVM ( docker still configured, unable to disable fan)

[Po-Hsu Lin]

Public bug reported:

Issue found on E/F s390x LPAR / zVM (they are manually provisioned
systems)

Test failed with:
docker still configured, unable to disable fan

  * Command:
  ./ubuntu_fan_smoke_test.sh 10.245.0.0/16
  Exit status: 1
  Duration: 12.935628891

  stdout:
  Running in the Canonical CI environment
  Testing Fan Networking (pre-0.13.0 API)
  docker pull s390x/ubuntu: PASSED
  enable disable fan test: FAILED (fanctl returned 1)
  stderr:
  /usr/sbin/fanatic: docker still configured, unable to disable fan

docker container ls shows there is no docker running
$ sudo docker container ls -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
$


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CasperMD5CheckResult: skip
CurrentDmesg:

Date: Mon May 18 11:08:11 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:

Lspci-vt: -[:00]-
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
PciMultimedia:

ProcFB:

ProcKernelCmdLine: root=/dev/mapper/kl04vg01-kl04root crashkernel=196M 
BOOT_IMAGE=
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-03-03 (76 days ago)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug eoan focal package-from-proposed s390x ubuntu-fan-smoke-test

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: eoan ubuntu-fan-smoke-test

** Description changed:

  Issue found on E/F s390x LPAR / zVM (they are manually provisioned
  systems)
  
  Test failed with:
- docker still configured, unable to disable fan
+ docker still configured, unable to disable fan
  
+   * Command:
+   ./ubuntu_fan_smoke_test.sh 10.245.0.0/16
+   Exit status: 1
+   Duration: 12.935628891
  
-   * Command: 
-   ./ubuntu_fan_smoke_test.sh 10.245.0.0/16
-   Exit status: 1
-   Duration: 12.935628891
-   
-   stdout:
-   Running in the Canonical CI environment
-   Testing Fan Networking (pre-0.13.0 API)
-   docker pull s390x/ubuntu: PASSED
-   enable disable fan test: FAILED (fanctl returned 1)
-   stderr:
-   /usr/sbin/fanatic: docker still configured, unable to disable fan
+   stdout:
+   Running in the Canonical CI environment
+   Testing Fan Networking (pre-0.13.0 API)
+   docker pull s390x/ubuntu: PASSED
+   enable disable fan test: FAILED (fanctl returned 1)
+   stderr:
+   /usr/sbin/fanatic: docker still configured, unable to disable fan
+ 
+ docker container ls shows there is no docker running
+ $ sudo docker container ls -a
+ CONTAINER IDIMAGE   COMMAND CREATED   
  STATUS  PORTS   NAMES
+ $
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  CurrentDmesg:
-  
+ 
  Date: Mon May 18 11:08:11 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
-  
+ 
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  PciMultimedia:
-  
+ 
  ProcFB:
-  

[Kernel-packages] [Bug 1877657] Re: bionic snapdragon 4.15 snap failed Certification testing

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1875601] Re: built-using constraints preventing uploads

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1349028] Re: getitimer returns it_value=0 erroneously

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-101.102

---
linux (4.15.0-101.102) bionic; urgency=medium

  * bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)

  * 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
  swap

  * bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"

linux (4.15.0-100.101) bionic; urgency=medium

  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)

  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data

  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests

  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset

  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs

  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising

  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect

  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs

  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: 

[Kernel-packages] [Bug 1501972] Re: nvidia kernel module failed to build [/bin/sh: 1: cc: not found]

[Robert van der Spek]

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

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

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

Title:
  nvidia kernel module failed to build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  I really have no idea of this issue, i just booted up and ubuntu
  notified me that there was a problem... hopefully ubuntu is self
  reporting enough information.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-346 346.96-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-65-generic
  Date: Thu Oct  1 18:17:00 2015
  InstallationDate: Installed on 2015-09-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 346.96-0ubuntu0.0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-346
  Title: nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.346.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1501972/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

[Kai-Heng Feng]

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

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY 

[Kernel-packages] [Bug 1878670] Re: i915 crashes hsw_power_well_enable

[Kurt Aaholst]

Sounds resasonable.

Do you need any more info from me?

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

Title:
  i915 crashes hsw_power_well_enable

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

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1869940] Re: No networks available/visible after suspend

[Kai-Heng Feng]

Please reproduce the issue then attach dmesg.

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

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

Title:
  No networks available/visible after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  WiFI network disconnected and no networks visible after resume from
  suspend. Had to reboot the machine to get networking (WiFI) back up
  and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 21:18:43 2020
  InstallationDate: Installed on 2020-03-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  IpRoute:
   default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp59s0 scope link metric 1000 
   192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
   DORIAN  2c3f821d-0865-4747-974a-2f861ee0dc38  wifi  1585682245  tis 31 mar 
2020 21:17:25  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp59s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/DORIAN.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp59s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  DORIAN  
2c3f821d-0865-4747-974a-2f861ee0dc38  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp59s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1871962] Re: NETDEV WATCHDOG: enx106530060c6c (r8152): transmit queue 0 timed out

[Kai-Heng Feng]

[19120.043303] usb 4-2.2: Dell TB16 Dock, disable RX aggregation

Do you use TB16 dock? It doesn't seems so...

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

Title:
  NETDEV WATCHDOG: enx106530060c6c (r8152): transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [21388.637197] [ cut here ]
  [21388.637206] NETDEV WATCHDOG: enx106530060c6c (r8152): transmit queue 0 
timed out
  [21388.637255] WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:447 
dev_watchdog+0x258/0x260
  [21388.637257] Modules linked in: nls_utf8 isofs uas usb_storage thunderbolt 
rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm typec_displayport cmac 
algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 mei_hdcp 
intel_rapl_msr snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
dell_laptop ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec 
snd_hda_core snd_usb_audio snd_seq_midi snd_seq_midi_event snd_usbmidi_lib 
btusb snd_hwdep snd_rawmidi btrtl ath10k_pci snd_seq joydev btbcm ath10k_core 
cdc_ether btintel snd_seq_device usbnet uvcvideo snd_pcm bluetooth 
x86_pkg_temp_thermal ath intel_powerclamp r8152 mii videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 coretemp videobuf2_common snd_timer videodev 
dell_wmi mc kvm_intel kvm ecdh_generic ecc intel_cstate dell_smbios snd 
mac80211 intel_rapl_perf dcdbas input_leds serio_raw intel_wmi_thunderbolt 
dell_wmi_descriptor wmi_bmof cfg80211 rtsx_pci_ms soundcore libarc4 
hid_multitouch memstick mei_me intel_pch_thermal
  [21388.637355]  ucsi_acpi intel_xhci_usb_role_switch processor_thermal_device 
typec_ucsi roles intel_rapl_common mei intel_soc_dts_iosf typec intel_hid 
acpi_pad int3400_thermal acpi_thermal_rel int3403_thermal int340x_thermal_zone 
mac_hid sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 mmc_block dm_crypt hid_generic usbhid crct10dif_pclmul 
crc32_pclmul i915 ghash_clmulni_intel rtsx_pci_sdmmc aesni_intel crypto_simd 
cryptd glue_helper i2c_algo_bit psmouse drm_kms_helper syscopyarea sysfillrect 
sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm intel_lpss_pci intel_lpss 
rtsx_pci idma64 virt_dma i2c_hid wmi hid pinctrl_sunrisepoint pinctrl_intel 
video
  [21388.637433] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G   OE 
5.4.0-21-generic #25-Ubuntu
  [21388.637436] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [21388.637446] RIP: 0010:dev_watchdog+0x258/0x260
  [21388.637452] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 5e 26 e8 00 01 e8 ed bc 
fa ff 44 89 e9 4c 89 fe 48 c7 c7 10 63 a3 83 48 89 c2 e8 33 61 71 ff <0f> 0b eb 
80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7
  [21388.637456] RSP: 0018:b70f8020ce30 EFLAGS: 00010286
  [21388.637460] RAX:  RBX: 99f6cf37e200 RCX: 
0006
  [21388.637463] RDX: 0007 RSI: 0096 RDI: 
99f6de5578c0
  [21388.637466] RBP: b70f8020ce60 R08: 0746 R09: 
0004
  [21388.637468] R10:  R11: 0001 R12: 
0001
  [21388.637471] R13:  R14: 99f6d2d86480 R15: 
99f6d2d86000
  [21388.637475] FS:  () GS:99f6de54() 
knlGS:
  [21388.637479] CS:  0010 DS:  ES:  CR0: 80050033
  [21388.637483] CR2: 7fbb8f20a000 CR3: 00046620a005 CR4: 
003606e0
  [21388.637486] Call Trace:
  [21388.637489]  
  [21388.637502]  ? pfifo_fast_enqueue+0x150/0x150
  [21388.637513]  call_timer_fn+0x32/0x130
  [21388.637524]  __run_timers.part.0+0x180/0x280
  [21388.637534]  ? timerqueue_add+0x9b/0xb0
  [21388.637540]  ? enqueue_hrtimer+0x3d/0x90
  [21388.637550]  ? recalibrate_cpu_khz+0x10/0x10
  [21388.637556]  ? ktime_get+0x3e/0xa0
  [21388.637566]  run_timer_softirq+0x2a/0x50
  [21388.637574]  __do_softirq+0xe1/0x2d6
  [21388.637580]  ? hrtimer_interrupt+0x13b/0x220
  [21388.637588]  irq_exit+0xae/0xb0
  [21388.637595]  smp_apic_timer_interrupt+0x7b/0x140
  [21388.637601]  apic_timer_interrupt+0xf/0x20
  [21388.637603]  
  [21388.637612] RIP: 0010:cpuidle_enter_state+0xc5/0x450
  [21388.637616] Code: ff e8 af 2c 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 
f6 c4 02 0f 85 65 03 00 00 31 ff e8 02 8a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 
0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d
  [21388.637619] RSP: 0018:b70f800f3e38 EFLAGS: 0246 ORIG_RAX: 
ff13
  [21388.637622] RAX: 99f6de56ad00 RBX: 83d59b40 RCX: 
001f
  [21388.637624] RDX:  RSI: 4041ceb5 RDI: 

  [21388.637626] RBP: b70f800f3e78 R08: 1373ee1f080a R09: 
16b1
  [21388.637628] R10: 99f6de569a00 R11: 99f6de5699e0 R12: 
99f6de575700
  [21388.637630] R13: 0006 R14: 0006 

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

[Ubuntu Kernel Bot]

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

apport-collect 1869940

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

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

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

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

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

Title:
  No networks available/visible after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  WiFI network disconnected and no networks visible after resume from
  suspend. Had to reboot the machine to get networking (WiFI) back up
  and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 21:18:43 2020
  InstallationDate: Installed on 2020-03-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  IpRoute:
   default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp59s0 scope link metric 1000 
   192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
   DORIAN  2c3f821d-0865-4747-974a-2f861ee0dc38  wifi  1585682245  tis 31 mar 
2020 21:17:25  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp59s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/DORIAN.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp59s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  DORIAN  
2c3f821d-0865-4747-974a-2f861ee0dc38  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp59s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available

[Frank Heimes]

It's now also in linux-next, tagged with 'next-20200515'.
Pretty big patch for an SRU, but can cherry-picked cleanly from focal 
master-next.
I'll start to prepare the SRU soon - changing status to Triaged ...


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

** Changed in: ubuntu-z-systems
   Status: Incomplete => Triaged

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

Title:
  [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO
  instructions are available

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  One of the PCI enhancements on Z15 are the enhanced PCI load/store
  instructions which can be executed directly from user space code. When
  these instructions are available and preexisting user space code still
  uses the old s390_pci_mmio_write/read system calls, the system calls
  fail with an "Unable to handle kernel pointer dereference in virtual
  kernel address space" in the kernel.  This issue affects distributions
  which have the enablement for Z15 PCI enhancements and where customers
  run workloads which accesses PCI adapters from user space, e.g. RDMA
  applications.  To solve this, the system call implementation needs to
  be enhanced to provide to execute enhanced PCI load/store instructions
  on behalf of the user space application making use of the mappings
  into its virtual address space

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874055/+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 1879276] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: eoan

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

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

[Ubuntu Kernel Bot]

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

apport-collect 1870442

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

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

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

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

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 

[Kernel-packages] [Bug 1861532] Re: brightness control not working [Lenovo Legion Y540/Y545]

[Kai-Heng Feng]

Can you please attach output of `ls /sys/class/backlight`?

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

Title:
  brightness control not working [Lenovo Legion Y540/Y545]

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  after selecting nvidia-driver-435 in livepatch- additional drivers the
  brightness control stops working after the first reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 31 22:00:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 4.15.0-76-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3ffc]
  InstallationDate: Installed on 2020-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 81Q4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=084301b5-fdae-4c92-811e-0536a3b7555b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN35WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y540-17IRH
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81Q4:pvrLegionY540-17IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLegionY540-17IRH:
  dmi.product.family: Legion Y540-17IRH
  dmi.product.name: 81Q4
  dmi.product.sku: LENOVO_MT_81Q4_BU_idea_FM_Legion Y540-17IRH
  dmi.product.version: Legion Y540-17IRH
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861532/+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 1865471] Re: USB 3.1 Gen 1 not work after using suspend

[Kai-Heng Feng]

Can you please run "echo 0 | sudo tee /sys/power/pm_async", then suspend
to see if it works??

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning.

  I use "suspend"(settings -> energy -> When the shutdown...) on 18.04.

  Each wake up, USB ports 3.1 Gen 1 don't work (only those on the
  motherboard on the back of the case).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x)

  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:

  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---

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

[Ubuntu Kernel Bot]

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

apport-collect 1878007

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

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

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

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

** Tags added: 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/1878007

Title:
   Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron
  7373. When the screen is turned off (so, the suspend or screen lock
  features are affected), the system freeze and I need to force the
  laptop turn off and on again. There are some cases when it turn off
  the screen without issues, but most of the time it freezes. Even
  "SysRq REISUB" does not work for rebooting when system crash. I can
  reproduce the issue using `xset dpms force off`.

  Initially this bug report was filled thinking it was a suspend issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144

  Syslog or systemd journal does not provide any error information about
  the crash.

  "lsb_release -rd" output:
  Description: Ubuntu 20.04 LTS
  Release: 20.04

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

[Ubuntu Kernel Bot]

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

apport-collect 1879299

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

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

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

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

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

Title:
  enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x
  LPAR / zVM ( docker still configured, unable to disable fan)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on E/F s390x LPAR / zVM (they are manually provisioned
  systems)

  Test failed with:
  docker still configured, unable to disable fan

    * Command:
    ./ubuntu_fan_smoke_test.sh 10.245.0.0/16
    Exit status: 1
    Duration: 12.935628891

    stdout:
    Running in the Canonical CI environment
    Testing Fan Networking (pre-0.13.0 API)
    docker pull s390x/ubuntu: PASSED
    enable disable fan test: FAILED (fanctl returned 1)
    stderr:
    /usr/sbin/fanatic: docker still configured, unable to disable fan

  docker container ls shows there is no docker running
  $ sudo docker container ls -a
  CONTAINER IDIMAGE   COMMAND CREATED   
  STATUS  PORTS   NAMES
  $

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  CurrentDmesg:

  Date: Mon May 18 11:08:11 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/kl04vg01-kl04root crashkernel=196M 
BOOT_IMAGE=
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-03-03 (76 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879299/+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 1879305] [NEW] [UBUNTU 20.04] Subiquity installer cannot find dasd device

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.

Installation stops at trying to find a dasd disk. I tried following
Curtin documentation on dasd and examples from
https://github.com/canonical/curtin/blob/master/examples/tests/basic-
dasd.yaml with different options, but had no success.

Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

#cloud-config
autoinstall:
  version: 1
  reporting:
remote:
  type: webhook
  endpoint: http://t35lp37.lnxne.boe:8080/log/
  level: DEBUG
  refresh-installer:
update: yes
  apt:
primary:
- arches: [s390x]
  uri: http://us.ports.ubuntu.com/ubuntu-ports
  identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
  keyboard: {layout: us, variant: ''}
  locale: en_US
  ssh:
allow-pw: true
authorized-keys: []
install-server: true
  storage:
config:
  - {device_id: 0.0.3695, blocksize: 4096, disk_layout: cdl, mode: quick, 
preserve: false, type: dasd, id: dasd-dasda}
  - {ptable: vtoc, serial: 0X3695, path: /dev/dasda, wipe: 
superblock-recursive, preserve: false, name: '', grub_device: false, device_id: 
0.0.3695, type: disk, id: disk-dasda}
  - {device: disk-dasda, size: 22153265152, wipe: superblock, flag: '', 
number: 1, preserve: false, type: partition, id: partition-0}
  - {fstype: ext4, volume: partition-0, preserve: false, type: format, id: 
format-0}
  - {device: format-0, path: /, type: mount, id: mount-0}


I get the following output on the webhook:
curtin start subiquity/Filesystem/apply_autoinstall_config:
curtin start 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config:
curtin finish 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: 
{'device_id': '0.0.3695', 'grub_device': False, 'id': 'disk-dasda', 'name': '', 
'path': '/dev/dasda', 'preserve': False, 'ptable': 'vtoc', 'serial': '0X3695', 
'type': 'disk', 'wipe': 'superblock-recursive'} matched no disk
curtin finish subiquity/Filesystem/apply_autoinstall_config: {'device_id': 
'0.0.3695', 'grub_device': False, 'id': 'disk-dasda', 'name': '', 'path': 
'/dev/dasda', 'preserve': False, 'ptable': 'vtoc', 'serial': '0X3695', 'type': 
'disk', 'wipe': 'superblock-recursive'} matched no disk
curtin start subiquity/Error/1589794065.193394184.ui/add_info:
curtin finish subiquity/Error/1589794065.193394184.ui/add_info: written to 
/var/crash/1589794065.193394184.ui.crash


When I use a simple configuration described in Ubuntu Wiki ( 
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigReference#storage
 ), I get a different output:

  storage:
layout:
  name: direct

curtin start subiquity/Filesystem/apply_autoinstall_config:
curtin finish subiquity/Filesystem/_probe/probe_once: restricted=False
curtin finish subiquity/Filesystem/_probe:
curtin start 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config:
curtin finish 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: 'None 

   Type' object has no attribute 'grub_device'
curtin finish subiquity/Filesystem/apply_autoinstall_config: 'NoneType' object 
has no attribu  
  te 'grub_device'

(same with layout "lvm")

Manual installation works fine, but I need to enable the DASD in the
menu.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-185919 severity-high 
targetmilestone-inin2004
-- 
[UBUNTU 20.04] Subiquity installer cannot find dasd device
https://bugs.launchpad.net/bugs/1879305
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1879305] [NEW] [UBUNTU 20.04] Subiquity installer cannot find dasd device

[bugproxy]

Public bug reported:

I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.

Installation stops at trying to find a dasd disk. I tried following
Curtin documentation on dasd and examples from
https://github.com/canonical/curtin/blob/master/examples/tests/basic-
dasd.yaml with different options, but had no success.

Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2 
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
 
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
 autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/

#cloud-config
autoinstall:
  version: 1
  reporting:
remote:
  type: webhook
  endpoint: http://t35lp37.lnxne.boe:8080/log/
  level: DEBUG
  refresh-installer:
update: yes
  apt:
primary:
- arches: [s390x]
  uri: http://us.ports.ubuntu.com/ubuntu-ports
  identity: {hostname: m8330038, password: 
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
  keyboard: {layout: us, variant: ''}
  locale: en_US
  ssh:
allow-pw: true
authorized-keys: []
install-server: true
  storage:
config:
  - {device_id: 0.0.3695, blocksize: 4096, disk_layout: cdl, mode: quick, 
preserve: false, type: dasd, id: dasd-dasda}
  - {ptable: vtoc, serial: 0X3695, path: /dev/dasda, wipe: 
superblock-recursive, preserve: false, name: '', grub_device: false, device_id: 
0.0.3695, type: disk, id: disk-dasda}
  - {device: disk-dasda, size: 22153265152, wipe: superblock, flag: '', 
number: 1, preserve: false, type: partition, id: partition-0}
  - {fstype: ext4, volume: partition-0, preserve: false, type: format, id: 
format-0}
  - {device: format-0, path: /, type: mount, id: mount-0}


I get the following output on the webhook:
curtin start subiquity/Filesystem/apply_autoinstall_config:
curtin start 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config:
curtin finish 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: 
{'device_id': '0.0.3695', 'grub_device': False, 'id': 'disk-dasda', 'name': '', 
'path': '/dev/dasda', 'preserve': False, 'ptable': 'vtoc', 'serial': '0X3695', 
'type': 'disk', 'wipe': 'superblock-recursive'} matched no disk
curtin finish subiquity/Filesystem/apply_autoinstall_config: {'device_id': 
'0.0.3695', 'grub_device': False, 'id': 'disk-dasda', 'name': '', 'path': 
'/dev/dasda', 'preserve': False, 'ptable': 'vtoc', 'serial': '0X3695', 'type': 
'disk', 'wipe': 'superblock-recursive'} matched no disk
curtin start subiquity/Error/1589794065.193394184.ui/add_info:
curtin finish subiquity/Error/1589794065.193394184.ui/add_info: written to 
/var/crash/1589794065.193394184.ui.crash


When I use a simple configuration described in Ubuntu Wiki ( 
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigReference#storage
 ), I get a different output:

  storage:
layout:
  name: direct

curtin start subiquity/Filesystem/apply_autoinstall_config:
curtin finish subiquity/Filesystem/_probe/probe_once: restricted=False
curtin finish subiquity/Filesystem/_probe:
curtin start 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config:
curtin finish 
subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: 'None 

   Type' object has no attribute 'grub_device'
curtin finish subiquity/Filesystem/apply_autoinstall_config: 'NoneType' object 
has no attribu  
  te 'grub_device'

(same with layout "lvm")

Manual installation works fine, but I need to enable the DASD in the
menu.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-185919 severity-high 
targetmilestone-inin2004

** Tags added: architecture-s39064 bugnameltc-185919 severity-high
targetmilestone-inin2004

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU 20.04] Subiquity installer cannot find dasd device

Status in linux package in Ubuntu:
  New

Bug description:
  I'm installing Ubuntu 20.04 with a nocloud-net installation source on
  a z/VM guest. I'm currently limited to seeing installation output only
  through webhook reporter, because I cannot access shell on the target
  

[Kernel-packages] [Bug 1878147] Re: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED

[You-Sheng Yang]

https://lore.kernel.org/linux-
wireless/20200518081444.7664-1-yhchu...@realtek.com/

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

Title:
  Realtek 8723DE [10ec:d723] subsystem [10ec:d738]  disconnects
  unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [ 7.002889] wlp5s0: authenticate with a4:56:30:cc:0f:30
  [ 7.146619] wlp5s0: send auth to a4:56:30:cc:0f:30 (try 1/3)
  [ 7.258747] wlp5s0: authenticated
  [ 7.262852] wlp5s0: associate with a4:56:30:cc:0f:30 (try 1/3)
  [ 7.266190] wlp5s0: RX AssocResp from a4:56:30:cc:0f:30 (capab=0x431 status=0 
aid=4)
  [ 7.266205] rtw_pci :05:00.0: sta a4:56:30:cc:0f:30 joined with macid 0
  [ 7.266425] rtw_pci :05:00.0: failed to send h2c command
  [ 7.266437] wlp5s0: associated
  [ 7.299291] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready

  That error "failed to send h2c command" is only observed multiple
  times in current oem-osp1 kernel for multiple times during the test
  rounds, and is never found with the OOT module built from
  https://github.com/rtlwifi-linux/rtw88_8723de/tree/master-coex-trial2.
  And so is following error when reproduced against Ubuntu kernels:

  [ 207.523312] wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason:
  23=IEEE8021X_FAILED).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1050.53
  ProcVersionSignature: Ubuntu 5.0.0-1050.55-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1050-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1667 F pulseaudio
u  3061 F pulseaudio
   /dev/snd/controlC0:  gdm1667 F pulseaudio
u  3061 F pulseaudio
  Date: Tue May 12 14:59:32 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-grenn+X39
  InstallationDate: Installed on 2020-04-10 (31 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 004: ID 04d9:0024 Holtek Semiconductor, Inc. 
   Bus 001 Device 003: ID 0bda:d739 Realtek Semiconductor Corp. 
   Bus 001 Device 005: ID 062a:4c01 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3888
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1050-oem-osp1 
root=UUID=17e0a095-201d-4dca-a2e7-6e16dcd6a797 ro quiet splash vt.handoff=1
  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-5.0.0-1050-oem-osp1 N/A
   linux-backports-modules-5.0.0-1050-oem-osp1  N/A
   linux-firmware   1.173.18
  SourcePackage: linux-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.19.29
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.19.29:bd02/13/2020:svnDellInc.:pnVostro3888:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3888
  dmi.product.sku: 09B2
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1878147/+subscriptions

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

[Kernel-packages] [Bug 1874055] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From niklas.schne...@ibm.com 2020-05-18 07:18 EDT---
I agree, it's pretty big but this was the least impact approach we could think
of and it fixes a kernel crash that can be triggered from user space simply by 
invoking the s390_pci_read/write_mmio syscalls when running with MIO.

The code mostly mirrors existing PCI code with the addition of the
secondary address space access and is otherwise self contained so it
should be extremely unlikely to impact anything apart from these two
syscalls.

With the new PCI instructions that can be used in userspace, these
syscalls will not be needed in the future but we of course still need
them for applications that have not been updated to use the new
instructions.

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

Title:
  [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO
  instructions are available

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  One of the PCI enhancements on Z15 are the enhanced PCI load/store
  instructions which can be executed directly from user space code. When
  these instructions are available and preexisting user space code still
  uses the old s390_pci_mmio_write/read system calls, the system calls
  fail with an "Unable to handle kernel pointer dereference in virtual
  kernel address space" in the kernel.  This issue affects distributions
  which have the enablement for Z15 PCI enhancements and where customers
  run workloads which accesses PCI adapters from user space, e.g. RDMA
  applications.  To solve this, the system call implementation needs to
  be enhanced to provide to execute enhanced PCI load/store instructions
  on behalf of the user space application making use of the mappings
  into its virtual address space

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874055/+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 1879299] Re: enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x LPAR / zVM ( docker still configured, unable to disable fan)

[Po-Hsu Lin]

These docker fanatic config can be removed with the following interactive 
command:
fanatic deconfigure

After that, the test can be executed properly.

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

Title:
  enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x
  LPAR / zVM ( docker still configured, unable to disable fan)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on E/F s390x LPAR / zVM (they are manually provisioned
  systems)

  Test failed with:
  docker still configured, unable to disable fan

    * Command:
    ./ubuntu_fan_smoke_test.sh 10.245.0.0/16
    Exit status: 1
    Duration: 12.935628891

    stdout:
    Running in the Canonical CI environment
    Testing Fan Networking (pre-0.13.0 API)
    docker pull s390x/ubuntu: PASSED
    enable disable fan test: FAILED (fanctl returned 1)
    stderr:
    /usr/sbin/fanatic: docker still configured, unable to disable fan

  docker container ls shows there is no docker running
  $ sudo docker container ls -a
  CONTAINER IDIMAGE   COMMAND CREATED   
  STATUS  PORTS   NAMES
  $

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  CurrentDmesg:

  Date: Mon May 18 11:08:11 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/kl04vg01-kl04root crashkernel=196M 
BOOT_IMAGE=
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-03-03 (76 days ago)

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

[Dave Jones]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1879393/+attachment/5373659/+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/1879393

Title:
  Delayed failure in Genesys USB3 SD card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
  Ubuntu Xenial for many months. Recently, I re-installed the machine it
  was attached to with a fresh install of Ubuntu Focal. When initially
  booted, the device works perfectly (at least, the USB3 ports and SD
  card reader do; those are the only ports I use on it). However, after
  some period of time I inevitably find the device has stopped working,
  and dmesg is flooded with repeats of the following block of messages
  (I include several copies below so the typical time-delay between
  repeats can be observed):

  [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   

  [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.

  [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
 
  [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
   
  [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39826.850677] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39826.938742] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
  [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39859.618979] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39859.706965] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd

  The delay before failure (and these messages appearing) is highly
  variable. Sometimes it's within a couple of minutes of booting the
  machine; sometimes the device works happily for a couple of hours
  before failure.

  I've found that simply replugging the device (temporarily) solves the
  issue, but obviously I'd prefer the device to be as reliable as it was
  under the Xenial kernel.

  This may be related to #1798979 which features extremely similar log
  messages on failure, but the symptoms are ever so slightly different
  (no CPU spike, no blinking LED), as is the model of card reader, hence
  why I've filed a separate bug. I'll add an apport report after filing
  this, but I should add there are multiple card-readers on this machine
  (my work involves raspberry pis, so I often find myself re-writing
  cards in bulk :). The specific one with the issue is listed as follows
  in the lsusb output:

  Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and
  microSDXC CardReader

  The other card reader listed in that output (realtek) is a separate device 
with no issues.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-09 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
 

[Kernel-packages] [Bug 1879393] ProcInterrupts.txt

[Dave Jones]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1879393/+attachment/5373657/+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/1879393

Title:
  Delayed failure in Genesys USB3 SD card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
  Ubuntu Xenial for many months. Recently, I re-installed the machine it
  was attached to with a fresh install of Ubuntu Focal. When initially
  booted, the device works perfectly (at least, the USB3 ports and SD
  card reader do; those are the only ports I use on it). However, after
  some period of time I inevitably find the device has stopped working,
  and dmesg is flooded with repeats of the following block of messages
  (I include several copies below so the typical time-delay between
  repeats can be observed):

  [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   

  [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.

  [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
 
  [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
   
  [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39826.850677] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39826.938742] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
  [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39859.618979] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39859.706965] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd

  The delay before failure (and these messages appearing) is highly
  variable. Sometimes it's within a couple of minutes of booting the
  machine; sometimes the device works happily for a couple of hours
  before failure.

  I've found that simply replugging the device (temporarily) solves the
  issue, but obviously I'd prefer the device to be as reliable as it was
  under the Xenial kernel.

  This may be related to #1798979 which features extremely similar log
  messages on failure, but the symptoms are ever so slightly different
  (no CPU spike, no blinking LED), as is the model of card reader, hence
  why I've filed a separate bug. I'll add an apport report after filing
  this, but I should add there are multiple card-readers on this machine
  (my work involves raspberry pis, so I often find myself re-writing
  cards in bulk :). The specific one with the issue is listed as follows
  in the lsusb output:

  Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and
  microSDXC CardReader

  The other card reader listed in that output (realtek) is a separate device 
with no issues.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-09 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American 

[Kernel-packages] [Bug 1879393] ProcEnviron.txt

[Dave Jones]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1879393/+attachment/5373656/+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/1879393

Title:
  Delayed failure in Genesys USB3 SD card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
  Ubuntu Xenial for many months. Recently, I re-installed the machine it
  was attached to with a fresh install of Ubuntu Focal. When initially
  booted, the device works perfectly (at least, the USB3 ports and SD
  card reader do; those are the only ports I use on it). However, after
  some period of time I inevitably find the device has stopped working,
  and dmesg is flooded with repeats of the following block of messages
  (I include several copies below so the typical time-delay between
  repeats can be observed):

  [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   

  [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.

  [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
 
  [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
   
  [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39826.850677] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39826.938742] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
  [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39859.618979] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39859.706965] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd

  The delay before failure (and these messages appearing) is highly
  variable. Sometimes it's within a couple of minutes of booting the
  machine; sometimes the device works happily for a couple of hours
  before failure.

  I've found that simply replugging the device (temporarily) solves the
  issue, but obviously I'd prefer the device to be as reliable as it was
  under the Xenial kernel.

  This may be related to #1798979 which features extremely similar log
  messages on failure, but the symptoms are ever so slightly different
  (no CPU spike, no blinking LED), as is the model of card reader, hence
  why I've filed a separate bug. I'll add an apport report after filing
  this, but I should add there are multiple card-readers on this machine
  (my work involves raspberry pis, so I often find myself re-writing
  cards in bulk :). The specific one with the issue is listed as follows
  in the lsusb output:

  Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and
  microSDXC CardReader

  The other card reader listed in that output (realtek) is a separate device 
with no issues.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-09 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends 

[Kernel-packages] [Bug 1879393] ProcModules.txt

[Dave Jones]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1879393/+attachment/5373658/+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/1879393

Title:
  Delayed failure in Genesys USB3 SD card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
  Ubuntu Xenial for many months. Recently, I re-installed the machine it
  was attached to with a fresh install of Ubuntu Focal. When initially
  booted, the device works perfectly (at least, the USB3 ports and SD
  card reader do; those are the only ports I use on it). However, after
  some period of time I inevitably find the device has stopped working,
  and dmesg is flooded with repeats of the following block of messages
  (I include several copies below so the typical time-delay between
  repeats can be observed):

  [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   

  [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.

  [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
 
  [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
   
  [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39826.850677] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39826.938742] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
  [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39859.618979] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39859.706965] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd

  The delay before failure (and these messages appearing) is highly
  variable. Sometimes it's within a couple of minutes of booting the
  machine; sometimes the device works happily for a couple of hours
  before failure.

  I've found that simply replugging the device (temporarily) solves the
  issue, but obviously I'd prefer the device to be as reliable as it was
  under the Xenial kernel.

  This may be related to #1798979 which features extremely similar log
  messages on failure, but the symptoms are ever so slightly different
  (no CPU spike, no blinking LED), as is the model of card reader, hence
  why I've filed a separate bug. I'll add an apport report after filing
  this, but I should add there are multiple card-readers on this machine
  (my work involves raspberry pis, so I often find myself re-writing
  cards in bulk :). The specific one with the issue is listed as follows
  in the lsusb output:

  Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and
  microSDXC CardReader

  The other card reader listed in that output (realtek) is a separate device 
with no issues.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-09 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends 

[Kernel-packages] [Bug 1879393] Lsusb-v.txt

[Dave Jones]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1879393/+attachment/5373653/+files/Lsusb-v.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/1879393

Title:
  Delayed failure in Genesys USB3 SD card reader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a "UGreen USB3 Hub/SD card reader" which worked reliably under
  Ubuntu Xenial for many months. Recently, I re-installed the machine it
  was attached to with a fresh install of Ubuntu Focal. When initially
  booted, the device works perfectly (at least, the USB3 ports and SD
  card reader do; those are the only ports I use on it). However, after
  some period of time I inevitably find the device has stopped working,
  and dmesg is flooded with repeats of the following block of messages
  (I include several copies below so the typical time-delay between
  repeats can be observed):

  [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   

  [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.

  [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
 
  [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
   
  [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using 
xhci_hcd
  [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39826.850677] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39826.938742] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
  [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr   
   [39859.618979] xhci_hcd :05:00.0: A Set TR Deq 
Ptr command is pending.   [39859.706965] usb 6-2.3: 
reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd

  The delay before failure (and these messages appearing) is highly
  variable. Sometimes it's within a couple of minutes of booting the
  machine; sometimes the device works happily for a couple of hours
  before failure.

  I've found that simply replugging the device (temporarily) solves the
  issue, but obviously I'd prefer the device to be as reliable as it was
  under the Xenial kernel.

  This may be related to #1798979 which features extremely similar log
  messages on failure, but the symptoms are ever so slightly different
  (no CPU spike, no blinking LED), as is the model of card reader, hence
  why I've filed a separate bug. I'll add an apport report after filing
  this, but I should add there are multiple card-readers on this machine
  (my work involves raspberry pis, so I often find myself re-writing
  cards in bulk :). The specific one with the issue is listed as follows
  in the lsusb output:

  Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and
  microSDXC CardReader

  The other card reader listed in that output (realtek) is a separate device 
with no issues.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-09 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  

[Kernel-packages] [Bug 1879153] WifiSyslog.txt

[Morten Sjøgren]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1879153/+attachment/5373732/+files/WifiSyslog.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/1879153

Title:
  amdgpu prevents poweroff

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Turning off Kubuntu 20.04 stops short of actually powering off the
  machine.

  The monitors goes into suspend mode, but PC is still powered on and I
  have to hold the power button in to turn it off.

  I initially suspected an ACPI problem, but I found these two errors in
  /var/log/syslog after turning the computer on again:

  May 16 02:46:53 desktop kernel: [475329.688676] [ cut here 
]
  May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 
dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm 
xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc 
rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio 
snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp 
snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm
  May 16 02:46:53 desktop kernel: [475329.688783]  mac80211 intel_cstate 
libarc4 snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt 
btusb snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev 
input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac 
cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd 
gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea 
sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core 
libahci wmi video pinctrl_cannonlake pinctrl_intel
  May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg 
Tainted: GW 5.4.0-29-generic #33-Ubuntu
  May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte 
Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 
03/14/2019
  May 16 02:46:53 desktop kernel: [475329.688879] RIP: 
0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 
48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 
a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 
85 56 01 00
  May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 
EFLAGS: 00010202
  May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 
978c9de001b8 RCX: 
  May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 
978c9de001b8 RDI: 9791c8d5
  May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: 
bd3c81567554 R09: 
  May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: 
 R12: 0001
  May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 
9791c8d5 R15: 978c9de001b8
  May 16 02:46:53 desktop kernel: [475329.66] FS:  7fe19eb9ca80() 
GS:9791ddb0() knlGS:
  May 16 02:46:53 desktop kernel: [475329.67] CS:  0010 DS:  ES:  
CR0: 80050033
  May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 
00088a80c006 CR4: 003606e0
  May 16 02:46:53 desktop kernel: [475329.68] Call Trace:
  May 16 02:46:53 desktop kernel: [475329.688959]  
dcn20_pipe_control_lock.part.0+0x112/0x1f0 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689026]  
dcn20_pipe_control_lock+0x1c/0x20 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689087]  
dc_stream_set_cursor_position+0x128/0x160 [amdgpu]
  May 16 02:46:53 desktop kernel: [475329.689152]  
handle_cursor_update.isra.0+0x226/0x300 [amdgpu]
  May 16 02:46:53