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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Desktop installation fails to show new login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I install 20.04 desktop, the try ubuntu mechanism works fine with
  my AST2400 graphics and LG display. When I then install on my hard
  disk (using all default settings) the system boots, I can see the
  orange screen with "Ubuntu" logo text, but I cannot move the mouse
  pointer and I do not see a login.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 17:45:18 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Supermicro Super Server
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SDV-TLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd05/27/2015:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-TLN4F:rvr1.02:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Upon update te 5.4.0-37-generic, boot hangs with black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon updating to linux-5.p.0-37 this morning, it asked me to restart,
  and when it did, all I had was a black screen.  I could see the power
  was on, because the power led was lit.  I rebooted a couple times with
  the same result.  Then rebooted to single user, did fsck, repair
  broken packages, and rebooted, and it came up, but not using both
  monitors.  So I did another update of the packages, and rebooted.  It
  was still black.  I ended up rebooting on the previous kernel, and it
  works now, and I'm submitting this bug report using that setup.  If it
  would be helpful, I can reboot single user, and eventually get it up
  with only the laptop monitor, and submit a ubuntu-bug report that way
  too.

  Thanks for your great work on Ubuntu!

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frohro 1939 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 10:30:41 2020
  InstallationDate: Installed on 2019-04-19 (418 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  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-33-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882992/+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 1882999] [NEW] Wifi won't work.

[Furkan]

Public bug reported:

On HP pavilion gaming 15 ec0007nt and Linux mint 19.3 Tricia Cinnamon, I 
couldn't connect wifi. Nothing showing on wifi menu. I can't get any log from 
codes on guideline.
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  furkan 1791 F pulseaudio
 /dev/snd/controlC1:  furkan 1791 F pulseaudio
 /dev/snd/pcmC1D0p:   furkan 1791 F...m pulseaudio
 /dev/snd/controlC2:  furkan 1791 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19.3
InstallationDate: Installed on 2020-05-23 (18 days ago)
InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=820f1788-6f2a-41bc-94fe-9691a68157b9 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-32-generic N/A
 linux-backports-modules-5.0.0-32-generic  N/A
 linux-firmware1.173.18
Tags:  tricia
Uname: Linux 5.0.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/20/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.02
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86D5
dmi.board.vendor: HP
dmi.board.version: 96.16
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd09/20/2019:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D5:rvr96.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx
dmi.product.sku: 8BW49EA#AB8
dmi.sys.vendor: HP

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


** Tags: apport-collected tricia

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

Title:
  Wifi won't work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP pavilion gaming 15 ec0007nt and Linux mint 19.3 Tricia Cinnamon, I 
couldn't connect wifi. Nothing showing on wifi menu. I can't get any log from 
codes on guideline.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  furkan 1791 F pulseaudio
   /dev/snd/controlC1:  furkan 1791 F pulseaudio
   /dev/snd/pcmC1D0p:   furkan 1791 F...m pulseaudio
   /dev/snd/controlC2:  furkan 1791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  InstallationDate: Installed on 2020-05-23 (18 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=820f1788-6f2a-41bc-94fe-9691a68157b9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.173.18
  Tags:  tricia
  Uname: Linux 5.0.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86D5
  dmi.board.vendor: HP
  dmi.board.version: 96.16
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd09/20/2019:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D5:rvr96.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx
  dmi.product.sku: 8BW49EA#AB8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882999/+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 1882997] [NEW] Desktop installation fails to show new login

[Bart Besseling]

Public bug reported:

When I install 20.04 desktop, the try ubuntu mechanism works fine with
my AST2400 graphics and LG display. When I then install on my hard disk
(using all default settings) the system boots, I can see the orange
screen with "Ubuntu" logo text, but I cannot move the mouse pointer and
I do not see a login.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 17:45:18 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Supermicro Super Server
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-26-generic N/A
 linux-backports-modules-5.4.0-26-generic  N/A
 linux-firmware1.187
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0a
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X10SDV-TLN4F
dmi.board.vendor: Supermicro
dmi.board.version: 1.02
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd05/27/2015:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-TLN4F:rvr1.02:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Super Server
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug focal

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

Title:
  Desktop installation fails to show new login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I install 20.04 desktop, the try ubuntu mechanism works fine with
  my AST2400 graphics and LG display. When I then install on my hard
  disk (using all default settings) the system boots, I can see the
  orange screen with "Ubuntu" logo text, but I cannot move the mouse
  pointer and I do not see a login.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 17:45:18 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Supermicro Super Server
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SDV-TLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd05/27/2015:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-TLN4F:rvr1.02:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  add 16-bit width registers support for EEPROM at24 device

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU For Bionic

  [Impact]
  Larger EEPROM devices that use 16-bit addresses couldn't be accessed.

  The i2c/smbus currently only support to access data with 8-bit width of
  address. In some larger device, such as larger EEPROM, it requires to
  access the address large than 0xff, so it needs to extend address space
  to 16-bit width.

  [Fix]
  This commit is derivated from below commit, and then modified and provided
  by customer
  https://patchwork.ozlabs.org/patch/545292/

  Unfortunately, this commit doesn't get into mainline in the end, so I migrate 
the commit to latest kernel and finally get it merged.
  https://lkml.org/lkml/2020/4/24/635

  [Test]
  Verified on Eurotech's platforms.

  [Regression Potential]
  Low, this patch only changes the behavior of the device which has 
AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 
24c256.

  =
  SRU For Focal

  [Impact]
  Larger EEPROM devices that use 16-bit addresses couldn't be accessed.

  The i2c/smbus currently only support to access data with 8-bit width of
  address. In some larger device, such as larger EEPROM, it requires to
  access the address large than 0xff, so it needs to extend address space
  to 16-bit width.

  [Fix]
  Clear cherry pick from linux-next
  82f25bd73c0b regmap-i2c: add 16-bit width registers support

  [Test]
  Verified on Eurotech's platforms.

  [Regression Potential]
  Low, this patch provides new access functions for 16-bit registers,
  shouldn't affect any other devices which are already working well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+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 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Performing function level reset of AMD onboard USB and audio devices
  causes system lockup

Status in linux package in Ubuntu:
  In Progress
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:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
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:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justifcation]

  [Impact]

  Devices affected:

  * [1022:148c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Starship
USB 3.0 Host Controller
  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse
USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller

  Despite advertising FLReset device capabilities, performing a function level
  reset of either of these devices causes the system to lock up. This is of
  particular issue where these devices appear in their own IOMMU groups and are
  well suited to VFIO passthrough.

  Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode
  update, and affects dozens of motherboard models across various vendors.

  Additional discussion of this issue:
  
https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/

  [Fix]

  Two commits currently landed in linux-pci pci/virutualization:
  * 0d14f06cd665 PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0
  * 5727043c73fd PCI: Avoid FLR for AMD Starship USB 3.0

  [Test Case]

  Peform the test on an impacted system:

  * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4
socket);
  * Ryzen 3000-series CPU (2000-series possibly also affected);
  * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check
vendor release notes)

  In the above case where ':10:00.3' is the USB controller '1022:149c', 
issue
  a reset command:

$ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset

  Impacted systems will not return successfully and become unstable, requiring a
  reboot. `/var/logs/syslog` will show something resembling the following:

xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting
xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting
xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting
xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting
xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting
xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting
xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up
clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as 
unstable because the skew is too large:
clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: 
clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: 

tsc: Marking TSC unstable due to clocksource watchdog
TSC found unstable after boot, most likely due to broken BIOS. Use 
'tsc=unstable'.
sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, 
-2209419)

  [Regression Risk]
  Low. These two patches affect only systems with a device needs fix.

  == Original Bug Description ==

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  [Impact]

  Devices affected:

  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse HD Audio Controller

  Despite advertisi

[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1873325

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed

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 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

** Tags added: verification-needed-bionic

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+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 1877955] Re: Fix for secure boot rules in IMA arch policy on powerpc

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1877955

Title:
  Fix for secure boot rules in IMA arch policy on powerpc

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Currently the kernel module appended signature is verified twice
  (finit_module) - once by the module_sig_check() and again by IMA.

  * To prevent this the powerpc secure boot rules define an IMA
  architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
  not enabled.

  * But this doesn't take the ability into account of enabling
  "sig_enforce" at the boot command line (module.sig_enforce=1).

  * Including the IMA module appraise rule results in failing the
  finit_module syscall, unless the module signing public key is loaded
  onto the IMA keyring.

  * This patch fixes secure boot policy rules to be based on
  CONFIG_MODULE_SIG instead.

  [Fix]

  * fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
  Fix secure boot rules in ima arch policy"

  [Test Case]

  * Perform a secure boot on a powerpc system with
  'module.sig_enforce=1' set at the boot command.

  * If the IMA module appraise rule is included, the finit_module
  syscall will fail (unless the module signing public key got loaded
  onto the IMA keyring) without having the patch in place.

  * The verification needs to be done by the IBM Power team.

  [Regression Potential]

  * There is (always) a certain regression risk with having code
  changes, especially in the secure boot area.

  * But this patch is limited to the powerpc platform and will not
  affect any other architecture.

  * It got discussed at 
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
    before it became finally upstream accepted with kernel 5.7-rc7.

  * The secure boot code itself wasn't really touched, rather than it's basis 
for execution.
    The IMA policy rule for module appraisal is now added only if 
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
    Hence the change is very limited and straightforward.

  [Other]

  * Since the patch got upstream with 5.7-rc7, it is already in groovy, hence 
this SRU is for focal only.
  __

  == Comment: #0 - Michael Ranweiler  - 2020-04-22 
14:44:31 ==
  +++ This bug was initially created as a clone of Bug #184073 +++

  This bug is a follow on to LP 1866909 to address a missing piece -
  only half the following patch was included in 5.4.0-24.28.

  The upstream patch has an additional fix but it?s not critical for GA.
  It can get included as part of bug fixes. It also affects only power.
  The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
  posted to linux-integrity and linuxppc-dev mailing list
  (https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
  email-na...@linux.ibm.com/T/#u)

  If there are any issues identified during further testing, they will
  get opened as separate issue to be addressed later.

  Thanks & Regards,
     - Nayna

  == Comment: #4 - Michael Ranweiler  - 2020-05-11 
02:23:35 ==
  Updated posting:

  https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
  email-na...@linux.ibm.com/T/#u

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+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 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

** Tags added: verification-needed-bionic

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

Title:
  Slow send speed with Intel I219-V on Ubuntu 18.04.1

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
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:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  The throughput measured by iperf3 is around 70% of 1Gbps (Intel I219-LM
  [8086:15b7])
  I219 is a rather cheap NIC and it impacts its throughput if TSO(TCP
  segmentation offload) is enabled.  
  
  [Fix]   
  Disable TSO on NIC and move this task back to CPU fixes this issue.
  The impact of CPU loading is little to none.
  On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU
  usage of iperf3 increases from 1% to 4%
  
  [Verify]
  Origin
  [ ID] Interval Transfer Bandwidth Retr
  [ 4] 0.00-10.00 sec 918 MBytes 770 Mbits/sec 0 sender
  [ 4] 0.00-10.00 sec 916 MBytes 769 Mbits/sec receiver

  Becomes
  [ ID] Interval Transfer Bandwidth Retr
  [ 4] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 0 sender
  [ 4] 0.00-10.00 sec 1.09 GBytes 934 Mbits/sec receiver

  [Regression Potential]
  Low, disable TSO on Ethernet chip will move the TCP segmentation task
  to CPU. This increase CPU loading a little bit, and should not introduce
  any regression. 

  =

  Testing with iperf3 send speed is only 750mbps while receive speed is
  normal - 940mbps.

  Ubuntu 18.04.1
  Msi b250m mortar
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  django 1016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp0s31f6  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A69
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M MORTAR ARCTIC (MS-7A69)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A69
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1802691/+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 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  qeth: utilize virtual MAC for Layer2 OSD devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * A qeth device on a DPM-managed (HMC) IBM Z machine does not obtain
  its MAC address for layer2 OSD interfaces from the OSA Network
  Adapter, instead it uses a random MAC address.

  * This can cause connectivity issues in environments where reliable
  and pre-determined MAC addresses are required, ie. when doing network
  configuration based on DHCP.

  [Fix]

  * Backport 1: https://launchpadlibrarian.net/481647649/0001-s390-qeth-
  improve-fallback-to-random-MAC-address.patch

  * Backport 2: https://launchpadlibrarian.net/481647657/0002-s390-qeth-
  utilize-virtual-MAC-for-Layer2-OSD-devices.patch

  [Test Case]

  * Bring up a qeth L2 OSD interface in DPM-managed (HMC) LPAR

  * Inspect the interface's MAC address. It should be the same as
  displayed in the HMC DPM panels.

  * Due to the fact that a system is needed where the HMC is in DPM moce
  (rather than in classic mode) this needs to be tested by IBM.

  [Regression Potential]

  * There is a certain risk for a regression, since OSA devices are the
  standard netweork devices on s390x.

  * But static network configurations are still more popular for the
  usually long running workload on s390x and not dynamic assignments.

  * On the other hand qeth devices are s390x only, so this will at least
  not affect common code or code for other architectures.

  * The modifications are limited to drivers/s390/net/qeth_*.

  * The patches are upstream since quite a while, which speaks for their
  stability.

  [Other Info]

  * The upstream patch 21b1702af12e "s390/qeth: improve fallback to
  random MAC address" got upstream accepted with 4.18, hence is already
  in all Ubuntu release that are newer than bionic

  * And the upstream patch b144b99fff69 "s390/qeth: utilize virtual MAC
  for Layer2 OSD devices" got upstream accepted with 5.0, hence is also
  already in all Ubuntu release that are newer than bionic.

  __

  ---Problem Description---
  qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 
OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC 
Address.

  This causes connectivity issues in setups where a reliable & pre-
  determined MAC Address is required - ie. when doing network
  configuration via DHCP.

  ---uname output---
  Ubuntu 18.04 / vmlinuz-4.15.0-101-generic

  Machine Type = IBM z14 GA2

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   - Bring up a qeth L2 OSD interface in DPM-managed LPAR.
  - Inspect the interface's MAC Address. It should be the same as displayed in 
the DPM Panels.

  Stack trace output:
   no

  Oops output:
   no

  System Dump Info:
    The system is not configured to capture a system dump.

  -Attach sysctl -a output output to the bug.

  Backport of "s390/qeth: improve fallback to random MAC address"

  Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices"

  This ticket is for 18.04 only. Already available with 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1880834/+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 1878296] Re: rtl8723bu wifi issue after being turned off

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

