[Kernel-packages] [Bug 1892614] Re: RTL8723DE firmware bug: rtw_pci 0000:0d:00.0: failed to send h2c command

2020-10-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  RTL8723DE firmware bug: rtw_pci :0d:00.0: failed to send h2c
  command

Status in linux package in Ubuntu:
  Expired

Bug description:
  WiFi (WLAN) Module: Realtek RTL8723DE (came with my HP laptop). Ubuntu
  20.04 is the first Ubuntu release to have the module working out of
  the box.

  Network devices as output by 'inxi -N'
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: 
r8169 
  Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter driver: rtw_pci 
  Device-3: Realtek 802.11n WLAN Adapter type: USB driver: btusb 

  The error 'rtw_pci :0d:00.0: failed to send h2c command' is logged
  every time I use the module for internet access. The error is logged
  more frequently especially if I stream a video and other related
  tasks. The driver is stable but it may fail become unavailable unless
  a cold boot is performed. The attached log contains the error logged
  many times when I was streaming a video Today. According to
  https://askubuntu.com/questions/1217892/system-responds-with-failed-
  to-send-h2c-command-on-shutdown-what-does-that-me the error may be due
  to a firmware issue or the driver issue. The error does not occur if
  using the Realtek drivers obtained from Github in this link:
  https://github.com/lwfinger/rtw88 and the driver of the module is
  identified as rtw_8723de.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1949 F pulseaudio
   /dev/snd/controlC1:  tony   1949 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 08:37:12 2020
  InstallationDate: Installed on 2020-08-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: HP HP Laptop 15-bs1xx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=7b47411f-1984-4025-9678-8f5fba5b2059 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.65
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8444
  dmi.board.vendor: HP
  dmi.board.version: 67.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs1xx
  dmi.product.sku: 4UL47EA#BH5
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1892631] Re: Realtek RTL8723DE - rtw_pci: probe of 0000:02:00.0 failed with error -22

2020-10-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Realtek RTL8723DE - rtw_pci: probe of :02:00.0 failed with error
  -22

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since i shifted to linux os from windows there is no wifi adapter in
  rhis OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rgms   1613 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:44:50 2020
  InstallationDate: Installed on 2020-08-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: HP HP Laptop 15-ra0xx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=9261e553-c4b1-42ef-af23-6efccf90f670 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832C
  dmi.board.vendor: HP
  dmi.board.version: 25.56
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.60:bd05/17/2019:svnHP:pnHPLaptop15-ra0xx:pvrType1ProductConfigId:rvnHP:rn832C:rvr25.56:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ra0xx
  dmi.product.sku: 3QT49EA#BH5
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

2020-10-23 Thread Dhinchak Dhoom
Hi,

I was tracking this error since very long but still it seems that the issue 
still exist.
Even after Installing the above mentioned kernel touch-pad is still not working 
neither is visible in /proc/bus/input/devices. (attached is the cat 
/proc/bus/input/devices output)

>uname -a
Linux dhinchakdhoom-Thinkbook 5.6.0-1032-oem #33-Ubuntu SMP Fri Oct 16 12:04:33 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 

** Attachment added: "devices.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5426289/+files/devices.txt

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

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Triaged
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  Touchpad on sereval Lenovo ThinkBook doesn't work.

  [Fix]
  Maintain method calling ordering by calling _REG before issuing _STA, as
  ACPI spec suggested, for I2C ACPI devices.

  [Test]
  Positive feedback from several users.

  [Regression Potential]
  If there are some systems that rely on the wrong calling ordering then
  there's a regression risk. However it's rather unlikely.

  == Original Bug Report ==
  This is happening on a ThinkBook 14 IML 20RV.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1848 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 11:10:52 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20RV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN21WW
  dmi.board.name: LVA/LVAB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
  dmi.product.family: ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1901275] Re: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1901261 ***
https://bugs.launchpad.net/bugs/1901261

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 #1901261, 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 1901261
   package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: 
triggers looping, abandoned

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened after an upgrade to Ubuntu 20.10

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aman   1649 F pulseaudio
   /dev/snd/pcmC1D0p:   aman   1649 F...m pulseaudio
   /dev/snd/controlC0:  aman   1649 F pulseaudio
   /dev/snd/timer:  aman   1649 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 21:48:55 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-10-18 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=dc8e5d33-f9a4-46e3-a020-71bc51e232f7 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
  dmi.bios.date: 05/07/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434IQ_Q407IQ.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434IQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434IQ_Q407IQ.301:bd05/07/2020:br5.16:svnASUSTeKCOMPUTERINC.:pnZenBookUX434IQ_Q407IQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434IQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434IQ_Q407IQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2020-10-23 Thread Ubuntu Kernel Bot
*** This bug is a duplicate of bug 1901261 ***
https://bugs.launchpad.net/bugs/1901261

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened after an upgrade to Ubuntu 20.10

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aman   1649 F pulseaudio
   /dev/snd/pcmC1D0p:   aman   1649 F...m pulseaudio
   /dev/snd/controlC0:  aman   1649 F pulseaudio
   /dev/snd/timer:  aman   1649 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 21:48:55 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-10-18 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=dc8e5d33-f9a4-46e3-a020-71bc51e232f7 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
  dmi.bios.date: 05/07/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434IQ_Q407IQ.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434IQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434IQ_Q407IQ.301:bd05/07/2020:br5.16:svnASUSTeKCOMPUTERINC.:pnZenBookUX434IQ_Q407IQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434IQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434IQ_Q407IQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1901275] [NEW] package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread Aman Kumar Gupta
*** This bug is a duplicate of bug 1901261 ***
https://bugs.launchpad.net/bugs/1901261

Public bug reported:

This happened after an upgrade to Ubuntu 20.10

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  aman   1649 F pulseaudio
 /dev/snd/pcmC1D0p:   aman   1649 F...m pulseaudio
 /dev/snd/controlC0:  aman   1649 F pulseaudio
 /dev/snd/timer:  aman   1649 f pulseaudio