** Tags added: verification-needed-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/1878296

Title:
  rtl8723bu wifi issue after being turned off

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  With the rtl8723bu Wi-Fi/Bluetooth combo adapter, if the wifi is turned
  off and then turned on again under the circumstance that a Bluetooth
  device was paired previously, the system can't connect to a wireless
  network until the system is rebooted.

  [Fix]
  Commit e542e66b7c2e("rtl8xxxu: add bluetooth co-existence support for
  single antenna"), which landed v5.5 and as its subject suggests, support
  bluetooth co-existence for RTL8723BU and fixes WiFi disconnection
  problem when Bluetooth is in action.

  Commit a9bb0b515778("rtl8xxxu: Improve TX performance of RTL8723BU on
  rtl8xxxu driver") was added as a prerequisite to aforementioned fix.

  Commit 4fcef8609132("rtl8xxxu: remove set but not used variable
  'rate_mask'") and commit eac08515d7bd("rtl8xxxu: Remove set but not used
  variable 'vif','dev','len'") are included as minor fixes to previous
  commits.

  [Test Case]
  1. Turn on Wi-Fi and get associated with some AP.
  2. Pair some bluetooth device.
  3. Turn off Wi-Fi and turn again.
  4. Expect Wi-Fi reconnects to the previous associated AP.

  [Regression Potential]
  Low. Both commits only affect RTL8723BU.

  == Original Bug Description ==

  With the rtl8723bu wireless adapter, if the wifi is turned off and then 
turned on again, the system can't connect to a wireless network until the 
system is rebooted.
  The issue is not upstream. With mainline kernel and in other distros, 
everything works fine.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user 1384 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 19:02:49 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15

[Kernel-packages] [Bug 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+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 1878296] Re: rtl8723bu wifi issue after being turned off

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  rtl8723bu wifi issue after being turned off

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  With the rtl8723bu Wi-Fi/Bluetooth combo adapter, if the wifi is turned
  off and then turned on again under the circumstance that a Bluetooth
  device was paired previously, the system can't connect to a wireless
  network until the system is rebooted.

  [Fix]
  Commit e542e66b7c2e("rtl8xxxu: add bluetooth co-existence support for
  single antenna"), which landed v5.5 and as its subject suggests, support
  bluetooth co-existence for RTL8723BU and fixes WiFi disconnection
  problem when Bluetooth is in action.

  Commit a9bb0b515778("rtl8xxxu: Improve TX performance of RTL8723BU on
  rtl8xxxu driver") was added as a prerequisite to aforementioned fix.

  Commit 4fcef8609132("rtl8xxxu: remove set but not used variable
  'rate_mask'") and commit eac08515d7bd("rtl8xxxu: Remove set but not used
  variable 'vif','dev','len'") are included as minor fixes to previous
  commits.

  [Test Case]
  1. Turn on Wi-Fi and get associated with some AP.
  2. Pair some bluetooth device.
  3. Turn off Wi-Fi and turn again.
  4. Expect Wi-Fi reconnects to the previous associated AP.

  [Regression Potential]
  Low. Both commits only affect RTL8723BU.

  == Original Bug Description ==

  With the rtl8723bu wireless adapter, if the wifi is turned off and then 
turned on again, the system can't connect to a wireless network until the 
system is rebooted.
  The issue is not upstream. With mainline kernel and in other distros, 
everything works fine.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user 1384 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 19:02:49 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnolog

[Kernel-packages] [Bug 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Performing function level reset of AMD onboard USB and audio devices
  causes system lockup

Status in linux package in Ubuntu:
  In Progress
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:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
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:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justifcation]

  [Impact]

  Devices affected:

  * [1022:148c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Starship
USB 3.0 Host Controller
  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse
USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller

  Despite advertising FLReset device capabilities, performing a function level
  reset of either of these devices causes the system to lock up. This is of
  particular issue where these devices appear in their own IOMMU groups and are
  well suited to VFIO passthrough.

  Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode
  update, and affects dozens of motherboard models across various vendors.

  Additional discussion of this issue:
  
https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/

  [Fix]

  Two commits currently landed in linux-pci pci/virutualization:
  * 0d14f06cd665 PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0
  * 5727043c73fd PCI: Avoid FLR for AMD Starship USB 3.0

  [Test Case]

  Peform the test on an impacted system:

  * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4
socket);
  * Ryzen 3000-series CPU (2000-series possibly also affected);
  * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check
vendor release notes)

  In the above case where ':10:00.3' is the USB controller '1022:149c', 
issue
  a reset command:

$ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset

  Impacted systems will not return successfully and become unstable, requiring a
  reboot. `/var/logs/syslog` will show something resembling the following:

xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting
xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting
xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting
xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting
xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting
xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting
xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up
clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as 
unstable because the skew is too large:
clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: 
clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: 

tsc: Marking TSC unstable due to clocksource watchdog
TSC found unstable after boot, most likely due to broken BIOS. Use 
'tsc=unstable'.
sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, 
-2209419)

  [Regression Risk]
  Low. These two patches affect only systems with a device needs fix.

  == Original Bug Description ==

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  [Impact]

  Devices affected:

  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse HD Au

[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1867900

Title:
  CPU stress test fails with focal kernel

Status in kunpeng920:
  Incomplete
Status in kunpeng920 ubuntu-18.04-hwe series:
  Incomplete
Status in kunpeng920 ubuntu-20.04 series:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  We have several crypto accelerators for Hisilicon 1620 but unfortunately one 
of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 
makes kernel to run crypto functions without accelerator.

  [Fix]
  Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver.

  [Test]
  $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz 
--times --af-alg 0
  $ echo $?

  [Regression Potential]
  This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other 
platform.

  ==
  [Bug Description]
  CPU stress test fails with focal kernel

  [Steps to Reproduce]
  1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable
  2) sudo apt-add-repository -y ppa:hardware-certification/public
  3) sudo apt install -y canonical-certification-server
  4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux
  5) Run CPU stress test with `sudo certify-advanced`

  [Actual Results]
  Failed with
  stress-ng: fail:  [6118] stress-ng-af-alg: bind failed, errno=19 (No such 
device)

  [Expected Results]
  Passed

  [Reproducibility]
  100%

  [Additional information]
  Same test with bionic-update kernel passed

  [Resolution]

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

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/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:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Code that is using s390_pci_mmio_write/read system calls on a z15
  (that comes with enhanced PCI load/store instructions), fails with
  "Unable to handle kernel pointer dereference in virtual kernel address
  space".

  * This issue happens if enablement for z15 PCI enhancements is in
  place and where customers run workloads which access PCI adapters from
  user space, like RoCE/RDMA.

  * To solve this, the system call implementation needs to be improved to 
execute the enhanced PCI load/store instructions on behalf of the user space 
application,
    making use of the mappings into its virtual address space.

  [Fix]

  * f058599e22d59e594e5aae1dc10560568d8f4a8b f058599e22d5 "s390/pci: Fix
  s390_mmio_read/write with MIO"

  [Test Case]

  * Setting up a z15 with at least one PCI card (like RoCE) using an
  operating system that includes support and enablement for z15 (line
  20.04).

  * Install the rdma tools: sudo apt install ibverbs-providers ibverbs-
  utils

  * Verify you have some RDMA devices (requires ConnectX adapter)
    $ ibv_devices
    device node GUID
    -- 
    mlx5_0 98039b0300c682b4

  * Verify MIO instructions are enabled for the device
    $ cat /sys/bus/pci/devices/\:00\:00.0/mio_enabled
    1

  * Try to run an RDMA application from user space, e.g. ibv_rc_pingpong
    server side:
    ibv_rc_pingpong -d mlx5_0 -g 0 &
    client side:
    ibv_rc_pingpong -d mlx5_0 -g 0 localhost

  * Verify whether the kernel crashes or not.

  * Verification needs to be done by IBM on z15 hardware.

  [Regression Potential]

  * There is some regression potential with having code changes in the
  zPCI sub-system (zPCI is limited to s390x)

  * It could be that zPCI hardware get harmed, but zPCI hardware is not
  as wide-spread on s390x than ccw hardware components.

  * Only z15 hardware is affected - no other s390x hardware that is
  supported by Ubuntu.

  * However, the zPCI system is s390x only and the patch was accepted upstream 
with v5.7-rc7 and Linus commented: "And none of the fixes look like there's 
anything particularly scary going on. Most of it is very small, and the 
slightly larger patches aren't huge either and are well-contained (the two 
slightly larger patches are to s390 and rxrpc - and even those patches aren't 
really all _that_ big)"
  __

  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 1878147] Re: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/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:
  In Progress
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:
  In Progress
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:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Existing Wi-Fi connection may be deauthenticated unsolicitedly with
  reason 23=IEEE8021X_FAILED when the system is also paired with a
  Bluetooth device. A WLAN passphrase dialog propmpts, and system
  disconnects from network:

wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason:
  23=IEEE8021X_FAILED).

  [Fix]
  Realtek proposed a fix[1] to linux-wireless consisting of three patches.

rtw88: coex: 8723d: set antanna control owner
rtw88: coex: 8723d: handle BT inquiry cases
rtw88: fix EAPOL 4-way failure by finish IQK earlier

  The third one actually duplicates the fix we have for bug 1871300 also
  from Realtek and was claimed critical to this issue, therefore those for
  bug 1871300 are reverted in favor of the new one.

  Also revert that Ubuntu sauced "rtw88: 8723d: Add coex support" commit
  and replace it with the upstream one due to dependency to bt coex
  functionality.

  [1]: https://lore.kernel.org/linux-
  wireless/20200518081444.7664-1-yhchu...@realtek.com/

  [Test Case]
  1. Associate to a WLAN,
  2. Pair with some Bluetooth device, e.g. headset,
  3. Run a stress test script to disconnect and reconnect Wi-Fi for 200
 runs,
  4. Make sure Wi-Fi passphrase dialog doesn't prompt at the end of the
 test.

  [Regression Potential]
  Low. These changes are mostly about rtl8723de or 11n, which is also for
  8723de.

  == Original Bug Description ==

  Existing Wi-Fi connection may be deauthenticated unsolicitedly with
  reason 23=IEEE8021X_FAILED when the system is also paired with a
  Bluetooth device. A WLAN passphrase dialog propmpts, and system
  disconnects from network leaving an error message in syslog:

    [ 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

[Kernel-packages] [Bug 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Slow send speed with Intel I219-V on Ubuntu 18.04.1

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
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:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  The throughput measured by iperf3 is around 70% of 1Gbps (Intel I219-LM
  [8086:15b7])
  I219 is a rather cheap NIC and it impacts its throughput if TSO(TCP
  segmentation offload) is enabled.  
  
  [Fix]   
  Disable TSO on NIC and move this task back to CPU fixes this issue.
  The impact of CPU loading is little to none.
  On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU
  usage of iperf3 increases from 1% to 4%
  
  [Verify]
  Origin
  [ ID] Interval Transfer Bandwidth Retr
  [ 4] 0.00-10.00 sec 918 MBytes 770 Mbits/sec 0 sender
  [ 4] 0.00-10.00 sec 916 MBytes 769 Mbits/sec receiver

  Becomes
  [ ID] Interval Transfer Bandwidth Retr
  [ 4] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 0 sender
  [ 4] 0.00-10.00 sec 1.09 GBytes 934 Mbits/sec receiver

  [Regression Potential]
  Low, disable TSO on Ethernet chip will move the TCP segmentation task
  to CPU. This increase CPU loading a little bit, and should not introduce
  any regression. 

  =

  Testing with iperf3 send speed is only 750mbps while receive speed is
  normal - 940mbps.

  Ubuntu 18.04.1
  Msi b250m mortar
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  django 1016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp0s31f6  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A69
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M MORTAR ARCTIC (MS-7A69)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A69
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1802691/+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 1879327] Re: Enforce all config annotations

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1879327

Title:
  Enforce all config annotations

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

Bug description:
  [Impact]
  Not all config annotations are enforced, which means config could regress 
without notice.

  [Test case]
  Check the logs mention much more options being enforced. From the hundreds to 
more than 1.

  [Regression potential]
  Builds will start failing when config doesn't match annotations. However, 
this is an opt-in for now, which means only those branches prepared to accept 
it will risk such regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879327/+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 1874056] Re: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1874056

Title:
  [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Mellanox CX5 port multi-pathing is broken on s390x due to non-
  standard topology of PCI IDs (phys. and virtual)

  * The Mellanox Connect-X 5 PCI driver (mlx5) implements multi-path
  that can be used to combine multiple networking ports to improve
  performance and reliability.

  * For that purpose, the mlx5 driver combines PCI functions based on
  topology information (the function number) as determined by their PCI
  ID.

  * Currently the Linux on Z PCI bus does not reflect PCI topology
  information in the PCI ID. As a result, the mlx5 multi-path function
  is broken and cannot be activated.

  [Fix]

  * Backport 1: https://launchpadlibrarian.net/479699471/0001-s390-pci-
  Improve-handling-of-unset-UID.patch

  * Backport 2: https://launchpadlibrarian.net/479699482/0002-s390-pci-
  embedding-hotplug_slot-in-zdev.patch

  * Backport 3: https://launchpadlibrarian.net/479699492/0003-s390-pci-
  Expose-new-port-attribute-for-PCIe-function.patch

  * Backport 4: https://launchpadlibrarian.net/479699497/0004-s390-pci-
  adaptation-of-iommu-to-multifunction.patch

  * Backport 5: https://launchpadlibrarian.net/479700706/0005-s390-pci-
  define-kernel-parameters-for-PCI-multifunct.patch

  * Backport 6: https://launchpadlibrarian.net/479700712/0006-s390-pci-
  define-RID-and-RID-available.patch

  * Backport 7: https://launchpadlibrarian.net/479700739/0007-s390-pci-
  create-zPCI-bus.patch

  * Backport 8: https://launchpadlibrarian.net/479700769/0008-s390-pci-
  adapt-events-for-zbus.patch

  * Backport 9: https://launchpadlibrarian.net/479700786/0009-s390-pci-
  Handling-multifunctions.patch

  * Backport 10: https://launchpadlibrarian.net/479700794/0010-s390-pci-
  Do-not-disable-PF-when-VFs-exist.patch

  * Backport 11: https://launchpadlibrarian.net/479700798/0011-s390-pci-
  Documentation-for-zPCI.patch

  * Backport 12: https://launchpadlibrarian.net/479700799/0012-s390-pci-
  removes-wrong-PCI-multifunction-assignment.patch

  [Test Case]

  * Prepare an IBM z13 or LinuxONE III (or newer) system with two or
  more RoCE Express PCI 2(.1) adapters.

  * Assign the adapters (and it's virtual functions) to an LPAR.

  * Verify whether the physical and virtual functions are grouped in
  arbitrary order or in consecutive order - physical first (for example
  with lspci -t ...)

  [Regression Potential]

  * The regression potential can be considered as moderate, since:

  * It is purely s390x specific code (arch/s390/*
  drivers/iommu/s390-iommu.c and drivers/pci/hotplug/s390_pci_hpc.c -
  and some doc adjustments, too).

  * It largely affects zPCI, the s390x specific PCI code layer.

  * PCI cards available for s390x are optional cards (RoCE and zEDC) and
  not very wide-spread.

  * The situation described above affects the RoCE adapters only
  (Mellanox based).

  * The patches are also upstream accepted and available via linux-next,
  but to apply them to focal kernel 5.4 the above backports are needed.

  * However, the code is modified by several patches (12), hence there
  is a chance to break zPCI with them.

  * For upfront testing a PPA got created with a focal (master-next)
  kernel that incl. all the above patches.

  __

  Today, the enumeration of PCI functions on s390x does not reflect
  which functions belongs to which physical adapter.

  Layout of a PCI function address on Linux:
  :00:00.0
  ::.

  On s390x, each function is presented as individual root complex today,
  e.g.:

  PCHID 0100 VF1 :00:00.0
  PCHID 0100 VF23 0001:00:00.0
  PCHID 0200 VF1 0002:00:00.0
  OCHID 0100 VF17 0003:00:00.0

  On other platforms, the addresses correctly reflect the actual HW
  configuration. Some device drivers (mlx5 for Mellanox adapters) group
  functions of one physical adapter by checking which PCI functions have
  identical values for ::. We need to use the
  same enumeration sc

[Kernel-packages] [Bug 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

** Tags added: verification-needed-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/1865988

Title:
  Performing function level reset of AMD onboard USB and audio devices
  causes system lockup

Status in linux package in Ubuntu:
  In Progress
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:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
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:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justifcation]

  [Impact]

  Devices affected:

  * [1022:148c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Starship
USB 3.0 Host Controller
  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse
USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller

  Despite advertising FLReset device capabilities, performing a function level
  reset of either of these devices causes the system to lock up. This is of
  particular issue where these devices appear in their own IOMMU groups and are
  well suited to VFIO passthrough.

  Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode
  update, and affects dozens of motherboard models across various vendors.

  Additional discussion of this issue:
  
https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/

  [Fix]

  Two commits currently landed in linux-pci pci/virutualization:
  * 0d14f06cd665 PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0
  * 5727043c73fd PCI: Avoid FLR for AMD Starship USB 3.0

  [Test Case]

  Peform the test on an impacted system:

  * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4
socket);
  * Ryzen 3000-series CPU (2000-series possibly also affected);
  * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check
vendor release notes)

  In the above case where ':10:00.3' is the USB controller '1022:149c', 
issue
  a reset command:

$ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset

  Impacted systems will not return successfully and become unstable, requiring a
  reboot. `/var/logs/syslog` will show something resembling the following:

xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting
xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting
xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting
xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting
xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting
xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting
xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up
clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as 
unstable because the skew is too large:
clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: 
clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: 

tsc: Marking TSC unstable due to clocksource watchdog
TSC found unstable after boot, most likely due to broken BIOS. Use 
'tsc=unstable'.
sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, 
-2209419)

  [Regression Risk]
  Low. These two patches affect only systems with a device needs fix.

  == Original Bug Description ==

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  [Impact]

  Devices affected:

  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro

[Kernel-packages] [Bug 1881576] Re: seccomp_benchmark times out on eoan

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  seccomp_benchmark times out on eoan

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  seccomp selftests will timeout, causing the test to be detected as failure.

  [Fix]
  Set timeout to 90s.

  [Test case]
  Run sudo make run_tests under tools/testing/selftests/seccomp/.

  [Regression potential]
  Minimal, the test could still timeout, but by reading the code, it should 
take around 42s to 50s to execute in the worst cases, so 90s seem safe enough.

  ==

  
  As it tries to calibrate how many samples will take more than 5 seconds to 
execute, it may end up picking up a number of samples that take 10 (but up to 
12) seconds. As the calibration will take double that time, it takes around 20 
seconds. Then, it executes the whole thing again, and then once more, with some 
added overhead. So, the thing might take more than 40 seconds, which is too 
close to the 45s timeout.

  So, it times out once in a while depending on the system. Using a
  timeout of 90 seconds should be safe enough for this test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+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 1881046] Re: ASoC/amd: add audio driver for amd renoir

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1881046

Title:
  ASoC/amd: add audio driver for amd renoir

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete

Bug description:
  This patchset is for mainline kernel-5.8, after backporting to 5.6,
  there is no need to change anything, but after backporting to 5.4
  kernel, because of API differences, need to do some change to adapt
  to 5.4 kernel's API. So there is one more patch for focal than for
  oem-5.6.

  [Impact]
  We have a couple of LENOVO machines which has amd renoir audio on
  them, our kernel doesn't have the driver for it yet.

  [Fix]
  amd just upstreamed the driver, it is for kernel-5.8, we backport
  them to ubunt kernel.

  [Test Case]
  boot the kernel with those patches, we could see a sound card named
  "acp" and the dmic on it could record sound via arecord.

  [Regression Risk]
  Low, just adding a new driver, no change to existing drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1881046/+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 1880656] Re: Fix incorrect speed/duplex when I210 device is runtime suspended

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1880656

Title:
  Fix incorrect speed/duplex when I210 device is runtime suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  When I210 device is runtime suspended, trying to read speed or duplex from 
sysfs causes an error:
  [  385.991957] igb :03:00.0 enp3s0: PCIe link lost

  [Fix]
  Only try to read the device register when it's not runtime suspended.

  [Test]
  Without the fix:
  $ cat /sys/class/net/enp3s0/speed
  1000

  With the fix:
  $ cat /sys/class/net/enp3s0/speed
  -1

  -1 means "unknown speed", which is the correct status when device is
  runtime suspend.

  [Regression Potential]
  Low. It's a trivial fix which limits to one driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1880656/+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 1880660] Re: security: lockdown: remove trailing semicolon before function body

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1880660

Title:
  security: lockdown: remove trailing semicolon before function body

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  In focal commit 40fc208c8aae ("UBUNTU: SAUCE: (lockdown) security:
  lockdown: expose a hook to lock the kernel down") adds an inline
  function with a trailing semicolon before the function body, that can
  potentially cause build errors.

  [Test case]

  Build anything that includes linux/security.h and check for
  warnings/errors.

  [Fix]

  Fix by removing the trailing semicolon.

  [Regression potential]

  The problem is an obvious syntax error, fix is trivial, so regression
  potential is minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880660/+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 1879688] Re: shiftfs: fix btrfs snapshot deletion

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  shiftfs: fix btrfs snapshot deletion

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  SRU Justification

  Impact: Stéphane discovered a problem during NorthSec which makes
  heavy use of shiftfs. In containers with a btrfs root filesystem that
  make use of shiftfs userns root is not able to delete subvolumes that
  have been created by another users which it would be able to do
  otherwise. This makes it impossible for LXD to delete nested
  containers.

  To reproduce this as root in the container:
  btrfs subvolume create my-subvol
  chown 1000:1000 my-subvol
  btrfs subvolume delete my-subvol

  The deletion will fail when it should have succeeded.

  Fix: For improved security we drop all capabilities before we forward
  btrfs ioctls in shiftfs. To fix the above problem we can retain the
  CAP_DAC_OVERRIDE capability only if we are userns root.

  Regression Potential: Limited to shiftfs. Even though we drop all
  capabilities in all capability sets we really mostly care about
  dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow
  you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained
  in the underlay would allow you to list subvolumes you shouldn't be
  able to list. This fix only retains CAP_DAC_OVERRIDE and only for the
  deletion of subvolumes and only by userns root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879688/+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 1878296] Re: rtl8723bu wifi issue after being turned off

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  rtl8723bu wifi issue after being turned off

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  With the rtl8723bu Wi-Fi/Bluetooth combo adapter, if the wifi is turned
  off and then turned on again under the circumstance that a Bluetooth
  device was paired previously, the system can't connect to a wireless
  network until the system is rebooted.

  [Fix]
  Commit e542e66b7c2e("rtl8xxxu: add bluetooth co-existence support for
  single antenna"), which landed v5.5 and as its subject suggests, support
  bluetooth co-existence for RTL8723BU and fixes WiFi disconnection
  problem when Bluetooth is in action.

  Commit a9bb0b515778("rtl8xxxu: Improve TX performance of RTL8723BU on
  rtl8xxxu driver") was added as a prerequisite to aforementioned fix.

  Commit 4fcef8609132("rtl8xxxu: remove set but not used variable
  'rate_mask'") and commit eac08515d7bd("rtl8xxxu: Remove set but not used
  variable 'vif','dev','len'") are included as minor fixes to previous
  commits.

  [Test Case]
  1. Turn on Wi-Fi and get associated with some AP.
  2. Pair some bluetooth device.
  3. Turn off Wi-Fi and turn again.
  4. Expect Wi-Fi reconnects to the previous associated AP.

  [Regression Potential]
  Low. Both commits only affect RTL8723BU.

  == Original Bug Description ==

  With the rtl8723bu wireless adapter, if the wifi is turned off and then 
turned on again, the system can't connect to a wireless network until the 
system is rebooted.
  The issue is not upstream. With mainline kernel and in other distros, 
everything works fine.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user 1384 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 19:02:49 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTob

[Kernel-packages] [Bug 1879688] Re: shiftfs: fix btrfs snapshot deletion

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

** Tags added: verification-needed-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/1879688

Title:
  shiftfs: fix btrfs snapshot deletion

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  SRU Justification

  Impact: Stéphane discovered a problem during NorthSec which makes
  heavy use of shiftfs. In containers with a btrfs root filesystem that
  make use of shiftfs userns root is not able to delete subvolumes that
  have been created by another users which it would be able to do
  otherwise. This makes it impossible for LXD to delete nested
  containers.

  To reproduce this as root in the container:
  btrfs subvolume create my-subvol
  chown 1000:1000 my-subvol
  btrfs subvolume delete my-subvol

  The deletion will fail when it should have succeeded.

  Fix: For improved security we drop all capabilities before we forward
  btrfs ioctls in shiftfs. To fix the above problem we can retain the
  CAP_DAC_OVERRIDE capability only if we are userns root.

  Regression Potential: Limited to shiftfs. Even though we drop all
  capabilities in all capability sets we really mostly care about
  dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow
  you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained
  in the underlay would allow you to list subvolumes you shouldn't be
  able to list. This fix only retains CAP_DAC_OVERRIDE and only for the
  deletion of subvolumes and only by userns root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879688/+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 1879658] Re: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Cannot create ipvlans with > 1500 MTU on recent Bionic kernels

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

Bug description:
  [IMPACT]

  Setting an MTU larger than the default 1500 results in an
  error on the recent (4.15.0-92+) Bionic/Xenial -hwe kernels
  when attempting to create ipvlan interfaces:

  # ip link add test0 mtu 9000 link eno1 type ipvlan mode l2
  RTNETLINK answers: Invalid argument

  This breaks Docker and other applications which use a Jumbo
  MTU (9000) when using ipvlans.

  The bug is caused by the following recent commit to Bionic
  & Xenial-hwe; which is pulled in via the stable patchset below,
  which enforces a strict min/max MTU when MTUs are being set up
  via rtnetlink for ipvlans:

  Breaking commit:
  ---
  Ubuntu-hwe-4.15.0-92.93~16.04.1
  * Bionic update: upstream stable patchset 2020-02-21 (LP: #1864261)
    * net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link()

  The above patch applies checks of dev->min_mtu and dev->max_mtu
  to avoid a malicious user from crashing the kernel with a bad
  value. It was patching the original patchset to centralize min/max
  MTU checking from various different subsystems of the networking
  kernel. However, in that patchset, the max_mtu had not been set
  to the largest phys (64K) or jumbo (9000 bytes), and defaults to
  1500. The recent commit above which enforces strict bounds checking
  for MTU size exposes the bug of the max mtu not being set correctly
  for the ipvlan driver (this has been previously fixed in bonding,
  teaming drivers).

  Fix:
  ---
  This was fixed in the upstream kernel as of v4.18-rc2 for ipvlans,
  but was not backported to Bionic along with other patches. The missing commit 
in the Bionic backport:

  ipvlan: use ETH_MAX_MTU as max mtu
  commit 548feb33c598dfaf9f8e066b842441ac49b84a8a

  [Test Case]

  1. Install any kernel earlier than 4.15.0-92 (Bionic/Xenial-hwe)

  2. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2
     (where test1 eno1 is the physical interface you are adding
  the ipvlan on)

  3. # ip link
  ...
  14: test1@eno1:  mtu 9000 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
  ...
    // check that your test1 ipvlan is created with mtu 9000

  4. Install 4.15.0-92 kernel or later

  5. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2
  RTNETLINK answers: Invalid argument

  6. With the above fix commit backported to the xenial-hwe/Bionic,
  the jumbo mtu ipvlan creation works again, identical to before 92.

  [Regression Potential]

  This commit is in upstream mainline as of v4.18-rc2, and hence
  is already in Cosmic and later, i.e. all post Bionic releases
  currently. Hence there's low regression potential here.

  It only impacts ipvlan functionality, and not other networking
  systems, so core systems should not be affected by this. And
  affects on setup so it either works or doesn't. Patch is trivial.

  It only impacts Bionic/Xenial-hwe 4.15.0-92 onwards versions
  (where the latent bug got exposed).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879658/+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 1879704] Re: [UBUNTU 20.04] s390x/pci: fix linking between PF and VF for multifunction devices

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1879704

Title:
  [UBUNTU 20.04] s390x/pci: fix linking between PF and VF for
  multifunction devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * It's currently not possible on s390x to verify the relationships
  between PFs and VFs of network interfaces (neither natively nor in
  libvirt).

  * So s390x currently behaves differently here compared to other
  architectures, but shouldn't, since this is needed for proper
  management.

  * The creation of not only the sysfs, but also the in-kernel link
  (struct pci_dev->physfn), solves this and on top allows the use of a
  common code path for disabling/shutdown of PFs.

  * This code path is right now fenced off by the struct
  pci_dev->no_vf_scan flag of which s390x is currently the only user.

  * This allows to gracefully and orderly shutdown VFs associated with a
  PF as triggered by '/sys/bus/pci/devices//sriov_numvfs'

  * Previously this could leave the card in an unresponsive error state.

  [Fix]

  * a1ceea67f2e5b73cebd456e7fb463b3052bc6344 a1ceea67f2e5 "PCI/IOV:
  Introduce pci_iov_sysfs_link() function"

  * e5794cf1a270d813a5b9373a6876487d4d154195 e5794cf1a270 "s390/pci:
  create links between PFs and VFs"

  [Test Case]

  * Setup an s390x LPAR with at least one SR-IOV card and assign PF and
  VFs to that system.

  * Determine if a device is a virtual function: for other architectures
  this is currently available in the file 'physfn' which is a link to
  the parent PF's device.

  * Determine virtual functions of a physical function: for other
  architectures this is currently available as 'virtfn{index}' links
  under the PF device's directory.

  * Determine the physical function of a virtual function: on x86 this
  is currently available in the file 'physfn' which is a link to the
  parent PF.

  * This verification needs to be done by IBM on a system with SR-IOV
  (PCI-based) hardware.

  [Regression Potential]

  * There is a certain regression risk with having code changes in the PCI/IOV 
space,
    even is they are limited, especially is the patches touche common code.

  * The changes in pci.h are very minimal, and the iov.c changes are
  traceable, too. All other modifications are s390x specific.

  * Nevertheless, it could be that PCI hardware get harmed, here
  especially (SR-)IOV hardware.

  * The patches got cross-company verified (IBM and Google).

  * They were brought upstream and are currently tagged with 20200521,
  and are planned to be included in 5.8.

  * A patched kernel was created based on a LP PPA and successfully
  tested by IBM.

  [Other]

  * Since the fix/patch is planned to be included in kernel v5.8, it
  will later automatically land in groovy.

  * But because groovy is not there yet (5.8 is not yet out), this SRU
  got requested for focal and groovy.

  * This SRU depends on the SRU from LP 1874056, and this has already two ACKs.
    So LP 1874056 needs to be applied before this one!
  __

  As with other architectures, we must be able on s390x to verify the
  following relationships between PFs and VFs for proper management
  (including by libvirt) of network interfaces:

  1. Determine if a device is a virtual function: for other architectures this 
is currently available in the file `physfn` which is a link to the parent PF's 
device.
  2. Determine virtual functions of a physical function: for other 
architectures this is currently available as `virtfn{index}` links under the PF 
device's directory.
  3. Determine the physical function of a virtual function: on x86 this is 
currently available in the file `physfn` which is a link to the parent PF

  More details for the already existing parameters mentioned above can
  be found here: https://www.kernel.org/doc/Documentation/ABI/testing
  /sysfs-bus-pci

  Moreover creating not just the sysfs but also the in-kernel link
  (struct pci_dev->physfn) also allows us to use the common code path
  for disabling/shutdown of PFs

[Kernel-packages] [Bug 1881576] Re: seccomp_benchmark times out on eoan

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

** Tags added: verification-needed-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/1881576

Title:
  seccomp_benchmark times out on eoan

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  seccomp selftests will timeout, causing the test to be detected as failure.

  [Fix]
  Set timeout to 90s.

  [Test case]
  Run sudo make run_tests under tools/testing/selftests/seccomp/.

  [Regression potential]
  Minimal, the test could still timeout, but by reading the code, it should 
take around 42s to 50s to execute in the worst cases, so 90s seem safe enough.

  ==

  
  As it tries to calibrate how many samples will take more than 5 seconds to 
execute, it may end up picking up a number of samples that take 10 (but up to 
12) seconds. As the calibration will take double that time, it takes around 20 
seconds. Then, it executes the whole thing again, and then once more, with some 
added overhead. So, the thing might take more than 40 seconds, which is too 
close to the 45s timeout.

  So, it times out once in a while depending on the system. Using a
  timeout of 90 seconds should be safe enough for this test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+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 1881710] Re: tpm: fix TIS locality timeout problems

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1881710

Title:
  tpm: fix TIS locality timeout problems

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  [Impact]
  It has been reported that some TIS based TPMs are giving unexpected errors 
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs 
don't like it when you get and then relinquish a locality (as the 
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This 
currently happens all the time in the O_NONBLOCK write path. This affects 
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix 
invalid locking in NONBLOCKING mode").
  PatchLink: https://patchwork.kernel.org/patch/11576453/

  [Fix]
  Fix this by moving the tpm_try_get_ops()
  further down the code to after the O_NONBLOCK determination is made.
  This is safe because the priv->buffer_mutex still protects the priv
  state being modified.

  [Regression Risk]
  Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid 
locking in NONBLOCKING mode").

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+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 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

[AlekseyK]

Now freezes after cover open as well, so not solved at all!

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882917/+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 1882992] [NEW] Upon update te 5.4.0-37-generic, boot hangs with black screen

[Rob Frohne]

Public bug reported:

Upon updating to linux-5.p.0-37 this morning, it asked me to restart,
and when it did, all I had was a black screen.  I could see the power
was on, because the power led was lit.  I rebooted a couple times with
the same result.  Then rebooted to single user, did fsck, repair broken
packages, and rebooted, and it came up, but not using both monitors.  So
I did another update of the packages, and rebooted.  It was still black.
I ended up rebooting on the previous kernel, and it works now, and I'm
submitting this bug report using that setup.  If it would be helpful, I
can reboot single user, and eventually get it up with only the laptop
monitor, and submit a ubuntu-bug report that way too.

Thanks for your great work on Ubuntu!

Rob

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-37-generic 5.4.0-37.41
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  frohro 1939 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 10:30:41 2020
InstallationDate: Installed on 2019-04-19 (418 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
MachineType: LENOVO 20FES0EX00
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-33-generic 
root=/dev/mapper/ubuntu--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-33-generic N/A
 linux-backports-modules-5.4.0-33-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET91W (1.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FES0EX00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad Yoga 260
dmi.product.name: 20FES0EX00
dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
dmi.product.version: ThinkPad Yoga 260
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Upon update te 5.4.0-37-generic, boot hangs with black screen

Status in linux package in Ubuntu:
  New

Bug description:
  Upon updating to linux-5.p.0-37 this morning, it asked me to restart,
  and when it did, all I had was a black screen.  I could see the power
  was on, because the power led was lit.  I rebooted a couple times with
  the same result.  Then rebooted to single user, did fsck, repair
  broken packages, and rebooted, and it came up, but not using both
  monitors.  So I did another update of the packages, and rebooted.  It
  was still black.  I ended up rebooting on the previous kernel, and it
  works now, and I'm submitting this bug report using that setup.  If it
  would be helpful, I can reboot single user, and eventually get it up
  with only the laptop monitor, and submit a ubuntu-bug report that way
  too.

  Thanks for your great work on Ubuntu!

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frohro 1939 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 10:30:41 2020
  InstallationDate: Installed on 2019-04-19 (418 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  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-33-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.boa

[Kernel-packages] [Bug 1882995] [NEW] package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned

[arindam]

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

Public bug reported:

can't uninstall the above kernel

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs bnep btusb btrtl btbcm 
btintel bluetooth snd_hda_codec_hdmi snd_hda_codec_realtek nouveau 
snd_hda_codec_generic ledtrig_audio ath5k mxm_wmi ath mac80211 uvcvideo 
videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_hda_intel 
videobuf2_common snd_intel_dspcfg acer_wmi k10temp snd_hda_codec sparse_keymap 
snd_hda_core mac_hid videodev mc ums_realtek pata_acpi wmi i2c_nforce2
ApportVersion: 2.20.11-0ubuntu27.2
AptOrdering:
 linux-image-5.4.0-33-generic:amd64: Remove
 linux-modules-5.4.0-33-generic:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  arindam1592 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Jun 10 23:03:54 2020
DpkgTerminalLog:
 Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ...
 E: Aborting removal of the running kernel
 dpkg: error processing package linux-image-5.4.0-33-generic (--remove):
  installed linux-image-5.4.0-33-generic package pre-removal script subprocess 
returned error exit status 1
 dpkg: too many errors, stopping
DuplicateSignature:
 package:linux-image-5.4.0-33-generic:5.4.0-33.37
 Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ...
 E: Aborting removal of the running kernel
 dpkg: error processing package linux-image-5.4.0-33-generic (--remove):
  installed linux-image-5.4.0-33-generic package pre-removal script subprocess 
returned error exit status 1
ErrorMessage: installed linux-image-5.4.0-33-generic package pre-removal script 
subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=b8575c3a-feb1-4a9c-a199-23048b250eef
InstallationDate: Installed on 2020-05-02 (38 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Acer, inc. AS4530
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=41800492-cf71-4e29-808c-bd10d3cd8617 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
SourcePackage: linux
Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to 
install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2008
dmi.bios.vendor: Acer
dmi.bios.version: v1.
dmi.board.name: Grasmoor
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrv1.:bd08/15/2008:svnAcer,inc.:pnAS4530:pvrNotApplicable:rvnAcer,Inc.:rnGrasmoor:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: AS4530
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

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


** Tags: amd64 apport-package 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/1882995

Title:
  package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to
  install/upgrade: installed linux-image-5.4.0-33-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  can't uninstall the above kernel

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs bnep btusb btrtl btbcm 
btintel bluetooth snd_hda_codec_hdmi snd_hda_codec_realtek nouveau 
snd_hda_codec_generic ledtrig_audio ath5k mxm_wmi ath mac80211 uvcvideo 
videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_hda_intel 
videobuf2_common snd_intel_dspcfg acer_wmi k10temp snd_hda_codec sparse_keymap 
snd_hda_core mac_hid videodev mc ums_realtek pata_acpi wmi i2c_nforce2
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   linux-image-5.4.0-33-generic:amd64: Remove
   linux-modules-5.4.0-33-generic:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arindam1592 F pulseaudio
  CasperMD5

[Kernel-packages] [Bug 1882995] Re: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned er

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1881951, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1881951
   package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: 
installed linux-image-5.4.0-33-generic package pre-removal script subprocess 
returned error exit status 1

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

Title:
  package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to
  install/upgrade: installed linux-image-5.4.0-33-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  can't uninstall the above kernel

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs bnep btusb btrtl btbcm 
btintel bluetooth snd_hda_codec_hdmi snd_hda_codec_realtek nouveau 
snd_hda_codec_generic ledtrig_audio ath5k mxm_wmi ath mac80211 uvcvideo 
videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_hda_intel 
videobuf2_common snd_intel_dspcfg acer_wmi k10temp snd_hda_codec sparse_keymap 
snd_hda_core mac_hid videodev mc ums_realtek pata_acpi wmi i2c_nforce2
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   linux-image-5.4.0-33-generic:amd64: Remove
   linux-modules-5.4.0-33-generic:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arindam1592 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 23:03:54 2020
  DpkgTerminalLog:
   Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-5.4.0-33-generic (--remove):
installed linux-image-5.4.0-33-generic package pre-removal script 
subprocess returned error exit status 1
   dpkg: too many errors, stopping
  DuplicateSignature:
   package:linux-image-5.4.0-33-generic:5.4.0-33.37
   Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-5.4.0-33-generic (--remove):
installed linux-image-5.4.0-33-generic package pre-removal script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-5.4.0-33-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=b8575c3a-feb1-4a9c-a199-23048b250eef
  InstallationDate: Installed on 2020-05-02 (38 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer, inc. AS4530
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=41800492-cf71-4e29-808c-bd10d3cd8617 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to 
install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.
  dmi.board.name: Grasmoor
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.:bd08/15/2008:svnAcer,inc.:pnAS4530:pvrNotApplicable:rvnAcer,Inc.:rnGrasmoor:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: AS4530
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Kernel-packages] [Bug 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

[AlekseyK]

No :( helped only partially. When laptop went on suspend by 20 min
timeout it freezes after resume again. So not solved!

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882917/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

[Robert Boerner]

While the system is booted into Linux Mint 19.3 (with audio working
properly), the kernel version is reported as:

Linux NUC8CCHK 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7
13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

(I think the kernel version may have been updated slightly as a result
of an automatic update)

The dmesg log file from the system booting under Linux Mint 19.3 with
that kernel is attached.

Thank you for your continued assistance!

** Attachment added: "Linux_Mint_19_3_dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+attachment/5382512/+files/Linux_Mint_19_3_dmesg.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/1875199

Title:
  [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound output. Only a 'Dummy' audio output device is listed in the
  Gnome Sound application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 12:12:49 2020
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1215 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Intel(R) Client Systems NUC8CCHK
  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-28-generic 
root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-28-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: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems

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

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

Re: [Kernel-packages] [Bug 1876492] Re: keyboard, mouse & touchpad freeze

[Meir Levi]

I may have to replace it with 8GB module
Levi

> On Jun 10, 2020, at 9:07 AM, Meir Levi  wrote:
> 
> 
> Most likely yes. At first I thought some add ons on my Firefox were the 
> culprit but the problem still persists 
> Thanks
> 
>>> On Jun 10, 2020, at 1:31 AM, Kai-Heng Feng <1876...@bugs.launchpad.net> 
>>> wrote:
>>> 
>> This system only has 4GB memory. Did the issue happen under heavy memory
>> pressure?
>> 
>> -- 
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1876492
>> 
>> Title:
>>  keyboard, mouse & touchpad freeze
>> 
>> Status in linux package in Ubuntu:
>>  Confirmed
>> 
>> Bug description:
>>  It happens after wakeup in overnight suspend & few minutes of surfing.
>>  Firefox open
>>  Page: twitter account
>> 
>>  ProblemType: Bug
>>  DistroRelease: Ubuntu 20.04
>>  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
>>  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>>  Uname: Linux 5.4.0-28-generic x86_64
>>  ApportVersion: 2.20.11-0ubuntu27
>>  Architecture: amd64
>>  AudioDevicesInUse:
>>   USERPID ACCESS COMMAND
>>   /dev/snd/controlC1:  user-meir   1408 F pulseaudio
>>   /dev/snd/controlC0:  user-meir   1408 F pulseaudio
>>  CasperMD5CheckResult: skip
>>  CurrentDesktop: X-Cinnamon
>>  Date: Sat May  2 10:13:15 2020
>>  InstallationDate: Installed on 2020-05-01 (0 days ago)
>>  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
>>  MachineType: Dell Inc. Inspiron 3180
>>  ProcFB: 0 amdgpudrmfb
>>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
>> root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
>>  RelatedPackageVersions:
>>   linux-restricted-modules-5.4.0-28-generic N/A
>>   linux-backports-modules-5.4.0-28-generic  N/A
>>   linux-firmware1.187
>>  SourcePackage: linux
>>  UpgradeStatus: No upgrade log present (probably fresh install)
>>  WifiSyslog:
>> 
>>  dmi.bios.date: 03/09/2018
>>  dmi.bios.vendor: Dell Inc.
>>  dmi.bios.version: 1.3.0
>>  dmi.board.name: 0918N8
>>  dmi.board.vendor: Dell Inc.
>>  dmi.board.version: A00
>>  dmi.chassis.type: 10
>>  dmi.chassis.vendor: Dell Inc.
>>  dmi.chassis.version: 1.3.0
>>  dmi.modalias: 
>> dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
>>  dmi.product.family: Inspiron
>>  dmi.product.name: Inspiron 3180
>>  dmi.product.sku: 087E
>>  dmi.product.version: 1.3.0
>>  dmi.sys.vendor: Dell Inc.
>> 
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876492/+subscriptions

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

Title:
  keyboard, mouse & touchpad freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It happens after wakeup in overnight suspend & few minutes of surfing.
  Firefox open
  Page: twitter account

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user-meir   1408 F pulseaudio
   /dev/snd/controlC0:  user-meir   1408 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sat May  2 10:13:15 2020
  InstallationDate: Installed on 2020-05-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  host freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Compaq 6710b 4Gib Ram

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sqladmin   2651 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 10:32:00 2020
  InstallationDate: Installed on 2020-06-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP Compaq 6710b (RM403UT#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a9082c84-0e7e-4d40-9889-70ef9dfc26ef ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.11
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: CNU82810YZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.11:bd04/10/2008:svnHewlett-Packard:pnHPCompaq6710b(RM403UT#ABA):pvrF.11:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b (RM403UT#ABA)
  dmi.product.sku: RM403UT#ABA
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882984/+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 1881821] Re: MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade)

[Alberto Donato]

** Changed in: maas
Milestone: 2.8.0 => 2.9.0b1

** Changed in: maas
   Status: Triaged => Fix Committed

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

Title:
  MAAS does not properly detect max interface speed for interfaces which
  use multiple phyiscal ports(Cisco UCS B200 M5 blade)

Status in MAAS:
  Fix Committed
Status in MAAS 2.7 series:
  Triaged
Status in MAAS 2.8 series:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  MAAS 2.7.1
  Ubuntu 18.04.4

  When attempting to commission a Cisco UCS B200 M5 blade, the
  commissioning finishes (if smartctl-validate is disabled), however on
  the machine in question in the Networking tab, it only shows 2 nics,
  eth0 and eth1.  and shows no storage.

  Going to SSH in the middle of commissioning, running lshw shows all 10
  NICs, and the disk of the proper size.

  This is causing the buckets.yaml for FCE to be inaccurate, and thus
  cannot write a bucketsconfig.yaml since the actual devices don't show
  up.

  This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for
  commissioning, all have the same behavior.

  I was previously hitting this bug
  https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from
  comment #10, and am no longer getting any commissioning errors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+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 1882975] Re: crypttab not found error causes boot failure with changes in zfs-initramfs_0.8.4-1ubuntu5

[satmandu]

I suspect this is due to my not having cryptsetup-initramfs installed.
Without that, cryptroot never gets created.

cryptsetup-initramfs's /usr/share/local-top/cryptroot
has this: mkdir -p /cryptroot # might not exist yet if the main system has no 
crypttab

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

Title:
  crypttab not found error causes boot failure with changes in zfs-
  initramfs_0.8.4-1ubuntu5

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  boot ends before rpool loads with a failure to find the crypttab file,
  which doesn't exist.

  Maybe this has a dependency upon a package that makes that?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu38
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 11:42:55 2020
  InstallationDate: Installed on 2019-10-19 (235 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1882975/+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 1882984] [NEW] host freezes

[Sherman Willden]

Public bug reported:

Compaq 6710b 4Gib Ram

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-37-generic 5.4.0-37.41
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sqladmin   2651 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 10:32:00 2020
InstallationDate: Installed on 2020-06-10 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP Compaq 6710b (RM403UT#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a9082c84-0e7e-4d40-9889-70ef9dfc26ef ro recovery nomodeset
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-37-generic N/A
 linux-backports-modules-5.4.0-37-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.11
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.asset.tag: CNU82810YZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.11:bd04/10/2008:svnHewlett-Packard:pnHPCompaq6710b(RM403UT#ABA):pvrF.11:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP Compaq 6710b (RM403UT#ABA)
dmi.product.sku: RM403UT#ABA
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug focal

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

Title:
  host freezes

Status in linux package in Ubuntu:
  New

Bug description:
  Compaq 6710b 4Gib Ram

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sqladmin   2651 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 10:32:00 2020
  InstallationDate: Installed on 2020-06-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP Compaq 6710b (RM403UT#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=a9082c84-0e7e-4d40-9889-70ef9dfc26ef ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.11
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: CNU82810YZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.11:bd04/10/2008:svnHewlett-Packard:pnHPCompaq6710b(RM403UT#ABA):pvrF.11:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b (RM403UT#ABA)
  dmi.product.sku: RM403UT#ABA
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882984/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Alex Tasin]

for me the two workaround doesn't work

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-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 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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/oem-priority/+bug/1845801/+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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu5

---
zfs-linux (0.8.4-1ubuntu5) groovy; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * debian/patches/4000-zsys-support.patch:
- Readd ZSys support erroneously dropped during previous debian merge.
- Add external Luks store encryption support.
  * debian/patches/git_fix_dependency_loop_encryption{1,2}.patch:
- Backport upstream patches (PR accepted, not merged yet) fixing a
  dependency loop when encryption via Luks (like swap) is enabled.
  (LP: #1875577)

 -- Didier Roche   Wed, 10 Jun 2020 10:48:19 +0200

** Changed in: zfs-linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 control
  root@eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avail
  Mem

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

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

Re: [Kernel-packages] [Bug 1876492] Re: keyboard, mouse & touchpad freeze

[Meir Levi]

Most likely yes. At first I thought some add ons on my Firefox were the culprit 
but the problem still persists 
Thanks

> On Jun 10, 2020, at 1:31 AM, Kai-Heng Feng <1876...@bugs.launchpad.net> wrote:
> 
> This system only has 4GB memory. Did the issue happen under heavy memory
> pressure?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1876492
> 
> Title:
>  keyboard, mouse & touchpad freeze
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  It happens after wakeup in overnight suspend & few minutes of surfing.
>  Firefox open
>  Page: twitter account
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 20.04
>  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
>  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>  Uname: Linux 5.4.0-28-generic x86_64
>  ApportVersion: 2.20.11-0ubuntu27
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC1:  user-meir   1408 F pulseaudio
>   /dev/snd/controlC0:  user-meir   1408 F pulseaudio
>  CasperMD5CheckResult: skip
>  CurrentDesktop: X-Cinnamon
>  Date: Sat May  2 10:13:15 2020
>  InstallationDate: Installed on 2020-05-01 (0 days ago)
>  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
>  MachineType: Dell Inc. Inspiron 3180
>  ProcFB: 0 amdgpudrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
> root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
>  RelatedPackageVersions:
>   linux-restricted-modules-5.4.0-28-generic N/A
>   linux-backports-modules-5.4.0-28-generic  N/A
>   linux-firmware1.187
>  SourcePackage: linux
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  WifiSyslog:
> 
>  dmi.bios.date: 03/09/2018
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: 1.3.0
>  dmi.board.name: 0918N8
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: A00
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Dell Inc.
>  dmi.chassis.version: 1.3.0
>  dmi.modalias: 
> dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
>  dmi.product.family: Inspiron
>  dmi.product.name: Inspiron 3180
>  dmi.product.sku: 087E
>  dmi.product.version: 1.3.0
>  dmi.sys.vendor: Dell Inc.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876492/+subscriptions

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

Title:
  keyboard, mouse & touchpad freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It happens after wakeup in overnight suspend & few minutes of surfing.
  Firefox open
  Page: twitter account

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user-meir   1408 F pulseaudio
   /dev/snd/controlC0:  user-meir   1408 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sat May  2 10:13:15 2020
  InstallationDate: Installed on 2020-05-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=eedc8f40-27b4-4fed-8609-5e17643f30c6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to
  version 4)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently, a couple of patches were upstreamed to Linux to upgrade
  vmxnet3 driver to version 4. Below are the commits:

  vmxnet3: prepare for version 4 changes
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

  vmxnet3: add support to get/set rx flow hash
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

  vmxnet3: add geneve and vxlan tunnel offload support
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

  vmxnet3: update to version 4
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

  vmxnet3: use correct hdr reference when packet is encapsulated
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

  vmxnet3: allow rx flow hash ops only when rss is enabled
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

  This is a request to bring Ubuntu vmxnet3 driver up to date with Linux
  kernel.

  Thanks,
  Yuhua Zou

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

[thedoctar]

apport information

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

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

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

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

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

[thedoctar]

apport information

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

** Description changed:

  Wifi card stopped working. I use Lubuntu 20.04.
  
  Wifi card info:
  
*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f
  
  Releveant journal log attached. In brief,
  
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: LXQt
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-05-11 (29 days ago)
+ InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: linux (not installed)
+ Tags:  focal
+ Uname: Linux 5.6.11-050611-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sudo
+ _MarkForUpload: True

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

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)

[Kernel-packages] [Bug 1882968] ProcCpuinfoMinimal.txt

[thedoctar]

apport information

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

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] Re: ath10k_pci failed to wake target for write32

[thedoctar]

apport information

** Tags added: apport-collected focal

** Description changed:

  Wifi card stopped working. I use Lubuntu 20.04.
  
  Wifi card info:
  
*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f
  
  Releveant journal log attached. In brief,
  
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: LXQt
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-05-11 (29 days ago)
+ InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: linux (not installed)
+ Tags:  focal
+ Uname: Linux 5.6.11-050611-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sudo
+ _MarkForUpload: True

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

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubunt

[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

[Guilherme G. Piccoli]

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1869672

Title:
  Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

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

Bug description:
  [Impact]
  * Kdump kernel can't be loaded using Linux kernel 4.15.0-65 and newer on 
Bionic; kexec fails to load using the "new" kexec_file_load() syscall, showing 
the following messages in dmesg:

  kexec: Undefined symbol: __stack_chk_fail
  kexec-bzImage64: Loading purgatory failed

  * Reason for this was that backport from upstream commit b059f801a937
  ("x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS")
  makes use of a config option guard that wasn't backported to Ubuntu
  4.15.x series.

  * Also, we found another related issue, an undefined memcpy() symbol,
  that was related to the above patch too. We propose here a specific
  fix for Bionic, in the form of the patch attached in comment #18.

  [Test case]

  * Basically the test consists in booting a signed kernel in a secure
  boot environment (this is required given Ubuntu kernel is built with
  CONFIG_KEXEC_VERIFY_SIG so to use kexec_file_load() we must be in a
  proper signed/secure booted system). It works until 4.15.0-64, and
  starts to fail after this release, until the current proposed version
  4.15.0-97. We can also check kdump-tools service in the failing case,
  which shows:

  systemctl status kdump-tools
  [...]
  kdump-tools[895]: Starting kdump-tools: * Creating symlink 
/var/lib/kdump/vmlinuz
  kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img
  kdump-tools[895]: kexec_file_load failed: Exec format error
  kdump-tools[895]: * failed to load kdump kernel
  [...]

  * With the patch attached in the LP, it works normally again and I was
  able to collect a kdump.

  [Regression potential]

  * Given the patch is quite simple and fixes the build of purgatory, I
  think the regression potential is low. One potential regression in
  future would be on backports to purgatory Makefile, making them more
  difficult/prone to errors; given purgatory is a pretty untouchable
  code, I consider the regression potential here to be really low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869672/+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 1882975] [NEW] crypttab not found error causes boot failure with changes in zfs-initramfs_0.8.4-1ubuntu5

[satmandu]

Public bug reported:

boot ends before rpool loads with a failure to find the crypttab file,
which doesn't exist.

Maybe this has a dependency upon a package that makes that?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
Uname: Linux 5.4.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu38
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jun 10 11:42:55 2020
InstallationDate: Installed on 2019-10-19 (235 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy package-from-proposed

** Summary changed:

- crypttab not found error causes boot failure
+ crypttab not found error causes boot failure with new zfs-initramfs

** Summary changed:

- crypttab not found error causes boot failure with new zfs-initramfs
+ crypttab not found error causes boot failure with changes in 
zfs-initramfs_0.8.4-1ubuntu5

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

Title:
  crypttab not found error causes boot failure with changes in zfs-
  initramfs_0.8.4-1ubuntu5

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  boot ends before rpool loads with a failure to find the crypttab file,
  which doesn't exist.

  Maybe this has a dependency upon a package that makes that?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu38
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 11:42:55 2020
  InstallationDate: Installed on 2019-10-19 (235 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1882975/+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 1882893] Re: vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)

[Brian Murray]

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

Title:
  vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to
  version 4)

Status in linux package in Ubuntu:
  New

Bug description:
  Recently, a couple of patches were upstreamed to Linux to upgrade
  vmxnet3 driver to version 4. Below are the commits:

  vmxnet3: prepare for version 4 changes
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

  vmxnet3: add support to get/set rx flow hash
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

  vmxnet3: add geneve and vxlan tunnel offload support
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

  vmxnet3: update to version 4
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

  vmxnet3: use correct hdr reference when packet is encapsulated
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

  vmxnet3: allow rx flow hash ops only when rss is enabled
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

  This is a request to bring Ubuntu vmxnet3 driver up to date with Linux
  kernel.

  Thanks,
  Yuhua Zou

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882893/+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 1882893] [NEW] vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Recently, a couple of patches were upstreamed to Linux to upgrade
vmxnet3 driver to version 4. Below are the commits:

vmxnet3: prepare for version 4 changes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

vmxnet3: add support to get/set rx flow hash
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

vmxnet3: add geneve and vxlan tunnel offload support
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

vmxnet3: update to version 4
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

vmxnet3: use correct hdr reference when packet is encapsulated
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

vmxnet3: allow rx flow hash ops only when rss is enabled
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

This is a request to bring Ubuntu vmxnet3 driver up to date with Linux
kernel.

Thanks,
Yuhua Zou

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


** Tags: bot-comment
-- 
vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)
https://bugs.launchpad.net/bugs/1882893
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 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

[AlekseyK]

BIOS upgrade helped.

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1882968] [NEW] ath10k_pci failed to wake target for write32

[thedoctar]

Public bug reported:

Wifi card stopped working. I use Lubuntu 20.04.

Wifi card info:

  *-network 
   description: Wireless interface
   product: QCA6174 802.11ac Wireless Network Adapter
   vendor: Qualcomm Atheros
   physical id: 0
   bus info: pci@:3a:00.0
   logical name: wlp58s0
   version: 32
   serial: 9c:b6:d0:d4:9b:33
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:135 memory:dc00-dc1f

Releveant journal log attached. In brief,

Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
...
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed

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

** Attachment added: "log.txt"
   https://bugs.launchpad.net/bugs/1882968/+attachment/5382474/+files/log.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/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+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 1871977] Re: g_ether not working after reboot

[Juerg Haefliger]

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

** This bug has been marked a duplicate of bug 1861070
   Raspberry Pi 4B: USB OTG is not working

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

Title:
  g_ether not working after reboot

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  New
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  There is an issue with g_ether after warm reboot.

  Hardware I used for testing:

  Thinkpad L470 + Dock, Ubuntu 19.10
  USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter
  Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu 
19.10

  ==
  it seems like whenever I reboot my Pi, USB gadget port is not detected.  How 
to reproduce:

  1) make sure g_ether works on Pi 4
  2) make sure cdc_ether works on L470, as in dmesg it shows...
  [112961.147030] usb 1-3.2: new high-speed USB device number 11 using xhci_hcd
  [112961.237399] usb 1-3.2: New USB device found, idVendor=045e, 
idProduct=0301, bcdDevice= 5.03
  [112961.237406] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [112961.237411] usb 1-3.2: Product: USB Adapter
  [112961.237414] usb 1-3.2: Manufacturer: Raspberry Pi
  [112961.237418] usb 1-3.2: SerialNumber: ***MASKED***
  [112961.245067] cdc_ether 1-3.2:1.0 eth1: register 'cdc_ether' at 
usb-:00:14.0-3.2, CDC Ethernet Device, ***MASKED***
  3) verify IP connectivity works from L470 to Pi 4.
  4) reboot Pi 4; on L470 it shows:
  [113343.783925] usb 1-3.2: USB disconnect, device number 11
  [113343.784164] cdc_ether 1-3.2:1.0 eth1: unregister 'cdc_ether' 
usb-:00:14.0-3.2, CDC Ethernet Device
  5) wait for Pi 4 to become available (I use wifi on Pi 4 + ssh on L470)
  ==

  Expected: Pi4 should show up to L470 as USB ethernet gadget after warm reboot
  Actual: g_ether is loaded on Pi4 but L470 does not detect it
  Workaround: unplug Pi4 and plug in again, it will work;  given that I am 
using Y-cable, unplugging will not power down Pi 4.
  Concern: lose connectivity that needs human intervention to correct, i.e. 
cannot do it remotely.

  Note: I remember it is detected okay before I file for bug #1861070,
  not sure if it is related or not.  using g_cdc should be the same, but
  not separately tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1871977/+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 1864132] Re: g_ether missing eem support

[Juerg Haefliger]

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

** This bug has been marked a duplicate of bug 1861070
   Raspberry Pi 4B: USB OTG is not working

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

Title:
  g_ether missing eem support

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  New

Bug description:
  I am looking into enabling EEM with g_ether by module option
  use_eem=1, and g_ether won't be loaded because it has no EEM support
  compiled.

  Expected: EEM is compiled with g_ether (no such option for g_cdc) so
  that it can be enabled by use_eem=1.

  My "/sys/module/g_ether/parameters":
  -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice
  -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr
  -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber
  -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct
  -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor
  -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult

  modinfo g_ether:
  parm:   idVendor:USB Vendor ID (ushort)
  parm:   idProduct:USB Product ID (ushort)
  parm:   bcdDevice:USB Device version (BCD) (ushort)
  parm:   iSerialNumber:SerialNumber string (charp)
  parm:   iManufacturer:USB Manufacturer string (charp)
  parm:   iProduct:USB Product string (charp)
  parm:   qmult:queue length multiplier at high/super speed (uint)
  parm:   dev_addr:Device Ethernet Address (charp)
  parm:   host_addr:Host Ethernet Address (charp)
  parm:   use_eem:use CDC EEM mode (bool)

  dmesg:
  ...
  [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to 
list of pending drivers
  ...
  [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in 
SPRAM
  [5.772414] g_ether fe98.usb: failed to start g_ether: -2
  ...

   should it be another bug? -
  There is another issue that when my laptop is connected and the with my Pi 4 
reboot, the cdc_ether function provided to my laptop will not be available 
again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can 
unplug on laptop side w/o Pi 4 losing power).  I remember it was working as 
expected when I was testing out OTG function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1864132/+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 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28

[PhilX]

The bug still exists with 5.3.0-59 and also with the newest Ubuntu 20.04
LTS (kernel 5.4). No mouse and keyboard is working. Why is no one
reacting to such an massive bug, where a lot of people can't use Ubuntu
any more?

** Also affects: linux-signed-hwe (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/1863455

Title:
  USB system (mouse and keybord) are not working since kernel update to
  5.3.0-26 and 5.3.0-28

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  New

Bug description:
  Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. 
Keyboard and mouse (both connected via USB) are not working. It looks like 
everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the 
new kernel version has problems with the USB system. If I choose in GRUB an 
older kernel version (e.g. 5.0.0-37) everything is fine.
  Same problem with kernel 5.3.0-28.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Feb 16 05:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2019-03-19 (333 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: MSI MS-7817
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  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/1863455/+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 1881644] Re: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on

[Bjorn Helgaas]

I'm not using Mint.  I started with Ubuntu 18.04 in June 2018, installed
the "cinnamon" package, and recently updated to 20.04.  I don't know if
this is a regression because I didn't start using this configuration
until after moving to 20.04.  Pretty sure cinnamon came from the ubuntu
repo; my only apt sources change is for chrome.

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

Title:
  20.04 i915 laptop external monitor doesn't resume from power-save,
  must open lid to turn it on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell 5520 laptop -> Dell Thunderbolt dock -> HDMI -> external monitor.
  Running 20.04, i915 driver.

  Laptop lid closed, using external monitor only.  When external monitor
  turns off (after sleep-display-ac), keyboard/mouse activity should
  turn it back on, but do not.  Opening and closing the laptop lid does
  turn the external monitor back on.  Laptop is not suspended; I can ssh
  in from another machine.

  Happy to collect any additional information.

  To reproduce:
  - On Dell 5520 laptop connected to Dell Thunderbolt dock connected to 
external monitor via HDMI
  - Close laptop lid
  - Use external monitor, external keyboard, external mouse
  - Leave system idle for "sleep-display-ac" time
  - System puts external monitor in power-save mode
  - Move mouse, type on keyboard
  - No response, external monitor remains in power-save mode
  - Open laptop lid
  - External monitor turns on
  - Close laptop lid
  - External monitor remains on, I'm able to work as usual
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bjorn  1993 F pulseaudio
   /dev/snd/controlC1:  bjorn  1993 F pulseaudio
   /dev/snd/controlC0:  bjorn  1993 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=39f2962e-3115-438f-a447-03558db08edb
  InstallationDate: Installed on 2018-06-08 (725 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Precision 5520
  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-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-29 (34 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 1203147
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881644/+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 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

[AlekseyK]

** Description changed:

- Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
+ Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec
  
  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists: after
  I close laptop cover or after some time of inactivity Ubuntu suspends or
  hibernate (do not know). After I resume it, it starts to work but in
  10-15 sec Ubuntu freezes and I forced to power-off.
  
  Tried many things mentioned here:
  
  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc
  
  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original nvidia
  driver from manufacturer site. Do not know however if it affects
  warranty? ;) Any ideas how to solve, how to diagnose? Thanks!
  
  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):
  
  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)
  
  Logs for 4.18 kernel are slightly different:
  
  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)
  
- 
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  aleksey8485 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_UA.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_UA.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-1081-oem N/A
-  linux-backports-modules-4.15.0-1081-oem  N/A
-  linux-firmware   1.173.18
+  linux-restricted-modules-4.15.0-1081-oem N/A
+  linux-backports-modules-4.15.0-1081-oem  N/A
+  linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or

[Kernel-packages] [Bug 1877988] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

[Kai Kasurinen]

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

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1008.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i cannot install anything it crashes dpkg and cannot install any
  package from any repository by apt and dpkg

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  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
  AptOrdering:
   linux-tools-common:amd64: Install
   linux-tools-5.4.0-29:amd64: Install
   linux-tools-5.4.0-29-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1339 F pulseaudio
alireza2115 F pulseaudio
   /dev/snd/pcmC0D0p:   alireza2115 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon May 11 15:05:46 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ...
   Unpacking linux-tools-common (5.4.0-29.33) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1008.8
  InstallationDate: Installed on 2020-05-01 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81H7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=4ff62bed-a86c-4c62-a0fd-a29d1fd27022 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8QCN21WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 130-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8QCN21WW(V1.09):bd12/30/2019:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:
  dmi.product.family: ideapad 130-15IKB
  dmi.product.name: 81H7
  dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB
  dmi.product.version: Lenovo ideapad 130-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877988/+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 1877120] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

[Kai Kasurinen]

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

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1008.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installation Error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  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
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   1251 F pulseaudio
gdm1284 F pulseaudio
dhairy 1852 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed May  6 19:12:36 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ...
   Unpacking linux-tools-common (5.4.0-29.33) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1008.8
  InstallationDate: Installed on 2020-04-23 (12 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. Inspiron 5577
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6e08e244-ff74-4758-8edd-bddfdce5aecf ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  UpgradeStatus: Upgraded to focal on 2020-04-23 (12 days ago)
  dmi.bios.date: 12/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.2
  dmi.board.name: 0MVD5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.2:bd12/01/2018:svnDellInc.:pnInspiron5577:pvr1.1.2:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5577
  dmi.product.sku: 07E1
  dmi.product.version: 1.1.2
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877120/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux-riscv - 5.4.0-27.31

---
linux-riscv (5.4.0-27.31) focal; urgency=medium

  * focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798)

  * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667)
- [config] riscv: disable am-1805 RTC driver

  * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after
upgrade to 20.04 (LP: #1875665)
- [Config][focal/linux-riscv] Turn off CONFIG_RT_GROUP_SCHED

  [ Ubuntu: 5.4.0-34.38 ]

  * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118)
  * debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
  * Focal update: v5.4.41 upstream stable release (LP: #1878649)
- USB: serial: qcserial: Add DW5816e support
- nvme: refactor nvme_identify_ns_descs error handling
- nvme: fix possible hang when ns scanning fails during error recovery
- tracing/kprobes: Fix a double initialization typo
- net: macb: Fix runtime PM refcounting
- drm/amdgpu: move kfd suspend after ip_suspend_phase1
- drm/amdgpu: drop redundant cg/pg ungate on runpm enter
- vt: fix unicode console freeing with a common interface
- tty: xilinx_uartps: Fix missing id assignment to the console
- devlink: fix return value after hitting end in region read
- dp83640: reverse arguments to list_add_tail
- fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks
- ipv6: Use global sernum for dst validation with nexthop objects
- mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly
- neigh: send protocol value in neighbor create notification
- net: dsa: Do not leave DSA master with NULL netdev_ops
- net: macb: fix an issue about leak related system resources
- net: macsec: preserve ingress frame ordering
- net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc()
- net_sched: sch_skbprio: add message validation to skbprio_change()
- net: stricter validation of untrusted gso packets
- net: tc35815: Fix phydev supported/advertising mask
- net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict()
- net/tls: Fix sk_psock refcnt leak when in tls_data_ready()
- net: usb: qmi_wwan: add support for DW5816e
- nfp: abm: fix a memory leak bug
- sch_choke: avoid potential panic in choke_reset()
- sch_sfq: validate silly quantum values
- tipc: fix partial topology connection closure
- tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040
- bnxt_en: Fix VF anti-spoof filter setup.
- bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF.
- bnxt_en: Improve AER slot reset.
- bnxt_en: Return error when allocating zero size context memory.
- bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features().
- net/mlx5: DR, On creation set CQ's arm_db member to right value
- net/mlx5: Fix forced completion access non initialized command entry
- net/mlx5: Fix command entry leak in Internal Error State
- net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx()
- net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del()
- HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices
- sctp: Fix bundling of SHUTDOWN with COOKIE-ACK
- Revert "HID: wacom: generic: read the number of expected touches on a per
  collection basis"
- HID: usbhid: Fix race between usbhid_close() and usbhid_stop()
- HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT
- USB: uas: add quirk for LaCie 2Big Quadra
- usb: chipidea: msm: Ensure proper controller reset using role switch API
- USB: serial: garmin_gps: add sanity checking for data length
- tracing: Add a vmalloc_sync_mappings() for safe measure
- crypto: arch/nhpoly1305 - process in explicit 4k chunks
- KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction
- KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path
- KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER
- KVM: arm64: Fix 32bit PC wrap-around
- arm64: hugetlb: avoid potential NULL dereference
- drm: ingenic-drm: add MODULE_DEVICE_TABLE
- ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
- epoll: atomically remove wait entry on wake up
- eventpoll: fix missing wakeup for ovflist in ep_poll_callback
- mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous()
- mm: limit boost_watermark on small zones
- ceph: demote quotarealm lookup warning to a debug message
- staging: gasket: Check the return value of gasket_get_bar_index()
- coredump: fix crash when umh is disabled
- iocost: protect iocg->abs_vdebt with iocg->waitq.lock
- batman-adv: fix batadv_nc_random_weight_tq
- batman-adv: Fix refcnt leak in batadv_show_throughput_overri

[Kernel-packages] [Bug 1882008] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

[Kai Kasurinen]

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

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1008.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  terminal says to "apt --fix broken install" doing that doesnt work

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  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
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shaswat1593 F pulseaudio
   /dev/snd/controlC0:  shaswat1593 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun  4 09:48:47 2020
  DpkgHistoryLog:
   Start-Date: 2020-06-04  09:48:45
   Commandline: apt --fix-broken install
   Requested-By: shaswat (1000)
   Install: linux-tools-common:amd64 (5.4.0-33.37, automatic)
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-33.37_all.deb ...
   Unpacking linux-tools-common (5.4.0-33.37) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-33.37_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1008.8
  InstallationDate: Installed on 2020-05-06 (28 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire E1-472
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=315e55da-ed68-4b87-882f-3732bfb41034 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.08
  dmi.board.name: EA40_HW
  dmi.board.vendor: Acer
  dmi.board.version: V2.08
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.08
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.08:bd10/14/2013:svnAcer:pnAspireE1-472:pvrV2.08:rvnAcer:rnEA40_HW:rvrV2.08:cvnAcer:ct9:cvrV2.08:
  dmi.product.family: Aspire E1-472
  dmi.product.name: Aspire E1-472
  dmi.product.sku: Aspire E1-472_0762_2.08
  dmi.product.version: V2.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882008/+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 1882895] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

[Kai Kasurinen]

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

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1010.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a bad one.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  squinton   1113 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 09:18:45 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-37.41_all.deb ...
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  DuplicateSignature:
   package:linux-tools-common:(not installed)
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1010.10
  InstallationDate: Installed on 2020-05-09 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 004: ID 05ac:024f Apple, Inc. 
   Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.9
  dmi.board.name: 0HD5W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882895/+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 1881120] Re: linux-oem-5.6-tools-common should be dropped

[Launchpad Bug Tracker]

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

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

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

Title:
  linux-oem-5.6-tools-common should be dropped

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  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
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Froze half-way through updating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.

  To workaround, I rebooted, held the shift key and entered the grub
  menu, and booted using the prior kernel, linux 5.4.0.31. Then it
  worked. Grub was listing both linux 5.4.0.31 and linux 5.4.0.33, with
  the latter being the default and the one that froze upon booting after
  the botched update.

  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't
  yet tried to reboot into it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2075 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 14:58:58 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
  InstallationDate: Installed on 2016-06-24 (1446 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FQCTO1WW
  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-31-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-20 (21 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  linux-oem-5.6-tools-common should be dropped

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  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
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881120/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[David Jeffrey]

I have the same with the headset that was initially reported - the
Sennheiser HD 4.50 BTNC. A2DP works perfectly.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1882956] Re: Froze half-way through updating

[Albert Cardona]

I've now booted into linux 5.4.0-37-generic without incident.

** Description changed:

- In ubuntu 20.04 running linux kernel 5.4.0.31, running the updater
+ In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.
  
  To workaround, I rebooted, held the shift key and entered the grub menu,
  and booted using the prior kernel, linux 5.4.0.31. Then it worked. Grub
  was listing both linux 5.4.0.31 and linux 5.4.0.33, with the latter
- being the default and the one that froze upon booting.
+ being the default and the one that froze upon booting after the botched
+ update.
  
  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't yet
  tried to reboot into it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  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.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  albert 2075 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  albert 2075 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 14:58:58 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
  InstallationDate: Installed on 2016-06-24 (1446 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
-  Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
+  Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FQCTO1WW
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  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-31-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-31-generic N/A
-  linux-backports-modules-5.4.0-31-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-31-generic N/A
+  linux-backports-modules-5.4.0-31-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-20 (21 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

Title:
  Froze half-way through updating

Status in linux package in Ubuntu:
  New

Bug description:
  In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.

  To workaround, I rebooted, held the shift key and entered the grub
  menu, and booted using the prior kernel, linux 5.4.0.31. Then it
  worked. Grub was listing both linux 5.4.0.31 and linux 5.4.0.33, with
  the latter being the default and the one that froze upon booting after
  the botched update.

  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't
  yet tried to reboot

[Kernel-packages] [Bug 1882955] [NEW] LXD 4.2 broken on linux-kvm due to missing VLAN filtering

[Stéphane Graber]

Public bug reported:

This is another case of linux-kvm having unexplained differences
compared to linux-generic in areas that aren't related to hardware
drivers (see other bug we filed for missing nft).

This time, CPC is reporting that LXD no longer works on linux-kvm as we
now set vlan filtering on our bridges to prevent containers from
escaping firewalling through custom vlan tags.

This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the
generic kernel but is apparently missing on linux-kvm (I don't have any
system running that kernel to confirm its config, but the behavior
certainly matches that).

We need this fixed in focal and groovy.

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Changed in: linux-kvm (Ubuntu)
   Status: New => Triaged

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

Title:
  LXD 4.2 broken on linux-kvm due to missing VLAN filtering

Status in linux-kvm package in Ubuntu:
  Triaged

Bug description:
  This is another case of linux-kvm having unexplained differences
  compared to linux-generic in areas that aren't related to hardware
  drivers (see other bug we filed for missing nft).

  This time, CPC is reporting that LXD no longer works on linux-kvm as
  we now set vlan filtering on our bridges to prevent containers from
  escaping firewalling through custom vlan tags.

  This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the
  generic kernel but is apparently missing on linux-kvm (I don't have
  any system running that kernel to confirm its config, but the behavior
  certainly matches that).

  We need this fixed in focal and groovy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+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 1881120] Re: linux-oem-5.6-tools-common should be dropped

[Timo Aaltonen]

linux-oem-5.6 is fixed in git, linux still needs to add conflicts for
linux-oem-5.6-tools-common so it gets removed

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-oem-5.6 (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  linux-oem-5.6-tools-common should be dropped

Status in linux package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  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
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881120/+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 1882956] [NEW] Froze half-way through updating

[Albert Cardona]

Public bug reported:

In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
resulted in a frozen, irresponsive mouse and keyboard, and the laptop
wouldn't suspend when closing the lid. Upon reboot, the laptop froze
before reaching the login screen.

To workaround, I rebooted, held the shift key and entered the grub menu,
and booted using the prior kernel, linux 5.4.0.31. Then it worked. Grub
was listing both linux 5.4.0.31 and linux 5.4.0.33, with the latter
being the default and the one that froze upon booting after the botched
update.

Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
installation. ```sudo dpkg --configure -a``` solved the issue without
incident, updating grub with a new entry for linux 5.4.0.37. Haven't yet
tried to reboot into it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
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.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  albert 2075 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 14:58:58 2020
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
InstallationDate: Installed on 2016-06-24 (1446 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
 Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FQCTO1WW
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-31-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-05-20 (21 days ago)
dmi.bios.date: 04/18/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET40W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 1st
dmi.product.name: 20FQCTO1WW
dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
dmi.product.version: ThinkPad X1 Yoga 1st
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Froze half-way through updating

Status in linux package in Ubuntu:
  New

Bug description:
  In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.

  To workaround, I rebooted, held the shift key and entered the grub
  menu, and booted using the prior kernel, linux 5.4.0.31. Then it
  worked. Grub was listing both linux 5.4.0.31 and linux 5.4.0.33, with
  the latter being the default and the one that froze upon booting after
  the botched update.

  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't
  yet tried to reboot into it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2075 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 14:58:58 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
  InstallationDate: Installed on 2016-06-24 (1446 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camer

[Kernel-packages] [Bug 1882917] UdevDb.txt

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882917/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)

[Ole Petersen]

Hi, I have got basically the same machine, but the 14 inch version. My touchpad 
randomly works or not (about 50:50), but its behavior only changes after a 
second boot. If it does not work, I do constantly get the following kernel 
errors:
i2c_designware AMDI0010:00: controller timed out
Also, the touchpad is called sth like MSFT10010:00
and not Elan.
It's the same on all distros I tried (ubuntu, arch fedora)
Any ideas?

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

Title:
  Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as
  touch panel)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad isn't reacting at all

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andreas1223 F pulseaudio
   /dev/snd/controlC0:  andreas1223 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 29 18:05:01 2020
  InstallationDate: Installed on 2020-05-29 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: LENOVO 81YQ
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E7CN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
  dmi.product.family: IdeaPad 5 15ARE05
  dmi.product.name: 81YQ
  dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05
  dmi.product.version: IdeaPad 5 15ARE05
  dmi.sys.vendor: LENOVO

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

[AlekseyK]

apport information

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

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

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882917/+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 1878484] Re: kernel panic on i915

[Víctor Gonzalo]

The kernel from #22 doesn't get to boot. Last message shown is a
suspicious:

fb0: switching to inteldrmfb from EFI VGA

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

Title:
  kernel panic on i915

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using 20.04 fully up to date on an Asrock N3700.

  I'm getting random crashes every now and then. Total crash, no ssh or
  anything (later I found out it's a kernel panic). Not tied to any app,
  but it happened more often during gaming. Logs didn't show anything,
  they just stop. I set up netconsole, with debug and ignore_loglevel in
  the command line and I got this:

  [77196.866485] BUG: unable to handle page fault for address: 00a72860
  [77196.866527] #PF: supervisor read access in kernel mode
  [77196.866535] #PF: error_code(0x) - not-present page
  [77196.866542] PGD 0 P4D 0 
  [77196.866552] Oops:  [#1] SMP PTI
  [77196.866567] CPU: 2 PID: 1408 Comm: Xorg Tainted: P   O  
5.4.0-29-generic #33-Ubuntu
  [77196.866575] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./N3700-ITX, BIOS P2.00 04/16/2018
  [77196.866743] RIP: 0010:__i915_schedule+0x261/0x350 [i915]
  [77196.866748] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 
49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 
60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00
  [77196.866753] RSP: 0018:a48380c2b9e0 EFLAGS: 00010006
  [77196.866759] RAX: 00a72800 RBX: 961bed909a30 RCX: 
9619a559edb0
  [77196.866764] RDX: 961bed909a50 RSI: 961beaa21180 RDI: 
9619a559edc0
  [77196.866769] RBP: a48380c2ba78 R08: 961bf73f4420 R09: 
9619a559ed80
  [77196.866773] R10:  R11: 0208 R12: 
961bf73f4000
  [77196.866783] R13: a48380c2b9f0 R14: 1000 R15: 
a48380c2b9c0
  [77196.866788] FS:  7f6ee2aa9a80() GS:961bf830() 
knlGS:
  [77196.866794] CS:  0010 DS:  ES:  CR0: 80050033
  [77196.866798] CR2: 00a72860 CR3: 00026a0a2000 CR4: 
001006e0
  [77196.866802] Call Trace:
  [77196.866887]  i915_schedule+0x2d/0x50 [i915]
  [77196.866979]  __fence_set_priority+0x6b/0x90 [i915]
  [77196.867067]  fence_set_priority+0x23/0x60 [i915]
  [77196.867117]  i915_gem_object_wait_priority+0x13e/0x170 [i915]
  [77196.867194]  intel_prepare_plane_fb+0x1ab/0x2d0 [i915]
  [77196.867232]  drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper]
  [77196.867305]  intel_atomic_commit+0xc2/0x2b0 [i915]
  [77196.867370]  drm_atomic_nonblocking_commit+0x4d/0x60 [drm]
  [77196.867401]  drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper]
  [77196.867443]  drm_mode_page_flip_ioctl+0x59d/0x630 [drm]
  [77196.867469]  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
  [77196.867490]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [77196.867512]  drm_ioctl+0x234/0x3d0 [drm]
  [77196.867536]  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
  [77196.867550]  do_vfs_ioctl+0x407/0x670
  [77196.867560]  ? fput+0x13/0x15
  [77196.867568]  ? __sys_recvmsg+0x88/0xa0
  [77196.867575]  ksys_ioctl+0x67/0x90
  [77196.867582]  __x64_sys_ioctl+0x1a/0x20
  [77196.867592]  do_syscall_64+0x57/0x190
  [77196.867603]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [77196.867611] RIP: 0033:0x7f6ee2e0737b
  [77196.867618] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48
  [77196.867624] RSP: 002b:7ffe6ff493d8 EFLAGS: 0246 ORIG_RAX: 
0010
  [77196.867631] RAX: ffda RBX: 7ffe6ff49410 RCX: 
7f6ee2e0737b
  [77196.867635] RDX: 7ffe6ff49410 RSI: c01864b0 RDI: 
000e
  [77196.867640] RBP: c01864b0 R08: 002bf8f2 R09: 
006a
  [77196.867645] R10: 000e R11: 0246 R12: 
56454c520040
  [77196.867649] R13: 000e R14: 002bf8f2 R15: 
0002
  [77196.867655] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) 
spl(O) zlua(PO) joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr 
mei_hdcp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common 
intel_powerclamp coretemp kvm_intel kvm punit_atom_debug intel_cstate snd_seq 
snd_seq_device snd_timer snd mei_txe soundcore mei hci_uart 
intel_xhci_usb_role_switch btqca roles btrtl btbcm btintel bluetooth 
ecdh_generic ecc rfkill_gpio acpi_pad intel_int0002_vgpio mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt n

[Kernel-packages] [Bug 1882917] ProcCpuinfo.txt

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

[AlekseyK]

apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882917/+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 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

[AlekseyK]

apport information

** Tags added: apport-collected bionic

** Description changed:

  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec
  
  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists: after
  I close laptop cover or after some time of inactivity Ubuntu suspends or
  hibernate (do not know). After I resume it, it starts to work but in
  10-15 sec Ubuntu freezes and I forced to power-off.
  
  Tried many things mentioned here:
  
  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc
  
  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original nvidia
  driver from manufacturer site. Do not know however if it affects
  warranty? ;) Any ideas how to solve, how to diagnose? Thanks!
  
  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):
  
  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)
  
  Logs for 4.18 kernel are slightly different:
  
  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)
+ 
+ 
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aleksey8485 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-01-04 (158 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
+ MachineType: Dell Inc. Latitude 5501
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_UA.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-1081-oem N/A
+  linux-backports-modules-4.15.0-1081-oem  N/A
+  linux-firmware   1.173.18
+ Tags:  bionic
+ Uname: Linux 4.15.0-1081-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/12/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.8.4
+ dmi.board.name: 0Y8H01
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 5501
+ dmi.sys.vendor: Dell Inc.

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it stil

[Kernel-packages] [Bug 1882917] 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 1882917

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

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

[Nitro Kash]

No. REISUB doesn't work. Mouse and keyboard doesn't work during the
freeze. I am not able to open a tty or ssh to the system. It is exactly
like what is described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961. But none
of the solutions worked for me, including removing xserver-xorg-video-
intel. I will try using the new kernel.

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes randomly. Keyboard and mouse do not work at that time. I am 
not able to ssh to the computer or access tty. I am able to do only a hard 
reset. I tried some troubleshooting myself, but with my novice expertise with 
ubuntu. The freeze is more or less random. But it is possibly more frequent 
when running a video, like a youtube video in a browser. Freeze is more 
frequenty when going full screen with a video, a VM machine or a remote desktop 
through vnc4server.
  1. Tried removing some software like chrome, dropbox, virtualbox, etc. That 
did not help.
  2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 
kernel. That did not help either.
  3. Tried other distros like Mint and Fedora. Still had problem.
  4. Tried running with NVidia driver and xserver-xorg. The problem occured 
with both.
  5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured 
in both. 
  6. Tried all the suggestions in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were 
applicable. None of the suggestions helped.
  7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and 
experienced no crash/freeze with youtube running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 12:36:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651]
  InstallationDate: Installed on 2020-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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 N/A
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouv

[Kernel-packages] [Bug 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF

[Junien Fridrick]

Sorry for various reasons I won't be able to test 20.04

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

Title:
   mlx5 : not able to set a high MTU on the representor port for a VF

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25
  [1].

  With the distro driver, it's impossible to increase the MTU of a
  representor port :

  $ sudo ip li set enp50s0f0_0 mtu 1501
  RTNETLINK answers: Invalid argument

  Whereas with the OFED driver [2], I can set it up to 9978 :
  $ sudo ip li set mtu 9978 enp50s0f0_0
  $

  This is blocking to use OVS offloading with jumbo frames. Could we
  please get the feature in the distro driver ?

  Thanks !

  Steps to create the representor :

  echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs
  echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind
  sudo devlink dev eswitch set pci/:32:00.0 mode switchdev
  echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind

  [1] http://www.mellanox.com/related-docs/prod_adapter_cards
  /PB_ConnectX-5_VPI_Card_SocketDirect.pdf

  [2]
  
http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers&mrequest=downloads&mtype=ofed&mver=MLNX_OFED-4.5-1.0.1.0&mname=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 11 14:18 seq
   crw-rw 1 root audio 116, 33 Apr 11 14:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr 11 14:42:57 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+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 1867983] Re: Computer is frozen after suspend

[Glandos]

Is there anything to add?

I saw also no answer from you on the LKML, do you want me to answer that
the patch is working for me? I'm not used to LKML, but I think I can try
:)

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

Title:
  Computer is frozen after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  snd_hda_intel blocks/freezes suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since some packages upgrade(probalby couple months back; when I had
  LTS bionic) I'm unable to suspend my PC.

  I thought installing newest LTS focal will solve this problem but it
  didn't - system freezes on suspend displaying plymouth last screen.

  I found debug howto here :
  https://www.kernel.org/doc/Documentation/power/s2ram.txt

  What I found according to it:

  lut 21 09:43:39 pc kernel: PM:   Magic number: 0:88:726
  lut 21 09:43:39 pc kernel: PM:   hash matches drivers/base/power/main.c:1721
  lut 21 09:43:39 pc kernel: block loop6: hash matches
  lut 21 09:43:39 pc kernel: pci :01:00.1: hash matches
  lut 21 09:43:39 pc kernel: rtc_cmos 00:06: setting system clock to 
2060-02-21T08:43:23 UTC (2844578603)

  $ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Complex
  00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) 
I/O Memory Management Unit
  00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Kaveri P2P Bridge for 
GFX PCIe Port [1:0]
  00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
  00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA 
Controller [AHCI mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 
16)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (rev 01)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 0
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 1
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 2
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 3
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 4
  00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 5
  01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  marcin@pc:/sys

  
  $ ls /sys/devices/pci* 
  :00:00.0  :00:02.1  :00:04.0  :00:11.0  :00:13.0  
:00:14.1  :00:14.4  :00:18.1  :00:18.4   pci_bus
  :00:00.2  :00:03.0  :00:10.0  :00:12.0  :00:13.2  
:00:14.2  :00:14.5  :00:18.2  :00:18.5   power
  :00:02.0  :00:03.1  :00:10.1  :00:12.2  :00:14.0  
:00:14.3  :00:18.0  :00:18.3  firmware_node  uevent

  
  $ cat /sys/power/pm_trace_dev_match
  resulted in: block and snd_hda_intel

  as I was unable to force :
  $ modprobe -r -f snd_hda_intel
  modprobe: FATAL: Module snd_hda_intel is in use.

  I did change /etc/default/grub to:
  GRUB_CMDLINE_LINUX="snd_hda_intel.blacklist=1 
modprobe.blacklist=snd_hda_intel"

  then sudo grub-update.

  After reboot suspend was finnaly working correctly 
  but I've NO sound now:(

  
  Googling on the internet I found:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/co

[Kernel-packages] [Bug 1826376] Re: cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers

[Junien Fridrick]

Sorry I won't be able to test 20.04 as I don't have a Chelsio NIC
anymore

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

Title:
  cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Using ubuntu 18.04 with kernel 4.15.0-47-generic, my Chelsio NIC can't
  offload VXLAN with the distro drivers (features "tx-udp_tnl-
  segmentation" and "tx-udp_tnl-csum-segmentation"), but with the OFED
  driver ("ChelsioUwire-3.10.0.0"), it can.

  Can we please get this in the distro driver ?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 19 14:48 seq
   crw-rw 1 root audio 116, 33 Apr 19 14:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr 25 08:53:20 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro Super Server
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=7b06790c-9447-446a-b1cf-b25104638b26 ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826376/+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 1877858] Re: Improve TSC refinement (and calibration) reliability

[Guilherme G. Piccoli]

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

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

Title:
  Improve TSC refinement (and calibration) reliability

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

Bug description:
  [Impact]
  * We received a report recently of a missing TSC refinement across multiple 
reboots of a server, in an Intel Skylake-based processor. This was only 
reproducible in Bionic pre-5.0.

  * After checking kernel commits, we came up with 2 commits that
  largely improve the situation: a786ef152cdc ("x86/tsc: Make
  calibration refinement more robust")
  [git.kernel.org/linus/a786ef152cdc] and 604dc9170f24 ("x86/tsc: Use
  CPUID.0x16 to calculate missing crystal frequency")
  [git.kernel.org/linus/604dc9170f24]. We hereby request SRU for both of
  them.

  * The first commit contains improvement in comments and in an offset to match 
more recent (fast) machines, but the important part is a retry mechanism in the 
TSC refinement (in case it fails due to some disturbance on TSC read, like 
NMIs/SMIs).
   
  * The second commit is an improvement in TSC calibration for Skylake (and 
some other models), by checking a register instead of relying on table-based 
hardcoded values.

  * A note for Xenial (kernel 4.4): the second patch would require the
  inclusion of more commits, so given the "maturity" of this release
  (and the fact kernel 4.15 is an HWE for Xenial), I've kept it out of
  Xenial, backporting only the first and more important patch for 4.4 .

  [Test case]
  * Unfortunately there's not an easy way to test the effectiveness of the 
commits, specially the refinement improvement.

  * The user that reported us the missing refinements was able to test
  300 reboots with a regular Bionic kernel (and it reproduced the issue
  at least once), whereas when they tested with Bionic kernel + both
  hereby proposed commits, the problem didn't happen.

  * Regarding the calibration commit, it was well-tested by community
  using multiple machines and checking the TSC calibration read vs.
  tables present in instlatx64.atw.hu .

  [Regression potential]
  * We consider the regression potential low, specially due to the nature of 
the patches: the first is basically a retry mechanism (and some improvement in 
an offset to reflect more recent machines), and the 2nd is an improvement for 
TSC calibration on some platforms (that are currently hardcoded in a 
table-based way in kernel). Also, the patches are present upstream for a while 
and I couldn't find any fixes for them.

  * An hypothetical regression from the 2nd patch could be in TSC
  precision calculation, which refinement itself might as well
  circumvent. From the first patch, a bug in code is the one
  hypothetical regression I could think.

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