CasperMD5CheckResult: skip
Date: Fri Oct 23 21:48:55 2020
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2020-10-18 (5 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=dc8e5d33-f9a4-46e3-a020-71bc51e232f7 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.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu35
SourcePackage: linux
Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
dmi.bios.date: 05/07/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434IQ_Q407IQ.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434IQ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434IQ_Q407IQ.301:bd05/07/2020:br5.16:svnASUSTeKCOMPUTERINC.:pnZenBookUX434IQ_Q407IQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434IQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434IQ_Q407IQ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package groovy

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened after an upgrade to Ubuntu 20.10

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aman   1649 F pulseaudio
   /dev/snd/pcmC1D0p:   aman   1649 F...m pulseaudio
   /dev/snd/controlC0:  aman   1649 F pulseaudio
   /dev/snd/timer:  aman   1649 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 21:48:55 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-10-18 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_Q407IQ
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=dc8e5d33-f9a4-46e3-a020-71bc51e232f7 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
  dmi.bios.date: 05/07/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434IQ_Q407IQ.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434IQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

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

2020-10-23 Thread 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 1901268

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

Title:
  k-4.8 breaks display and mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest 4.8 kernel causes display to break
  menu does not open
  mouse doesnt work
  system: intel pentium 4th generation processor with HD graphics

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

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


[Kernel-packages] [Bug 1901268] [NEW] k-4.8 breaks display and mouse

2020-10-23 Thread ameyjoshi
Public bug reported:

The latest 4.8 kernel causes display to break
menu does not open
mouse doesnt work
system: intel pentium 4th generation processor with HD graphics

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1901268

Title:
  k-4.8 breaks display and mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest 4.8 kernel causes display to break
  menu does not open
  mouse doesnt work
  system: intel pentium 4th generation processor with HD graphics

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

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


[Kernel-packages] [Bug 1901266] [NEW] system slagish, thermal keep frequency at 400MHz

2020-10-23 Thread Alexander Mitsos
Public bug reported:

This morning I upgraded to 20.10 from 20.04

The system was quite slow although I have a fast machine. My virtual windows 10 
on virtualbox became unusable. When I tried to have the virtual machine open, I 
could not participate properly in a zoom call (I could still hear the people 
but they said that my voice was very choppy)
On 20.04 I was super-happy with the speed and I could have as many apps running 
as I want.

Based on google I started looking at 
% journalctl --follow
and this shows quite a few errors but not repeating often enough to explain it.

Then I googled some more and found that /boot/efi was writing and
reading.

Then I googled some more and thought I had trouble with gnome. So I reset it to 
default
% dconf reset -f /org/gnome/
and disabled the extensions. This made things slightly better but by far not 
acceptable.

After lots of searching I checked the frequency of the CPUs and it was at the 
minimum 400Hz (as shown by i7z and also other tools). I tried setting the 
governor with cpufreqctl and similar methods but this did not change anything.
I then found an old bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236 and tried 
% sudo systemctl stop thermald
this seems to work. After a few seconds the frequency shown in i7z goes to 
~4500 MHz and the virtual machine seems to work fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: thermald 2.3-4
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 01:39:40 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-20180608-47+merion+X66
InstallationDate: Installed on 2019-09-27 (392 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
SourcePackage: thermald
UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
mtime.conffile..etc.thermald.thermal-conf.xml: 2020-10-24T01:35:59.781865

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


** Tags: amd64 apport-bug groovy

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

Title:
  system slagish, thermal keep frequency at 400MHz

Status in thermald package in Ubuntu:
  New

Bug description:
  This morning I upgraded to 20.10 from 20.04

  The system was quite slow although I have a fast machine. My virtual windows 
10 on virtualbox became unusable. When I tried to have the virtual machine 
open, I could not participate properly in a zoom call (I could still hear the 
people but they said that my voice was very choppy)
  On 20.04 I was super-happy with the speed and I could have as many apps 
running as I want.

  Based on google I started looking at 
  % journalctl --follow
  and this shows quite a few errors but not repeating often enough to explain 
it.

  Then I googled some more and found that /boot/efi was writing and
  reading.

  Then I googled some more and thought I had trouble with gnome. So I reset it 
to default
  % dconf reset -f /org/gnome/
  and disabled the extensions. This made things slightly better but by far not 
acceptable.

  After lots of searching I checked the frequency of the CPUs and it was at the 
minimum 400Hz (as shown by i7z and also other tools). I tried setting the 
governor with cpufreqctl and similar methods but this did not change anything.
  I then found an old bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236 and tried 
  % sudo systemctl stop thermald
  this seems to work. After a few seconds the frequency shown in i7z goes to 
~4500 MHz and the virtual machine seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: thermald 2.3-4
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 01:39:40 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-20180608-47+merion+X66
  InstallationDate: Installed on 2019-09-27 (392 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: thermald
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  mtime.conffile..etc.thermald.thermal-conf.xml: 2020-10-24T01:35:59.781865

To manage notifications about this bug go to:

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

2020-10-23 Thread 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/1901261

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into this issue when trying to upgrade to 20.10 release from
  20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  segfault   3157 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Oct 24 02:45:57 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-12-24 (304 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. MS-7C37
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=69a0b6ee-819a-4efd-9a89-71cda6bab44a 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 04/20/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING EDGE WIFI (MS-7C37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd04/20/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGEDGEWIFI(MS-7C37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C37
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty

2020-10-23 Thread Wowbagger
This is a stupid uninitialized variable error in the postinstall script:

case "$1" in
configure)
# Added manually, since we mangled the arguments, and 
dpkg-maintscript-helper
# won't work
if [ -n "$2" ] && `dpkg --compare-versions "$2" lt "340.106-0ubuntu5"`; 
then
rm -f /etc/modprobe.d/nvidia-340.conf
fi
CURRENT_KERNEL=$(uname -r)
NEWEST_KERNEL=$(get_newest_kernel "$KERNELS")

Variable "KERNELS" is not defined, so when get_newest_kernel tries to
use dpkg to look up the kernel version it fails.

Defining "KERNELS" to be CURRENT_KERNEL allows the configure to work:

case "$1" in
configure)
# Added manually, since we mangled the arguments, and 
dpkg-maintscript-helper
# won't work
if [ -n "$2" ] && `dpkg --compare-versions "$2" lt "340.106-0ubuntu5"`; 
then
rm -f /etc/modprobe.d/nvidia-340.conf
fi
CURRENT_KERNEL=$(uname -r)
KERNELS=$CURRENT_KERNEL
NEWEST_KERNEL=$(get_newest_kernel "$KERNELS")

Seriously - this has been an issue for over a year, and nobody bothered
to look into it?

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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

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


[Kernel-packages] [Bug 1901261] Re: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  I ran into this issue when trying to upgrade to 20.10 release from
  20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  segfault   3157 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Oct 24 02:45:57 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-12-24 (304 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. MS-7C37
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=69a0b6ee-819a-4efd-9a89-71cda6bab44a 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 04/20/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING EDGE WIFI (MS-7C37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd04/20/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGEDGEWIFI(MS-7C37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C37
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1901261] [NEW] package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread yasaswi
Public bug reported:

I ran into this issue when trying to upgrade to 20.10 release from
20.04.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  segfault   3157 F pulseaudio
CasperMD5CheckResult: skip
Date: Sat Oct 24 02:45:57 2020
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2019-12-24 (304 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. MS-7C37
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=69a0b6ee-819a-4efd-9a89-71cda6bab44a 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.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu35
SourcePackage: linux
Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
dmi.bios.date: 04/20/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING EDGE WIFI (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd04/20/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGEDGEWIFI(MS-7C37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-package groovy

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  I ran into this issue when trying to upgrade to 20.10 release from
  20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  segfault   3157 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Oct 24 02:45:57 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-12-24 (304 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. MS-7C37
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=69a0b6ee-819a-4efd-9a89-71cda6bab44a 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 04/20/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING EDGE WIFI (MS-7C37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd04/20/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGEDGEWIFI(MS-7C37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C37
  

[Kernel-packages] [Bug 967399] Re: [11.10] Elantech trackpoint does not work Lenovo

2020-10-23 Thread Free Beachler
Confirmed 2020 Ubuntu support for ELANTech mouse/touchpad is horrid. I'd
like to add https://bugzilla.redhat.com/show_bug.cgi?id=1543769 to the
list of related kernel bugs.

** Bug watch added: Red Hat Bugzilla #1543769
   https://bugzilla.redhat.com/show_bug.cgi?id=1543769

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

Title:
  [11.10] Elantech trackpoint does not work Lenovo

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

Bug description:
  Title: trackpoint does not function

  Summary: trackpoint does not function

  Steps:
  1. log into desktop
  2. use trackpoint and trackpoint buttons

  Expected results: laptop responds to trackpoint and trackpoint buttons
  being pressed

  Actual results: nothing happens
  Manufacturer: LENOVO

  WORKAROUND: sudo modprobe proto=exps enables the trackpoint and
  touchpad, but user will lose multi-touch functionality.

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

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


[Kernel-packages] [Bug 1901257] [NEW] Bionic update: upstream stable patchset 2020-10-23

2020-10-23 Thread Kamal Mostafa
Public bug reported:

SRU Justification

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

   upstream stable patchset 2020-10-23

Ported from the following upstream stable releases:
v4.14.200, v4.19.148,
   v4.19.149

   from git://git.kernel.org/

af_key: pfkey_dump needs parameter validation
KVM: fix memory leak in kvm_io_bus_unregister_dev()
kprobes: fix kill kprobe which has been marked as gone
mm/thp: fix __split_huge_pmd_locked() for migration PMD
cxgb4: Fix offset when clearing filter byte counters
geneve: add transport ports in route lookup for geneve
hdlc_ppp: add range checks in ppp_cp_parse_cr()
ip: fix tos reflection in ack and reset packets
net: ipv6: fix kconfig dependency warning for IPV6_SEG6_HMAC
nfp: use correct define to return NONE fec
tipc: Fix memory leak in tipc_group_create_member()
tipc: fix shutdown() of connection oriented socket
tipc: use skb_unshare() instead in tipc_buf_append()
bnxt_en: Protect bnxt_set_eee() and bnxt_set_pauseparam() with mutex.
net: phy: Avoid NPD upon phy_detach() when driver is unbound
net: qrtr: check skb_put_padto() return value
net: add __must_check to skb_put_padto()
ipv4: Update exception handling for multipath routes via same device
MAINTAINERS: add CLANG/LLVM BUILD SUPPORT info
Documentation/llvm: add documentation on building w/ Clang/LLVM
Documentation/llvm: fix the name of llvm-size
net: wan: wanxl: use allow to pass CROSS_COMPILE_M68k for rebuilding firmware
net: wan: wanxl: use $(M68KCC) instead of $(M68KAS) for rebuilding firmware
kbuild: replace AS=clang with LLVM_IAS=1
tcp_bbr: refactor bbr_target_cwnd() for general inflight provisioning
tcp_bbr: adapt cwnd based on ack aggregation estimation
serial: 8250: Avoid error message on reprobe
RDMA/ucma: ucma_context reference leak in error path
mm: fix double page fault on arm64 if PTE_AF is cleared
scsi: aacraid: fix illegal IO beyond last LBA
m68k: q40: Fix info-leak in rtc_ioctl
gma/gma500: fix a memory disclosure bug due to uninitialized bytes
ASoC: kirkwood: fix IRQ error handling
media: smiapp: Fix error handling at NVM reading
arch/x86/lib/usercopy_64.c: fix __copy_user_flushcache() cache writeback
x86/ioapic: Unbreak check_timer()
ALSA: usb-audio: Add delay quirk for H570e USB headsets
ALSA: hda/realtek - Couldn't detect Mic if booting with headset plugged
PM / devfreq: tegra30: Fix integer overflow on CPU's freq max out
scsi: fnic: fix use after free
clk/ti/adpll: allocate room for terminating null
mtd: cfi_cmdset_0002: don't free cfi->cfiq in error path of cfi_amdstd_setup()
mfd: mfd-core: Protect against NULL call-back function pointer
tracing: Adding NULL checks for trace_array descriptor pointer
bcache: fix a lost wake-up problem caused by mca_cannibalize_lock
RDMA/i40iw: Fix potential use after free
xfs: fix attr leaf header freemap.size underflow
RDMA/iw_cgxb4: Fix an error handling path in 'c4iw_connect()'
mmc: core: Fix size overflow for mmc partitions
gfs2: clean up iopen glock mess in gfs2_create_inode
debugfs: Fix !DEBUG_FS debugfs_create_automount
CIFS: Properly process SMB3 lease breaks
kernel/sys.c: avoid copying possible padding bytes in copy_to_user
neigh_stat_seq_next() should increase position index
rt_cpu_seq_next should increase position index
seqlock: Require WRITE_ONCE surrounding raw_seqcount_barrier
media: ti-vpe: cal: Restrict DMA to avoid memory corruption
ACPI: EC: Reference count query handlers under lock
dmaengine: zynqmp_dma: fix burst length configuration
powerpc/eeh: Only dump stack once if an MMIO loop is detected
tracing: Set kernel_stack's caller size properly
ar5523: Add USB ID of SMCWUSBT-G2 wireless adapter
selftests/ftrace: fix glob selftest
tools/power/x86/intel_pstate_tracer: changes for python 3 compatibility
Bluetooth: Fix refcount use-after-free issue
mm: pagewalk: fix termination condition in walk_pte_range()
Bluetooth: prefetch channel before killing sock
ALSA: hda: Clear RIRB status before reading WP
skbuff: fix a data race in skb_queue_len()
audit: CONFIG_CHANGE don't log internal bookkeeping as an event
selinux: sel_avc_get_stat_idx should increase position index
scsi: lpfc: Fix RQ buffer leakage when no IOCBs available
scsi: lpfc: Fix coverity errors in fmdi attribute handling
drm/omap: fix possible object reference leak
perf test: Fix test trace+probe_vfs_getname.sh on s390
RDMA/rxe: Fix configuration of atomic queue pair attributes
KVM: x86: fix incorrect comparison in trace event
media: staging/imx: Missing assignment in imx_media_capture_device_register()
x86/pkeys: Add check for 

[Kernel-packages] [Bug 1894893] Re: [linux-azure][hibernation] GPU device no longer working after resume from hibernation in NV6 VM size

2020-10-23 Thread Marcelo Cerri
SRU submission: https://lists.ubuntu.com/archives/kernel-
team/2020-October/114241.html

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

Title:
  [linux-azure][hibernation] GPU device no longer working after resume
  from hibernation in NV6 VM size

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Groovy:
  In Progress

Bug description:
  [Impact]

  There are failed logs after resume from hibernation in NV6 (GPU passthrough 
size) VM in Azure:
  [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5

  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.

  [Test Case]

  How reproducible:
  100%

  Steps to Reproduce:
  1. Start a Standard_NV6 VM in Azure and enable hibernation properly (please 
refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )

  E.g. here I create a Generation-1 Ubuntu 20.04 Standard NV6_Promo (6
  vcpus, 56 GiB memory) VM in East US 2.

  2. Make sure the in-kernel open-source nouveau driver is loaded, or
  blacklist the nouveau driver and install the official Nvidia GPU
  driver (please follow https://docs.microsoft.com/en-us/azure/virtual-
  machines/linux/n-series-driver-setup : "Install GRID drivers on NV or
  NVv3-series VMs" -- the most important step to run the "./NVIDIA-
  Linux-x86_64-grid.run".)

  3. Run hibernation from serial console
  # systemctl hibernate

  4. After hibernation finishes, start VM and check dmesg
  # dmesg|grep fail

  Actual results:
  [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5

  And /proc/interrupts shows that the GPU interrupts are no longer
  happening.

  Expected results:
  No failed logs, and the GPU interrupt should still happen after hibernation.

  [Regression Potential]

  The fix touches the pci-hyperv and can compromise the hyper-v guest
  drivers. However the change is focuses on the execution path used for
  hibernation that is still not officially supported.

  [Other info]

  BUG FIX:
  I made a fix here: https://lkml.org/lkml/2020/9/4/1268.

  Without the patch, we see the error "hv_pci
  47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5"
  during hibernation when the VM has the Nvidia GPU driver loaded, and
  after hibernation the GPU driver can no longer receive any MSI/MSI-X
  interrupts when we check /proc/interrupts.

  With the patch, we should no longer see the error, and the GPU driver
  should still receive interrupts after hibernation.

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

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


[Kernel-packages] [Bug 1894895] Re: [linux-azure][hibernation] ]VM hangs after hibernation/resume if the VM has SRIOV NIC and has been deallocated

2020-10-23 Thread Marcelo Cerri
SRU submission: https://lists.ubuntu.com/archives/kernel-
team/2020-October/114240.html

** Description changed:

  [Impact]
  
  Description of problem:
  On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's 
VMBus Instance GUID may change, and as a result hibernation/resume can hang 
forever.
  
  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.
  
  [Test Case]
  
  How reproducible:
  100%
  
  Steps to Reproduce:
  1. Start a VM in Azure that supports Accelerated Networking, and enable 
hibernation properly (please refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )
  
  2. Do hibernation from serial console
  # systemctl hibernate
  
  4. After the VM state changes to "Stopped", click "Stop" button from
  Azure portal to change the VM state to Stopped(deallocated)
  
  5. Wait for some time (e.g. 10 minutes? 1 hour?), and click the "Start"
  button to start the VM, and then check the boot-up process from the
  serial console.
  
  Actual results:
  Can not boot up. VM hangs after resume.
  
  Starting Resume from hibernation us…6c7-2c0c-491e-adcf-b625d69faf76...
  [   19.822747] PM: resume from hibernation
  [   19.836693] Freezing user space processes ... (elapsed 0.003 seconds) done.
  [   19.846968] OOM killer disabled.
  [   19.850236] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [   20.542934] PM: Using 1 thread(s) for decompression
  [   20.548250] PM: Loading and decompressing image data (559580 pages)...
  [   22.844964] PM: Image loading progress:   0%
  [   28.131327] PM: Image loading progress:  10%
  [   32.346480] PM: Image loading progress:  20%
  [   37.453971] PM: Image loading progress:  30%
  [   40.834525] PM: Image loading progress:  40%
  [   42.980629] PM: Image loading progress:  50%
  [   44.342959] PM: Image loading progress:  60%
  [   45.506197] PM: Image loading progress:  70%
  [   46.800445] PM: Image loading progress:  80%
  [   48.010185] PM: Image loading progress:  90%
  [   49.045671] PM: Image loading done
  [   49.050419] PM: Read 2238320 kbytes in 28.48 seconds (78.59 MB/s)
  [   49.074198] printk: Suspending console(s) (use no_console_suspend to debug)
  
  (The VM hangs here forever)
  
  [Regression Potential]
  
- The fix touched the vmbus and can compromise the hyper-v guest drivers.
+ The fix touches vmbus and can compromise the hyper-v guest drivers.
  However the change is simple and just adds an additional timeout.
  
  [Other info]
  
  BUG FIX:
  A workaround patch is available and is being reviewed: 
https://lkml.org/lkml/2020/9/4/1270
  
  Final fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19873eec7e13fda140a0ebc75d6664e57c00bfb1

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

Title:
  [linux-azure][hibernation] ]VM hangs after hibernation/resume if the
  VM has SRIOV NIC and has been deallocated

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  [Impact]

  Description of problem:
  On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's 
VMBus Instance GUID may change, and as a result hibernation/resume can hang 
forever.

  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.

  [Test Case]

  How reproducible:
  100%

  Steps to Reproduce:
  1. Start a VM in Azure that supports Accelerated Networking, and enable 
hibernation properly (please refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )

  2. Do hibernation from serial console
  # systemctl hibernate

  4. After the VM state changes to "Stopped", click "Stop" button from
  Azure portal to change the VM state to Stopped(deallocated)

  5. Wait for some time (e.g. 10 minutes? 1 hour?), and click the
  "Start" button to start the VM, and then check the boot-up process
  from the serial console.

  Actual results:
  Can not boot up. VM hangs after resume.

  Starting Resume from hibernation us…6c7-2c0c-491e-adcf-b625d69faf76...
  [   19.822747] PM: resume from hibernation
  [   19.836693] Freezing user space processes ... (elapsed 0.003 seconds) done.
  [   19.846968] OOM killer disabled.
  [   19.850236] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [   20.542934] PM: Using 1 thread(s) for decompression
  [   20.548250] PM: Loading and decompressing image data (559580 pages)...
  [   22.844964] PM: Image loading progress:   0%
  [   28.131327] PM: Image loading progress:  10%
  [   32.346480] PM: Image loading progress:  20%
  [   37.453971] PM: Image loading progress:  30%
  [   40.834525] PM: Image loading progress:  40%
  [   42.980629] PM: 

[Kernel-packages] [Bug 1894893] Re: [linux-azure][hibernation] GPU device no longer working after resume from hibernation in NV6 VM size

2020-10-23 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

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

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

** Description changed:

+ [Impact]
+ 
  There are failed logs after resume from hibernation in NV6 (GPU passthrough 
size) VM in Azure:
  [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  
  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.
  
- How reproducible: 
+ [Test Case]
+ 
+ How reproducible:
  100%
  
  Steps to Reproduce:
  1. Start a Standard_NV6 VM in Azure and enable hibernation properly (please 
refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )
  
  E.g. here I create a Generation-1 Ubuntu 20.04 Standard NV6_Promo (6
  vcpus, 56 GiB memory) VM in East US 2.
  
  2. Make sure the in-kernel open-source nouveau driver is loaded, or
  blacklist the nouveau driver and install the official Nvidia GPU driver
  (please follow https://docs.microsoft.com/en-us/azure/virtual-
  machines/linux/n-series-driver-setup : "Install GRID drivers on NV or
  NVv3-series VMs" -- the most important step to run the "./NVIDIA-Linux-
  x86_64-grid.run".)
  
  3. Run hibernation from serial console
  # systemctl hibernate
  
  4. After hibernation finishes, start VM and check dmesg
  # dmesg|grep fail
  
  Actual results:
  [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  
  And /proc/interrupts shows that the GPU interrupts are no longer
  happening.
  
  Expected results:
  No failed logs, and the GPU interrupt should still happen after hibernation.
  
+ [Regression Potential]
+ 
+ The fix touches the pci-hyperv and can compromise the hyper-v guest
+ drivers. However the change is focuses on the execution path used for
+ hibernation that is still not officially supported.
+ 
+ [Other info]
  
  BUG FIX:
  I made a fix here: https://lkml.org/lkml/2020/9/4/1268.
  
  Without the patch, we see the error "hv_pci
  47505500-0001--3130-444531334632: hv_irq_unmask() failed: 0x5"
  during hibernation when the VM has the Nvidia GPU driver loaded, and
  after hibernation the GPU driver can no longer receive any MSI/MSI-X
  interrupts when we check /proc/interrupts.
  
  With the patch, we should no longer see the error, and the GPU driver
  should still receive interrupts after hibernation.

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

Title:
  [linux-azure][hibernation] GPU device no longer working after resume
  from hibernation in NV6 VM size

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Groovy:
  In Progress

Bug description:
  [Impact]

  There are failed logs after resume from hibernation in NV6 (GPU passthrough 
size) VM in Azure:
  [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5

  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.

  [Test Case]

  How reproducible:
  100%

  Steps to Reproduce:
  1. Start a Standard_NV6 VM in Azure and enable hibernation properly (please 
refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )

  E.g. here I create a Generation-1 Ubuntu 20.04 Standard NV6_Promo (6
  vcpus, 56 GiB memory) VM in East US 2.

  2. Make sure the in-kernel open-source nouveau driver is loaded, or
  blacklist the nouveau driver and install the official Nvidia GPU
  driver (please follow https://docs.microsoft.com/en-us/azure/virtual-
  machines/linux/n-series-driver-setup : "Install GRID drivers on NV or
  NVv3-series VMs" -- the most important step to run the "./NVIDIA-
  Linux-x86_64-grid.run".)

  3. Run hibernation from serial console
  # systemctl hibernate

  4. After hibernation finishes, start VM and check dmesg
  # dmesg|grep fail

  Actual results:
  [ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5
  [ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask() 
failed: 0x5

  And /proc/interrupts shows that the GPU interrupts are no longer
  happening.

  Expected results:
  No failed logs, 

[Kernel-packages] [Bug 1901125] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne

2020-10-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Wifi adapter isn't working after the update

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7
  Uname: Linux 5.9.1-050901-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  AptOrdering:
   bcmwl-kernel-source:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 10:10:48 2020
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-03-14 (222 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (0 days ago)

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

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


[Kernel-packages] [Bug 1901125] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne

2020-10-23 Thread Eduardo Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Wifi adapter isn't working after the update

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7
  Uname: Linux 5.9.1-050901-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  AptOrdering:
   bcmwl-kernel-source:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 10:10:48 2020
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-03-14 (222 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (0 days ago)

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

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


[Kernel-packages] [Bug 1894895] Re: [linux-azure][hibernation] ]VM hangs after hibernation/resume if the VM has SRIOV NIC and has been deallocated

2020-10-23 Thread Marcelo Cerri
5.8 already received the fix by upstream stable updates (LP:#1896795)
and hibernation is not supported in 4.15, because of that I'm targeting
only 5.4.

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

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

** Description changed:

+ [Impact]
+ 
  Description of problem:
  On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's 
VMBus Instance GUID may change, and as a result hibernation/resume can hang 
forever.
  
  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.
+ 
+ [Test Case]
  
  How reproducible:
  100%
  
  Steps to Reproduce:
  1. Start a VM in Azure that supports Accelerated Networking, and enable 
hibernation properly (please refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )
  
  2. Do hibernation from serial console
  # systemctl hibernate
  
  4. After the VM state changes to "Stopped", click "Stop" button from
  Azure portal to change the VM state to Stopped(deallocated)
  
  5. Wait for some time (e.g. 10 minutes? 1 hour?), and click the "Start"
  button to start the VM, and then check the boot-up process from the
  serial console.
  
  Actual results:
  Can not boot up. VM hangs after resume.
  
  Starting Resume from hibernation us…6c7-2c0c-491e-adcf-b625d69faf76...
  [   19.822747] PM: resume from hibernation
  [   19.836693] Freezing user space processes ... (elapsed 0.003 seconds) done.
  [   19.846968] OOM killer disabled.
  [   19.850236] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [   20.542934] PM: Using 1 thread(s) for decompression
  [   20.548250] PM: Loading and decompressing image data (559580 pages)...
  [   22.844964] PM: Image loading progress:   0%
  [   28.131327] PM: Image loading progress:  10%
  [   32.346480] PM: Image loading progress:  20%
  [   37.453971] PM: Image loading progress:  30%
  [   40.834525] PM: Image loading progress:  40%
  [   42.980629] PM: Image loading progress:  50%
  [   44.342959] PM: Image loading progress:  60%
  [   45.506197] PM: Image loading progress:  70%
  [   46.800445] PM: Image loading progress:  80%
  [   48.010185] PM: Image loading progress:  90%
  [   49.045671] PM: Image loading done
  [   49.050419] PM: Read 2238320 kbytes in 28.48 seconds (78.59 MB/s)
  [   49.074198] printk: Suspending console(s) (use no_console_suspend to debug)
  
  (The VM hangs here forever)
  
+ [Regression Potential]
+ 
+ The fix touched the vmbus and can compromise the hyper-v guest drivers.
+ However the change is simple and just adds an additional timeout.
+ 
+ [Other info]
+ 
  BUG FIX:
  A workaround patch is available and is being reviewed: 
https://lkml.org/lkml/2020/9/4/1270
+ 
+ Final fix:
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19873eec7e13fda140a0ebc75d6664e57c00bfb1

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

Title:
  [linux-azure][hibernation] ]VM hangs after hibernation/resume if the
  VM has SRIOV NIC and has been deallocated

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  [Impact]

  Description of problem:
  On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's 
VMBus Instance GUID may change, and as a result hibernation/resume can hang 
forever.

  This happens to the latest stable release of the linux-azure
  5.4.0-1023.23 kernel and the latest mainline linux kernel.

  [Test Case]

  How reproducible:
  100%

  Steps to Reproduce:
  1. Start a VM in Azure that supports Accelerated Networking, and enable 
hibernation properly (please refer to 
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/comments/14 )

  2. Do hibernation from serial console
  # systemctl hibernate

  4. After the VM state changes to "Stopped", click "Stop" button from
  Azure portal to change the VM state to Stopped(deallocated)

  5. Wait for some time (e.g. 10 minutes? 1 hour?), and click the
  "Start" button to start the VM, and then check the boot-up process
  from the serial console.

  Actual results:
  Can not boot up. VM hangs after resume.

  Starting Resume from hibernation us…6c7-2c0c-491e-adcf-b625d69faf76...
  [   19.822747] PM: resume from hibernation
  [   19.836693] Freezing user space processes ... (elapsed 0.003 seconds) done.
  [   19.846968] OOM killer disabled.
  [   19.850236] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [   20.542934] PM: Using 1 thread(s) for decompression
  [   20.548250] PM: Loading and decompressing image data (559580 pages)...
  [   22.844964] PM: Image loading progress:   0%
  [   28.131327] PM: Image loading progress:  10%
  [   

[Kernel-packages] [Bug 1901231] Re: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread Peter Buck
Recovered by booting into an older kernel and running

sudo update-initramfs -u -k 5.8.0-25-generic
sudo update-grub

There are still some initialization failures reported at boot but at
least the 20.10 boot is successful.

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  inadvertently killed upgrade from fosa to gorilla.  Result won't boot:
  "VFS: Unable to mount root fs on unknown-block(0,0) ]--"

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1838 F pulseaudio
   /dev/snd/controlC2:  peter  1838 F pulseaudio
   /dev/snd/controlC1:  peter  1838 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 12:53:07 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-10-22 (731 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=6a885885-4d9c-4d7d-abc9-70fa839e1635 ro quiet splash 
acpi_backlight=vendor
  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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-23 Thread Piotr Tomaszewski
@Christian (chris-svn),
Glad to help :)

@Coiby Xu (coiby),
Hey Sir, is there easy way to apply this patch on Ubuntu/PopOS distro without 
build whole 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/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  

[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed

2020-10-23 Thread Steve Paynter
Same bug as #1835660?

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

Title:
  [ 0.00] Initramfs unpacking failed: Decoding failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download MATE Groovy daily (sha256sum = 
7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 )
  2. Insert ISO into VirtualBox with EFI enabled
  3. Boot VM

  Expected results:
  * VM boots normally

  Actual results:
  * VM hangs during early boot with message

    [ 0.00] Initramfs unpacking failed: Decoding failed

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

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


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

2020-10-23 Thread 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/1901231

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  inadvertently killed upgrade from fosa to gorilla.  Result won't boot:
  "VFS: Unable to mount root fs on unknown-block(0,0) ]--"

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1838 F pulseaudio
   /dev/snd/controlC2:  peter  1838 F pulseaudio
   /dev/snd/controlC1:  peter  1838 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 12:53:07 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-10-22 (731 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=6a885885-4d9c-4d7d-abc9-70fa839e1635 ro quiet splash 
acpi_backlight=vendor
  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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1901231] Re: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  inadvertently killed upgrade from fosa to gorilla.  Result won't boot:
  "VFS: Unable to mount root fs on unknown-block(0,0) ]--"

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1838 F pulseaudio
   /dev/snd/controlC2:  peter  1838 F pulseaudio
   /dev/snd/controlC1:  peter  1838 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 12:53:07 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-10-22 (731 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=6a885885-4d9c-4d7d-abc9-70fa839e1635 ro quiet splash 
acpi_backlight=vendor
  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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1901231] [NEW] package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to install/upgrade: triggers looping, abandoned

2020-10-23 Thread Peter Buck
Public bug reported:

inadvertently killed upgrade from fosa to gorilla.  Result won't boot:
"VFS: Unable to mount root fs on unknown-block(0,0) ]--"

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  peter  1838 F pulseaudio
 /dev/snd/controlC2:  peter  1838 F pulseaudio
 /dev/snd/controlC1:  peter  1838 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Oct 23 12:53:07 2020
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-10-22 (731 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=6a885885-4d9c-4d7d-abc9-70fa839e1635 ro quiet splash 
acpi_backlight=vendor
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.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu35
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package groovy

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

Title:
  package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  inadvertently killed upgrade from fosa to gorilla.  Result won't boot:
  "VFS: Unable to mount root fs on unknown-block(0,0) ]--"

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1838 F pulseaudio
   /dev/snd/controlC2:  peter  1838 F pulseaudio
   /dev/snd/controlC1:  peter  1838 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 12:53:07 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-10-22 (731 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=6a885885-4d9c-4d7d-abc9-70fa839e1635 ro quiet splash 
acpi_backlight=vendor
  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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.8.0-25-generic 5.8.0-25.26 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  

[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed

2020-10-23 Thread Steve Paynter
Update: Nope, the machine isn't dead at that point:

* Das blinken licht (well hidden) on the USB stick, blinkens for 35 secs.
* The laptop fan starts up.
* A four-note tune plays.

And then nothing.

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

Title:
  [ 0.00] Initramfs unpacking failed: Decoding failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download MATE Groovy daily (sha256sum = 
7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 )
  2. Insert ISO into VirtualBox with EFI enabled
  3. Boot VM

  Expected results:
  * VM boots normally

  Actual results:
  * VM hangs during early boot with message

    [ 0.00] Initramfs unpacking failed: Decoding failed

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

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


[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed

2020-10-23 Thread Steve Paynter
Got this bug too.

Steps to reproduce:

1. Download ubuntu-20.04.1-desktop-amd64.iso and verify.
2. Install onto USB stick using Startup Disk Creator.
3. Boot machine from USB stick.

Expected results:
- Machine boots into live Ubuntu.

Actual results:
1. BIOS stuff, as per usual.
2. Grub 2.04 screen, boots "Ubuntu" option by default after a few seconds.
3. Machine hangs with message "[0.XX] Initramfs unpacking failed: Decoding 
failed" (where XX is a different number each time).
   This message is always followed by 5 lines of really tiny text, completely 
unreadable on my 4k screen.
   Machine now appears to be dead, except that:
   - On one occasion, hitting Enter caused screen to fill with more unreadable 
tiny text.
   - On another occasion, after a minute of me doing nothing, machine played a 
short chip tune!
   
Machine config:
- Lenovo Thinkpad X1 Extreme, Gen 2, one year old.
- UEFI BIOS Version: N2oet47w (1.34), 2020-08-06.
- Firmware is current (as per Lenovo Vantage check, done several days ago).
- My BIOS security settings are maxxed out.

Notes:
- I tried with Secure Boot enabled and disabled; made no difference.
- Machine boots fine into a very recent Ubuntu 20.10 beta, using same laptop 
and USB stick. (Unfortunately, the ROS software won't work on 20.10 yet.)
- Just repeating: all was fine with Ubuntu 20.10 beta. But fails with 20.04.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/1886769

Title:
  [ 0.00] Initramfs unpacking failed: Decoding failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download MATE Groovy daily (sha256sum = 
7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 )
  2. Insert ISO into VirtualBox with EFI enabled
  3. Boot VM

  Expected results:
  * VM boots normally

  Actual results:
  * VM hangs during early boot with message

    [ 0.00] Initramfs unpacking failed: Decoding failed

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

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


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

2020-10-23 Thread 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/1901215

Title:
  Cannot boot with thunderbolt dock connected before kernel loads

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays
  through the dock (HDMI and VGA). My system uses graphical boot via
  plymouth. Dell logo remains on screen while ubuntu loads into gdm3
  (when it is booting normally). I'm using LUKS.

  This is a regression from focal and kernel 5.4.

  If I boot the laptop with the thunderbolt dock connected, the system
  will get past the Dell logo, go to a black screen and remain there.
  The screen is powered up as I can see some light on the edges. It
  won't boot up or respond to any keys.

  After force-shutdown via power key long press, on the next boot the
  grub menu will appear. The system will boot normally then (with the
  dock still connected).

  If I boot the system with the dock disconnected, it will correctly go
  into disk encryption password prompt. If at that point I connect the
  dock and wait without entering the password, the system will correctly
  set up the dock: the displays lit up and the mouse and keyboard
  plugged into it become active. The system boots normally.

  I'm trying to bisect in which kernel version this happened. I'll put
  results in a comment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-generic 5.8.0.25.30
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  luis   3332 F pulseaudio
   /dev/snd/controlC0:  luis   3332 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 16:27:30 2020
  InstallationDate: Installed on 2019-08-17 (432 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=/dev/mapper/vglinux-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1901215] [NEW] Cannot boot with thunderbolt dock connected before kernel loads

2020-10-23 Thread Luis Alberto Pabón
Public bug reported:

Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through
the dock (HDMI and VGA). My system uses graphical boot via plymouth.
Dell logo remains on screen while ubuntu loads into gdm3 (when it is
booting normally). I'm using LUKS.

This is a regression from focal and kernel 5.4.

If I boot the laptop with the thunderbolt dock connected, the system
will get past the Dell logo, go to a black screen and remain there. The
screen is powered up as I can see some light on the edges. It won't boot
up or respond to any keys.

After force-shutdown via power key long press, on the next boot the grub
menu will appear. The system will boot normally then (with the dock
still connected).

If I boot the system with the dock disconnected, it will correctly go
into disk encryption password prompt. If at that point I connect the
dock and wait without entering the password, the system will correctly
set up the dock: the displays lit up and the mouse and keyboard plugged
into it become active. The system boots normally.

I'm trying to bisect in which kernel version this happened. I'll put
results in a comment.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-generic 5.8.0.25.30
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  luis   3332 F pulseaudio
 /dev/snd/controlC0:  luis   3332 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Oct 23 16:27:30 2020
InstallationDate: Installed on 2019-08-17 (432 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=/dev/mapper/vglinux-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-25-generic N/A
 linux-backports-modules-5.8.0-25-generic  N/A
 linux-firmware1.190
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug groovy third-party-packages

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

Title:
  Cannot boot with thunderbolt dock connected before kernel loads

Status in linux package in Ubuntu:
  New

Bug description:
  Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays
  through the dock (HDMI and VGA). My system uses graphical boot via
  plymouth. Dell logo remains on screen while ubuntu loads into gdm3
  (when it is booting normally). I'm using LUKS.

  This is a regression from focal and kernel 5.4.

  If I boot the laptop with the thunderbolt dock connected, the system
  will get past the Dell logo, go to a black screen and remain there.
  The screen is powered up as I can see some light on the edges. It
  won't boot up or respond to any keys.

  After force-shutdown via power key long press, on the next boot the
  grub menu will appear. The system will boot normally then (with the
  dock still connected).

  If I boot the system with the dock disconnected, it will correctly go
  into disk encryption password prompt. If at that point I connect the
  dock and wait without entering the password, the system will correctly
  set up the dock: the displays lit up and the mouse and keyboard
  plugged into it become active. The system boots normally.

  I'm trying to bisect in which kernel version this happened. I'll put
  results in a comment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-generic 5.8.0.25.30
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  luis   3332 F pulseaudio
   /dev/snd/controlC0:  luis   3332 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 16:27:30 2020
  InstallationDate: Installed on 2019-08-17 (432 days ago)
  InstallationMedia: 

[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load

2020-10-23 Thread Colin Ian King
OK, I'll close this bug for now. If it still bites please feel free to
re-open the bug and I'll get back onto it.

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => 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/1899249

Title:
  OpenZFS writing stalls, under load

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry
  Pi 8GB. ZFS deduplication, and LZJB compression is enabled.

  This issue seems to occur, intermittently, after some time (happens
  with both SMB access, via Samba, and when interacting with the system,
  via SSH), and never previously occurred, until a few months ago, and I
  sometimes have to force a reboot of the system (at the cost of some
  data loss), in order to use it again.

  The "dmesg" log reports:

  [25375.911590] z_wr_iss_h  D0  2161  2 0x0028
  [25375.911606] Call trace:
  [25375.911627]  __switch_to+0x104/0x170
  [25375.911639]  __schedule+0x30c/0x7c0
  [25375.911647]  schedule+0x3c/0xb8
  [25375.911655]  io_schedule+0x20/0x58
  [25375.911668]  rq_qos_wait+0x100/0x178
  [25375.911677]  wbt_wait+0xb4/0xf0
  [25375.911687]  __rq_qos_throttle+0x38/0x50
  [25375.911700]  blk_mq_make_request+0x128/0x610
  [25375.911712]  generic_make_request+0xb4/0x2d8
  [25375.911722]  submit_bio+0x48/0x218
  [25375.911960]  vdev_disk_io_start+0x670/0x9f8 [zfs]
  [25375.912181]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
  [25375.912400]  zio_nowait+0xd4/0x170 [zfs]
  [25375.912617]  vdev_mirror_io_start+0xa8/0x1b0 [zfs]
  [25375.912839]  zio_vdev_io_start+0x248/0x2b8 [zfs]
  [25375.913057]  zio_execute+0xac/0x110 [zfs]
  [25375.913096]  taskq_thread+0x2f8/0x570 [spl]
  [25375.913108]  kthread+0xfc/0x128
  [25375.913119]  ret_from_fork+0x10/0x1c
  [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds.
  [25375.919916]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.934835] txg_syncD0  2333  2 0x0028
  [25375.934850] Call trace:
  [25375.934869]  __switch_to+0x104/0x170
  [25375.934879]  __schedule+0x30c/0x7c0
  [25375.934887]  schedule+0x3c/0xb8
  [25375.934899]  schedule_timeout+0x9c/0x190
  [25375.934908]  io_schedule_timeout+0x28/0x48
  [25375.934946]  __cv_timedwait_common+0x1a8/0x1f8 [spl]
  [25375.934982]  __cv_timedwait_io+0x3c/0x50 [spl]
  [25375.935205]  zio_wait+0x130/0x2a0 [zfs]
  [25375.935423]  dsl_pool_sync+0x3fc/0x498 [zfs]
  [25375.935650]  spa_sync+0x538/0xe68 [zfs]
  [25375.935867]  txg_sync_thread+0x2c0/0x468 [zfs]
  [25375.935911]  thread_generic_wrapper+0x74/0xa0 [spl]
  [25375.935924]  kthread+0xfc/0x128
  [25375.935935]  ret_from_fork+0x10/0x1c
  [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds.
  [25375.942780]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.957702] zbackup D0 75339   5499 0x
  [25375.957716] Call trace:
  [25375.957732]  __switch_to+0x104/0x170
  [25375.957742]  __schedule+0x30c/0x7c0
  [25375.957750]  schedule+0x3c/0xb8
  [25375.957789]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.957823]  __cv_wait+0x30/0x40 [spl]
  [25375.958045]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.958263]  zil_commit+0x48/0x70 [zfs]
  [25375.958481]  zfs_create+0x544/0x7d0 [zfs]
  [25375.958698]  zpl_create+0xb8/0x178 [zfs]
  [25375.958711]  lookup_open+0x4ec/0x6a8
  [25375.958721]  do_last+0x260/0x8c0
  [25375.958730]  path_openat+0x84/0x258
  [25375.958739]  do_filp_open+0x84/0x108
  [25375.958752]  do_sys_open+0x180/0x2b0
  [25375.958763]  __arm64_sys_openat+0x2c/0x38
  [25375.958773]  el0_svc_common.constprop.0+0x80/0x218
  [25375.958781]  el0_svc_handler+0x34/0xa0
  [25375.958791]  el0_svc+0x10/0x2cc
  [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds.
  [25375.965564]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.980479] zbackup D0 95187   5499 0x
  [25375.980493] Call trace:
  [25375.980514]  __switch_to+0x104/0x170
  [25375.980525]  __schedule+0x30c/0x7c0
  [25375.980536]  schedule+0x3c/0xb8
  [25375.980578]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.980612]  __cv_wait+0x30/0x40 [spl]
  [25375.980834]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.981052]  zil_commit+0x48/0x70 [zfs]
  [25375.981280]  zfs_write+0xa3c/0xb90 [zfs]
  [25375.981498]  zpl_write_common_iovec+0xac/0x120 [zfs]
  [25375.981726]  zpl_iter_write+0xe4/0x150 [zfs]
  [25375.981766]  new_sync_write+0x100/0x1a8
  [25375.981776]  __vfs_write+0x74/0x90
  

[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load

2020-10-23 Thread Tyson Key
Thanks, Colin. I intend to retest, with 20.10, but for now, with
deduplication disabled, things seem stable.

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

Title:
  OpenZFS writing stalls, under load

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry
  Pi 8GB. ZFS deduplication, and LZJB compression is enabled.

  This issue seems to occur, intermittently, after some time (happens
  with both SMB access, via Samba, and when interacting with the system,
  via SSH), and never previously occurred, until a few months ago, and I
  sometimes have to force a reboot of the system (at the cost of some
  data loss), in order to use it again.

  The "dmesg" log reports:

  [25375.911590] z_wr_iss_h  D0  2161  2 0x0028
  [25375.911606] Call trace:
  [25375.911627]  __switch_to+0x104/0x170
  [25375.911639]  __schedule+0x30c/0x7c0
  [25375.911647]  schedule+0x3c/0xb8
  [25375.911655]  io_schedule+0x20/0x58
  [25375.911668]  rq_qos_wait+0x100/0x178
  [25375.911677]  wbt_wait+0xb4/0xf0
  [25375.911687]  __rq_qos_throttle+0x38/0x50
  [25375.911700]  blk_mq_make_request+0x128/0x610
  [25375.911712]  generic_make_request+0xb4/0x2d8
  [25375.911722]  submit_bio+0x48/0x218
  [25375.911960]  vdev_disk_io_start+0x670/0x9f8 [zfs]
  [25375.912181]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
  [25375.912400]  zio_nowait+0xd4/0x170 [zfs]
  [25375.912617]  vdev_mirror_io_start+0xa8/0x1b0 [zfs]
  [25375.912839]  zio_vdev_io_start+0x248/0x2b8 [zfs]
  [25375.913057]  zio_execute+0xac/0x110 [zfs]
  [25375.913096]  taskq_thread+0x2f8/0x570 [spl]
  [25375.913108]  kthread+0xfc/0x128
  [25375.913119]  ret_from_fork+0x10/0x1c
  [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds.
  [25375.919916]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.934835] txg_syncD0  2333  2 0x0028
  [25375.934850] Call trace:
  [25375.934869]  __switch_to+0x104/0x170
  [25375.934879]  __schedule+0x30c/0x7c0
  [25375.934887]  schedule+0x3c/0xb8
  [25375.934899]  schedule_timeout+0x9c/0x190
  [25375.934908]  io_schedule_timeout+0x28/0x48
  [25375.934946]  __cv_timedwait_common+0x1a8/0x1f8 [spl]
  [25375.934982]  __cv_timedwait_io+0x3c/0x50 [spl]
  [25375.935205]  zio_wait+0x130/0x2a0 [zfs]
  [25375.935423]  dsl_pool_sync+0x3fc/0x498 [zfs]
  [25375.935650]  spa_sync+0x538/0xe68 [zfs]
  [25375.935867]  txg_sync_thread+0x2c0/0x468 [zfs]
  [25375.935911]  thread_generic_wrapper+0x74/0xa0 [spl]
  [25375.935924]  kthread+0xfc/0x128
  [25375.935935]  ret_from_fork+0x10/0x1c
  [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds.
  [25375.942780]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.957702] zbackup D0 75339   5499 0x
  [25375.957716] Call trace:
  [25375.957732]  __switch_to+0x104/0x170
  [25375.957742]  __schedule+0x30c/0x7c0
  [25375.957750]  schedule+0x3c/0xb8
  [25375.957789]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.957823]  __cv_wait+0x30/0x40 [spl]
  [25375.958045]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.958263]  zil_commit+0x48/0x70 [zfs]
  [25375.958481]  zfs_create+0x544/0x7d0 [zfs]
  [25375.958698]  zpl_create+0xb8/0x178 [zfs]
  [25375.958711]  lookup_open+0x4ec/0x6a8
  [25375.958721]  do_last+0x260/0x8c0
  [25375.958730]  path_openat+0x84/0x258
  [25375.958739]  do_filp_open+0x84/0x108
  [25375.958752]  do_sys_open+0x180/0x2b0
  [25375.958763]  __arm64_sys_openat+0x2c/0x38
  [25375.958773]  el0_svc_common.constprop.0+0x80/0x218
  [25375.958781]  el0_svc_handler+0x34/0xa0
  [25375.958791]  el0_svc+0x10/0x2cc
  [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds.
  [25375.965564]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.980479] zbackup D0 95187   5499 0x
  [25375.980493] Call trace:
  [25375.980514]  __switch_to+0x104/0x170
  [25375.980525]  __schedule+0x30c/0x7c0
  [25375.980536]  schedule+0x3c/0xb8
  [25375.980578]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.980612]  __cv_wait+0x30/0x40 [spl]
  [25375.980834]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.981052]  zil_commit+0x48/0x70 [zfs]
  [25375.981280]  zfs_write+0xa3c/0xb90 [zfs]
  [25375.981498]  zpl_write_common_iovec+0xac/0x120 [zfs]
  [25375.981726]  zpl_iter_write+0xe4/0x150 [zfs]
  [25375.981766]  new_sync_write+0x100/0x1a8
  [25375.981776]  __vfs_write+0x74/0x90
  [25375.981784]  vfs_write+0xe4/0x1c8
  [25375.981794]  ksys_write+0x78/0x100
  

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-23 Thread Christian
@Coiby Xu (coiby)
Thank you very much for the patch in #189. It works like a charm.

@Piotr Tomaszewski (nfm886)
Thanks for posting your solution in #201. I was in the exact same situation and 
without it, I would probably still be wondering why it didnt work for me.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 

[Kernel-packages] [Bug 1901024] Re: Crash on startup using linux 5.8.0-25

2020-10-23 Thread Mauricio Faria de Oliveira
Hi Rauno,

Thanks for reporting this bug; nice finding on pci=noats.

$ grep -A1 noats ~/git/linux/Documentation/admin-guide/kernel-parameters.txt 
noats   [PCIE, Intel-IOMMU, AMD-IOMMU]
do not use PCIe ATS (and IOMMU device IOTLB).


Wondering if the amd gfx drivers with ats/iommu (ie, w/out pci=noats) causes 
memory corruption:

The screenshot in #1 shows that initramfs unpacking failed -- say,
something corrupted the compressed initramfs image loaded in memory --
and this happened closely to when AMD-Vi failed to access an IOMMU perf
count(er? I guess.)

And it seems to be graphics related, not just ats/iommu code alone,
which prints 'AMD-Vi' (it's in linux/drivers/iommu/amd/) since recovery
mode, with 'nomodeset', works fine.

When you boot in recovery mode, do you see initramfs unpacking failed as
well? (please check 'dmesg | grep -i initramfs')

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

Title:
  Crash on startup using linux 5.8.0-25

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my new Lenovo ThinkPad L15 and upgraded it to 
Ubuntu 20.10 for a newer kernel to fix minor compatibility issues with AMD 
Renoir.
  When using the newer kernel it freezes before splash. I did my best to follow 
instructions to create a crash file but none were ever created.
  Booting to recovery mode with 5.8 works, 5.4 kernel works. Booting from USB 
the (safe graphics) option works but not the default. On that USB I have latest 
available daily build (Oct 21 2020) of 20.10. I tried a fresh reinstall of 
Ubuntu 20.10 and still getting stuck.

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

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


[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-10-23 Thread Seamus Ryan
Ok yup this is almost certainly the issue (when the tunnel is pi is
tunnelling traffic for something other than itself)

My tunnel has been up for 12 hours, no crashes at all.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
 

[Kernel-packages] [Bug 1901024] Re: Crash on startup using linux 5.8.0-25

2020-10-23 Thread Rauno
For some reason switching to amd graphics drivers caused the crash. Also
for some reason grub boot option pci=noats fixes it.

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

Title:
  Crash on startup using linux 5.8.0-25

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my new Lenovo ThinkPad L15 and upgraded it to 
Ubuntu 20.10 for a newer kernel to fix minor compatibility issues with AMD 
Renoir.
  When using the newer kernel it freezes before splash. I did my best to follow 
instructions to create a crash file but none were ever created.
  Booting to recovery mode with 5.8 works, 5.4 kernel works. Booting from USB 
the (safe graphics) option works but not the default. On that USB I have latest 
available daily build (Oct 21 2020) of 20.10. I tried a fresh reinstall of 
Ubuntu 20.10 and still getting stuck.

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

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


[Kernel-packages] [Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port

2020-10-23 Thread Marc H.
Maybe the issue is heat, and the chip slows down of it overheats, and
some manufacturers did not include a heatsink on it, some did.

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

Title:
  0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device
  on USB3 port

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

Bug description:
  Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in
  USB3 port yields slow performance, dmesg flooded with errors. Plugging
  on USB2 port, exact same situation otherwise, works well. This is
  reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the
  left, 2 USB2 ports on the right.

  ### When working (USB2 port)
  * ethernet auto-negociation is fast
  * mii-tool is fast (typical 0.05s)
  * few lines in dmesg
  * good performance

  ### When failing :
  * ethernet auto-negociation fails, then sometimes eventually works
  * mii-tool is slow (10s of seconds instead of 0.05s)

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m40.014s
  user  0m0.013s
  sys   0m0.006s

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m50.015s
  user  0m0.011s
  sys   0m0.011s

  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m10.051s
  user  0m0.000s
  sys   0m0.012s

  But on some attempts mii-tool is fast...
  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m0.057s
  user  0m0.011s
  sys   0m0.012s

  * DHCP eventually completes (after about 30 seconds) then ethernet works.
  * whole system behaviour feels a little sluggish (not very clear, though)
  * mii-tool still slow (10s of seconds instead of 0.05s)

  ## dmesg when failing

  Full dmesg attached.

  Specific lines with occurrence count at random point (obtained with
  "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ).

   50 ei_me :00:16.0: reset: wrong host start response
   51 ei_me :00:16.0: reset: unexpected enumeration response hbm.
   60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING
  141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Another attempt

   11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
   61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
   61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1
  925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD

    5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110
    6 net_ratelimit: 31 callbacks suppressed
    9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
   10 net_ratelimit: 30 callbacks suppressed
   14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
  232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203182.075364] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.199491] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203182.199504] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:37 n55sf-l kernel: [203182.944174] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:37 n55sf-l kernel: [203182.944178] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command 

[Kernel-packages] [Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port

2020-10-23 Thread Marc H.
Just found by Google search to this post. I have the same issue on
Windows 10 with a AX88179 adapter. The adapter randomly crashes / driver
crashes under heavy load or the bandwidth suddenly drops down from
500mbit/s to around 3mbit/s. You can see the issue happening here:

https://i.imgur.com/TtWRpAE.gif

So it doesnt seem to be a Linux only issue at all. I am using the latest
driver on Windows by Asix 1.20.7.0 which doesnt do anything for this
issue.

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

Title:
  0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device
  on USB3 port

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

Bug description:
  Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in
  USB3 port yields slow performance, dmesg flooded with errors. Plugging
  on USB2 port, exact same situation otherwise, works well. This is
  reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the
  left, 2 USB2 ports on the right.

  ### When working (USB2 port)
  * ethernet auto-negociation is fast
  * mii-tool is fast (typical 0.05s)
  * few lines in dmesg
  * good performance

  ### When failing :
  * ethernet auto-negociation fails, then sometimes eventually works
  * mii-tool is slow (10s of seconds instead of 0.05s)

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m40.014s
  user  0m0.013s
  sys   0m0.006s

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m50.015s
  user  0m0.011s
  sys   0m0.011s

  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m10.051s
  user  0m0.000s
  sys   0m0.012s

  But on some attempts mii-tool is fast...
  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m0.057s
  user  0m0.011s
  sys   0m0.012s

  * DHCP eventually completes (after about 30 seconds) then ethernet works.
  * whole system behaviour feels a little sluggish (not very clear, though)
  * mii-tool still slow (10s of seconds instead of 0.05s)

  ## dmesg when failing

  Full dmesg attached.

  Specific lines with occurrence count at random point (obtained with
  "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ).

   50 ei_me :00:16.0: reset: wrong host start response
   51 ei_me :00:16.0: reset: unexpected enumeration response hbm.
   60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING
  141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Another attempt

   11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
   61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
   61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1
  925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD

    5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110
    6 net_ratelimit: 31 callbacks suppressed
    9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
   10 net_ratelimit: 30 callbacks suppressed
   14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
  232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203182.075364] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.199491] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  

[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load

2020-10-23 Thread Colin Ian King
@Tyson, hopefully the WBT changes helped to resolve this issue.  If so,
please let me know and I can close this bug.

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

Title:
  OpenZFS writing stalls, under load

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry
  Pi 8GB. ZFS deduplication, and LZJB compression is enabled.

  This issue seems to occur, intermittently, after some time (happens
  with both SMB access, via Samba, and when interacting with the system,
  via SSH), and never previously occurred, until a few months ago, and I
  sometimes have to force a reboot of the system (at the cost of some
  data loss), in order to use it again.

  The "dmesg" log reports:

  [25375.911590] z_wr_iss_h  D0  2161  2 0x0028
  [25375.911606] Call trace:
  [25375.911627]  __switch_to+0x104/0x170
  [25375.911639]  __schedule+0x30c/0x7c0
  [25375.911647]  schedule+0x3c/0xb8
  [25375.911655]  io_schedule+0x20/0x58
  [25375.911668]  rq_qos_wait+0x100/0x178
  [25375.911677]  wbt_wait+0xb4/0xf0
  [25375.911687]  __rq_qos_throttle+0x38/0x50
  [25375.911700]  blk_mq_make_request+0x128/0x610
  [25375.911712]  generic_make_request+0xb4/0x2d8
  [25375.911722]  submit_bio+0x48/0x218
  [25375.911960]  vdev_disk_io_start+0x670/0x9f8 [zfs]
  [25375.912181]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
  [25375.912400]  zio_nowait+0xd4/0x170 [zfs]
  [25375.912617]  vdev_mirror_io_start+0xa8/0x1b0 [zfs]
  [25375.912839]  zio_vdev_io_start+0x248/0x2b8 [zfs]
  [25375.913057]  zio_execute+0xac/0x110 [zfs]
  [25375.913096]  taskq_thread+0x2f8/0x570 [spl]
  [25375.913108]  kthread+0xfc/0x128
  [25375.913119]  ret_from_fork+0x10/0x1c
  [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds.
  [25375.919916]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.934835] txg_syncD0  2333  2 0x0028
  [25375.934850] Call trace:
  [25375.934869]  __switch_to+0x104/0x170
  [25375.934879]  __schedule+0x30c/0x7c0
  [25375.934887]  schedule+0x3c/0xb8
  [25375.934899]  schedule_timeout+0x9c/0x190
  [25375.934908]  io_schedule_timeout+0x28/0x48
  [25375.934946]  __cv_timedwait_common+0x1a8/0x1f8 [spl]
  [25375.934982]  __cv_timedwait_io+0x3c/0x50 [spl]
  [25375.935205]  zio_wait+0x130/0x2a0 [zfs]
  [25375.935423]  dsl_pool_sync+0x3fc/0x498 [zfs]
  [25375.935650]  spa_sync+0x538/0xe68 [zfs]
  [25375.935867]  txg_sync_thread+0x2c0/0x468 [zfs]
  [25375.935911]  thread_generic_wrapper+0x74/0xa0 [spl]
  [25375.935924]  kthread+0xfc/0x128
  [25375.935935]  ret_from_fork+0x10/0x1c
  [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds.
  [25375.942780]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.957702] zbackup D0 75339   5499 0x
  [25375.957716] Call trace:
  [25375.957732]  __switch_to+0x104/0x170
  [25375.957742]  __schedule+0x30c/0x7c0
  [25375.957750]  schedule+0x3c/0xb8
  [25375.957789]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.957823]  __cv_wait+0x30/0x40 [spl]
  [25375.958045]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.958263]  zil_commit+0x48/0x70 [zfs]
  [25375.958481]  zfs_create+0x544/0x7d0 [zfs]
  [25375.958698]  zpl_create+0xb8/0x178 [zfs]
  [25375.958711]  lookup_open+0x4ec/0x6a8
  [25375.958721]  do_last+0x260/0x8c0
  [25375.958730]  path_openat+0x84/0x258
  [25375.958739]  do_filp_open+0x84/0x108
  [25375.958752]  do_sys_open+0x180/0x2b0
  [25375.958763]  __arm64_sys_openat+0x2c/0x38
  [25375.958773]  el0_svc_common.constprop.0+0x80/0x218
  [25375.958781]  el0_svc_handler+0x34/0xa0
  [25375.958791]  el0_svc+0x10/0x2cc
  [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds.
  [25375.965564]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.980479] zbackup D0 95187   5499 0x
  [25375.980493] Call trace:
  [25375.980514]  __switch_to+0x104/0x170
  [25375.980525]  __schedule+0x30c/0x7c0
  [25375.980536]  schedule+0x3c/0xb8
  [25375.980578]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.980612]  __cv_wait+0x30/0x40 [spl]
  [25375.980834]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.981052]  zil_commit+0x48/0x70 [zfs]
  [25375.981280]  zfs_write+0xa3c/0xb90 [zfs]
  [25375.981498]  zpl_write_common_iovec+0xac/0x120 [zfs]
  [25375.981726]  zpl_iter_write+0xe4/0x150 [zfs]
  [25375.981766]  new_sync_write+0x100/0x1a8
  [25375.981776]  __vfs_write+0x74/0x90
  [25375.981784]  vfs_write+0xe4/0x1c8
  [25375.981794]  ksys_write+0x78/0x100
  

[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome

2020-10-23 Thread Mike Gao
I got another wifi shutdown today, and therefore I'm moving to Fedora 33
with the latest kernel. Please close this issue.

I have also attached the dmesg message below.

** Attachment added: "err.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+attachment/5425911/+files/err.log

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

Title:
  Internet disconnected unexpectly + Xorg freeze while watching html5
  video in Chrome

Status in linux package in Ubuntu:
  In Progress

Bug description:
  A few issues:

  1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1,
  the system sometimes gets disconnected with the network and I get the
  following error in syslog:

  iwlwifi: BIOS contains WGDS but no WRDS

  It is unclear if this is the cause of the problem, but this is likely
  related to kernel.

  2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will
  sometimes cause xorg freeze. The exact cause is unknown. (Mouse,
  control all freeze for 5-10 seconds)

  3) After Wake up from sleep got the following error on screen

  sof-audio-pci error: no reply expected, received 0x0
  iwlwifi: BIOS contains WGDS but no WRDS

  4) After wake up from a long sleep session, sometimes chrome will not
  render web page correctly or even freeze. It is unclear if its a
  Chrome problem, or a Nvidia problem, or a Kernel Problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-47-generic 5.4.0-47.51
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gao1931 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 09:14:36 2020
  InstallationDate: Installed on 2020-08-25 (19 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 7591
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-47-generic N/A
   linux-backports-modules-5.4.0-47-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0JKGD4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7591
  dmi.product.sku: 0923
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2020-10-23 Thread bluppfisk
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Same issue. Had some promising results with pali's branch of pulseaudio
which contains fixes for HSP/HFP profiles. But then a
pulseaudio/kernel/idk update borked it all and I don't have the mental
bandwidth to try it all again.

https://gitlab.freedesktop.org/pali/pulseaudio

Kernel v 5.9.1 (but all previous versions I tried had the same issue)
Ubuntu 20.04
XPS 13 9300
Sony WH-1000XM3

-- 
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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-23 Thread PEDRO PORTO BUARQUE DE GUSMAO
Hi,

Can I do this with Secure Boot on?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 

[Kernel-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

2020-10-23 Thread Kurt Aaholst
There is now an official 20.04 for the XPS-13-9300 which does not have
this issue.

You may close this bug if you like.

Thanks again.

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

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

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

  Extract of syslog is attached.

  Requested info is below:

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

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

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions

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


[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

2020-10-23 Thread You-Sheng Yang
Wifi firmware blobs are identical to those in
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-
firmware.git/commit/?h=ath10k-20201022=60cb7a28a5dce0b7da88498ee752d30b692090ba
.

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

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

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

Bug description:
  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1842 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enx00e04c6801fa  no wireless extensions.
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=580a1e2b-9a42-4f3b-b20f-ddbed7b572f5 ro
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1010-oem N/A
   linux-backports-modules-5.6.0-1010-oem  N/A
   linux-firmware  1.187+lp1867862.1
  RfKill:

  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 05/14/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.9
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.9:bd05/14/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions

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


[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2020-10-23 Thread Adam Niedling
** Tags added: groovy

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-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 sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-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 sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1899586] Re: Fix broken MSI interrupt after HDA controller was suspended

2020-10-23 Thread Stefan Bader
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-oem-5.6 (Ubuntu Focal)

** 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)
   Importance: Undecided => Medium

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => Fix Released

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

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

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

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

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

Title:
  Fix broken MSI interrupt after HDA controller was suspended

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

Bug description:
  [Impact]
  After HDA controller gets suspended and resumed, no MSI interrupt raised
  when plugging headset to the audio jack.

  [Fix]
  Power up the Realtek codec when HDA controller runtime resumes.

  [Test]
  1) Make sure both codec and HDA controller are runtime suspended.
  2) Runtime resume the HDA controller without runtime resume the codec.
  3) Plug a headset and see if the system can detect anything.

  With the fix applied, we can see azx_interrupt() is working again by
  using ftrace.

  [Regression Potential]
  If there's any system that is not affected by this issue, runtime-resume
  the HDA controller will take a slightly longer time. It's rather
  unlikely, since _all_ systems with Realtek codec we tested have this
  issue, regardless of AMD or Intel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899586/+subscriptions

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


[Kernel-packages] [Bug 1898865] Re: Enable brightness control on HP DreamColor panel

2020-10-23 Thread Stefan Bader
** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Enable brightness control on HP DreamColor panel

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

Bug description:
  [Impact]
  Brightness on HP DreamColor panel, which can be found on new HP Zbook
  Studio, cannot be changed.

  [Fix]
  Let DRM know the panel should use DPCD instead of PWM to control
  backlight.
   
  [Test]  
  With the patch applied, we can change the brightness on HP Zbook Studio.

  [Regression Potential]
  If there's any panel in the quirk list depends on checking brightness
  control capability then this change will have an impact. However it's 
  rather unlikely because it defeats the purpose of the quirk list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1898865/+subscriptions

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


[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch

2020-10-23 Thread Fred Kimmy
** Also affects: kunpeng920/ubuntu-20.04-hwe
   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/1867591

Title:
  [ACC-0316]sync mainline kernel 5.6rc6  ACC patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  Incomplete
Status in kunpeng920 ubuntu-18.04-hwe series:
  Incomplete
Status in kunpeng920 ubuntu-20.04 series:
  Incomplete
Status in kunpeng920 ubuntu-20.04-hwe series:
  New
Status in kunpeng920 upstream-kernel series:
  Incomplete
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
  roce patchset have merged into mainline 5.6rc2 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver
  crypto: hisilicon/sec2 - Update IV and MAC operation
  crypto: hisilicon/sec2 - Add iommu status check
  crypto: hisilicon/sec2 - Add workqueue for SEC driver.
  crypto: hisilicon - Use one workqueue per qm instead of per qp
  crypto: hisilicon - qm depends on UACCE
  crypto: hisilicon - remove redundant assignment of pointer ctx
  hisilicon - register zip engine to uacce
  hisilicon - Remove module_param uacce_mode
  uacce: add uacce driver
  uacce: Add documents for uacce
  crypto: hisilicon - Fix duplicate print when qm occur multiple errors
  crypto: hisilicon - Unify error detect process into qm
  crypto: hisilicon - Configure zip RAS error type
  crypto: hisilicon - Unify hardware error init/uninit into QM

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions

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


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

2020-10-23 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-23 03:29 EDT---
*** Bug 185933 has been marked as a duplicate of this bug. ***

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

Title:
  dasd_fba io error and kernel panic

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

Bug description:
  Generated I/O errors every hour in syslog and caused kernel panic with 
workloads running
   
  ---uname output---
  Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 
2020 s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  distro provided. up-to-date from Ubuntu18.04.
   
  Machine Type = z15 
   
  ---System Hang---
   The hourly generated I/O errors didn't impact the system up and running. 
When there are workloads on it, it will cause kernel panic and rebooted the 
server. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   After migrated from 16.04 to 18.04, will see the i/o errors. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   [52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and 
failed
  [52297.898244] dasd(fba): I/O status report for device 0.0.0100:
 dasd(fba): in req: 2e142bcd CS: 0x20 DS: 0x0C
 dasd(fba): device 0.0.0100: Failing CCW: a84f6c9f
 dasd(fba): SORRY - NO VALID SENSE AVAILABLE
  [52297.898255] dasd(fba): Related CP in req: 2e142bcd
 dasd(fba): CCW d15f44d3: 63400010 7FE2BBA0 DAT: 
0200 008150F2  0017
 dasd(fba): CCW b09ad76e: 4348 7FE2BBB0 DAT: 
0506 
 dasd(fba): CCW c44dfb20: 41600C00 F360 DAT: 
       
 dasd(fba): CCW a84f6c9f: 4348 7FE2BBB8 DAT: 
0510 0006
 dasd(fba): CCW 22dac88c: 4160  DAT:
 dasd(fba): CCW 69686544: 4348 7FE2BBC0 DAT: 
0502 0016
 dasd(fba): CCW 7bb6a17c: 41200400 F360 DAT: 
       
  [52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
   
  *Additional Instructions for y...@cn.ibm.com: 
  -Attach sysctl -a output output to the bug.

  [reply] [?]
  Internal Only
  Comment 1 QI YE 2020-03-12 02:29:20 CDT

  The z/VM version 6.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+subscriptions

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


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

2020-10-23 Thread 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/1901139

Title:
  No Intel HD sound 9th Gen Acer Swift 3 Notebook (possibly others)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device
  detected. lsmod shows module loaded, but alsa/pulse/etc is not picking
  up the audio device.  If I boot using the old kernel that was left
  behind, it works (5.4.0-52 from 20.04).  It does not work with shipped
  kernel (5.8.0-52) & does not work with kernel 5.9.1-050901 (the
  current unsigned kernel from mainline). lspci shows the device
  regardless of what I boot.  lsmod also shows the driver loading, but I
  don't see the codec portion of the driver loading on the current and
  testing kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-generic 5.8.0.25.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1108 F pulseaudio
andrew 1112 F pipewire-media-
   /dev/snd/seq:andrew 1107 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Oct 23 00:59:27 2020
  InstallationDate: Installed on 2019-11-16 (341 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Swift SF315-52G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=821af7d8-e605-4db1-aaef-f6d17905aeec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.08:bd12/21/2018:svnAcer:pnSwiftSF315-52G:pvrV1.08:rvnKBL:rnErdinger_KL:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52G
  dmi.product.sku: 
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1899508] Re: alsa/hda/realtek - The front Mic on a HP machine doesn't work

2020-10-23 Thread Stefan Bader
** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

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

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

Title:
  alsa/hda/realtek - The front Mic on a HP machine doesn't work

Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Triaged
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  This fix is only for oem-5.6 kernel, other kernels will merge this
  patch with stable update. Our oem project needs this patch to be merged
  ASAP.

  [Impact]
  When using a HP machine, after plugging the headset at front jack,
  there is no any input device shows.

  [Fix]
  The codec of the HP ZCentrol is alc671 and it needs to override the pin
  configuration to enable the headset mic.
  This patch is going to be merged by upstream, now backport it to
  oem-5.6 kernel.

  [Test Case]
  Boot the system, plug a headset and check the gnome-control-center,
  the Mic is active in the UI, and record the sound, it could record
  the sound.

  [Regression Risk]
  Low, this patch is to add a platform specific quirk to override pin
  configuration and already tested in this HP machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1899508/+subscriptions

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


[Kernel-packages] [Bug 1896716] Re: [SRU][OEM-5.6]Fix AMD system hang after re-plugin USBC-DP dongle

2020-10-23 Thread AaronMa
** Changed in: linux-oem-5.6 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  [SRU][OEM-5.6]Fix AMD system hang after re-plugin USBC-DP dongle

Status in HWE Next:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  After much times of re-plug USBC-DP dongle with external monitor,
  AMD laptop will hang.

  [Fix]
  AMD GPU driver set the wrong link setting to DP port.
  After initialize the DP setting, DP works fine.

  [Test Case]
  Verified on the target platform. no hang again.

  [Regression Potential]
  Low,
  Upstream fix in 5.7 kernel, Verified with positive results.
  Groovy already got this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1896716/+subscriptions

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


[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5

2020-10-23 Thread Jonas
Jeff, I synced the newest image from the 20th but this image still has
the same problem. BTW our machines do not have Intel X710 NICs but some
old Intel I350.

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

Title:
  [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
  after images update on Oct 5

Status in MAAS:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Note: Per comment #29, this was working up until Oct 5.  It looks to
  me like the last update to the focal boot images are also dated Oct 5
  coinciding with the appearance of this issue.

  
  1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1)
  2. 18.04(bionic) is good to deploy on the same sut/env.
  3. deployment failed on SUT pxe boot stage w/ error below,
  "Booting under MAAS direction...
  error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'.

  press any key to continue..."

  4.cross check for 'boot-initrd' file had been found on MAAS sever(ref 
attachment)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   eno1np0   no wireless extensions.

   eno2np1   no wireless extensions.
  MachineType: Supermicro Super Server
  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 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic 
root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-118-generic N/A
   linux-backports-modules-4.15.0-118-generic  N/A
   linux-firmware  1.173.19
  RfKill:

  Tags:  bionic uec-images
  Uname: Linux 4.15.0-118-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H12SSW-NT/iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  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.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789: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
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   eno1np0   no wireless extensions.

   eno2np1   no wireless extensions.
  MachineType: Supermicro Super Server
  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 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic 
root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-118-generic N/A
   linux-backports-modules-4.15.0-118-generic  N/A
   linux-firmware  1.173.19
  RfKill:

  Tags:  bionic uec-images
  Uname: Linux 4.15.0-118-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H12SSW-NT/iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  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: 

[Kernel-packages] [Bug 1901139] [NEW] No Intel HD sound 9th Gen Acer Swift 3 Notebook (possibly others)

2020-10-23 Thread nukedathlonman
Public bug reported:

Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device
detected. lsmod shows module loaded, but alsa/pulse/etc is not picking
up the audio device.  If I boot using the old kernel that was left
behind, it works (5.4.0-52 from 20.04).  It does not work with shipped
kernel (5.8.0-52) & does not work with kernel 5.9.1-050901 (the current
unsigned kernel from mainline). lspci shows the device regardless of
what I boot.  lsmod also shows the driver loading, but I don't see the
codec portion of the driver loading on the current and testing kernels.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-generic 5.8.0.25.30
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andrew 1108 F pulseaudio
  andrew 1112 F pipewire-media-
 /dev/snd/seq:andrew 1107 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Oct 23 00:59:27 2020
InstallationDate: Installed on 2019-11-16 (341 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Swift SF315-52G
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=821af7d8-e605-4db1-aaef-f6d17905aeec ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-52-generic N/A
 linux-backports-modules-5.4.0-52-generic  N/A
 linux-firmware1.190
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
dmi.bios.date: 12/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.08
dmi.board.asset.tag: Default string
dmi.board.name: Erdinger_KL
dmi.board.vendor: KBL
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.08
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.08:bd12/21/2018:svnAcer:pnSwiftSF315-52G:pvrV1.08:rvnKBL:rnErdinger_KL:rvrV1.08:cvnAcer:ct10:cvrV1.08:
dmi.product.family: Swift 3
dmi.product.name: Swift SF315-52G
dmi.product.sku: 
dmi.product.version: V1.08
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

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

Title:
  No Intel HD sound 9th Gen Acer Swift 3 Notebook (possibly others)

Status in linux package in Ubuntu:
  New

Bug description:
  Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device
  detected. lsmod shows module loaded, but alsa/pulse/etc is not picking
  up the audio device.  If I boot using the old kernel that was left
  behind, it works (5.4.0-52 from 20.04).  It does not work with shipped
  kernel (5.8.0-52) & does not work with kernel 5.9.1-050901 (the
  current unsigned kernel from mainline). lspci shows the device
  regardless of what I boot.  lsmod also shows the driver loading, but I
  don't see the codec portion of the driver loading on the current and
  testing kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-generic 5.8.0.25.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1108 F pulseaudio
andrew 1112 F pipewire-media-
   /dev/snd/seq:andrew 1107 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Oct 23 00:59:27 2020
  InstallationDate: Installed on 2019-11-16 (341 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Swift SF315-52G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=821af7d8-e605-4db1-aaef-f6d17905aeec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.08:bd12/21/2018:svnAcer:pnSwiftSF315-52G:pvrV1.08:rvnKBL:rnErdinger_KL:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.family: Swift 3
  dmi.product.name: Swift 

[Kernel-packages] [Bug 1901024] Re: Crash on startup using linux 5.8.0-25

2020-10-23 Thread Rauno
I can't start a web browser in recovery mode so apport-collect is
unusable.

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

Title:
  Crash on startup using linux 5.8.0-25

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my new Lenovo ThinkPad L15 and upgraded it to 
Ubuntu 20.10 for a newer kernel to fix minor compatibility issues with AMD 
Renoir.
  When using the newer kernel it freezes before splash. I did my best to follow 
instructions to create a crash file but none were ever created.
  Booting to recovery mode with 5.8 works, 5.4 kernel works. Booting from USB 
the (safe graphics) option works but not the default. On that USB I have latest 
available daily build (Oct 21 2020) of 20.10. I tried a fresh reinstall of 
Ubuntu 20.10 and still getting stuck.

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

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


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

2020-10-23 Thread 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 1901134

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

Title:
  P620 reported TPM errors on Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Thinkstation P620 will report TPM initial errors as follows on Ubuntu 20.04
  ~~
  root@lenovo-INVALID:~# dmesg | grep -i tpm
  [2.052240] tpm tpm0: tpm_try_transmit: send(): error -5
  [2.052257] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling 
instead

  It seems to be TPM IRQ. The same P620 BIOS, such issue doesn't happen
  on other OS.

  Regards,
  Jiqi.

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

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


[Kernel-packages] [Bug 1901135] [NEW] [SRU][OEM-5.6]Fix no video out from some monitors on amdgpu

2020-10-23 Thread AaronMa
Public bug reported:

[Impact]
On some models of Dell monitors, amdgpu lost signal.
Blackscreen only.

[Fix]
Handle aux write failure, and retry it to fix it.

[Test Case]
Verified on the monitors, display OK.

[Regression Potential]
Low,
Upstream fix, Verified with positive results.
Focal and Groovy already got this fix.

** Affects: hwe-next
 Importance: Undecided
 Assignee: AaronMa (mapengyu)
 Status: New

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

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  [SRU][OEM-5.6]Fix no video out from some monitors on amdgpu

Status in HWE Next:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-5.6 source package in Focal:
  New

Bug description:
  [Impact]
  On some models of Dell monitors, amdgpu lost signal.
  Blackscreen only.

  [Fix]
  Handle aux write failure, and retry it to fix it.

  [Test Case]
  Verified on the monitors, display OK.

  [Regression Potential]
  Low,
  Upstream fix, Verified with positive results.
  Focal and Groovy already got this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1901135/+subscriptions

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


[Kernel-packages] [Bug 1901134] [NEW] P620 reported TPM errors on Ubuntu 20.04

2020-10-23 Thread Jiqi Li
Public bug reported:

Hi,

Thinkstation P620 will report TPM initial errors as follows on Ubuntu 20.04
~~
root@lenovo-INVALID:~# dmesg | grep -i tpm
[2.052240] tpm tpm0: tpm_try_transmit: send(): error -5
[2.052257] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling 
instead

It seems to be TPM IRQ. The same P620 BIOS, such issue doesn't happen on
other OS.

Regards,
Jiqi.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1901134

Title:
  P620 reported TPM errors on Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Thinkstation P620 will report TPM initial errors as follows on Ubuntu 20.04
  ~~
  root@lenovo-INVALID:~# dmesg | grep -i tpm
  [2.052240] tpm tpm0: tpm_try_transmit: send(): error -5
  [2.052257] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling 
instead

  It seems to be TPM IRQ. The same P620 BIOS, such issue doesn't happen
  on other OS.

  Regards,
  Jiqi.

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

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


[Kernel-packages] [Bug 1867118] Re: dasd_fba io error and kernel panic

2020-10-23 Thread Frank Heimes
No, the issue is not yet fixed and rolled out with 20.04 updates.
It means that the issue is handled for focal/20.04 by the LP bug 1900624 and 
that is just Fix Committed (and not yet Fix Released).
The status and plan is (as of today) that the commit 709192d531e5 ("s390/dasd: 
Fix zero write for FBA devices") landed in Ubuntu's focal master-next git tree.
And according to 'kernel.ubuntu.com' an new binary kernel will be build and 
made available for testing in '-proposed' around 13-Nov. And if the "Bug 
verification & Regression testing" doesn't show any problems, this kernel will 
then be released to '-updates' around 30-Nov.

All kernel updates are usually processed by 3-weekly 'kernel SRU' cycles that 
are posted here: https://kernel.ubuntu.com/
But due to internal rearrangements and changes one SRU cycle is skipped this 
time ("There will be no SRU cycle from October 12 through November 8.").
 
But the fix is already included in Ubuntu 20.10, which was released just 
yesterday!

To shorten the time a bit until it get's released for focal/20.04, I
just compile a kernel based on the current master-next (that should have
the fix in) and made it available for testing here:
https://people.canonical.com/~fheimes/lp1867118/

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

Title:
  dasd_fba io error and kernel panic

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

Bug description:
  Generated I/O errors every hour in syslog and caused kernel panic with 
workloads running
   
  ---uname output---
  Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC 
2020 s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  distro provided. up-to-date from Ubuntu18.04.
   
  Machine Type = z15 
   
  ---System Hang---
   The hourly generated I/O errors didn't impact the system up and running. 
When there are workloads on it, it will cause kernel panic and rebooted the 
server. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   After migrated from 16.04 to 18.04, will see the i/o errors. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   [52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and 
failed
  [52297.898244] dasd(fba): I/O status report for device 0.0.0100:
 dasd(fba): in req: 2e142bcd CS: 0x20 DS: 0x0C
 dasd(fba): device 0.0.0100: Failing CCW: a84f6c9f
 dasd(fba): SORRY - NO VALID SENSE AVAILABLE
  [52297.898255] dasd(fba): Related CP in req: 2e142bcd
 dasd(fba): CCW d15f44d3: 63400010 7FE2BBA0 DAT: 
0200 008150F2  0017
 dasd(fba): CCW b09ad76e: 4348 7FE2BBB0 DAT: 
0506 
 dasd(fba): CCW c44dfb20: 41600C00 F360 DAT: 
       
 dasd(fba): CCW a84f6c9f: 4348 7FE2BBB8 DAT: 
0510 0006
 dasd(fba): CCW 22dac88c: 4160  DAT:
 dasd(fba): CCW 69686544: 4348 7FE2BBC0 DAT: 
0502 0016
 dasd(fba): CCW 7bb6a17c: 41200400 F360 DAT: 
       
  [52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
   
  *Additional Instructions for y...@cn.ibm.com: 
  -Attach sysctl -a output output to the bug.

  [reply] [?]
  Internal Only
  Comment 1 QI YE 2020-03-12 02:29:20 CDT

  The z/VM version 6.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+subscriptions

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