[Kernel-packages] [Bug 1858988] Re: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142]

[Kai-Heng Feng]

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: Fix Committed

** Also affects: linux-oem-osp1 (Ubuntu Focal)
   Importance: Undecided
   Status: Fix Released

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

** Also affects: linux-oem-osp1 (Ubuntu Eoan)
   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/1858988

Title:
  USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2
  card [1b21:2142]

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

Bug description:
  [Impact]
  Hotplug USB key to Sunix USB Type-A 3.1 Gen 2 card can't be detected

  [Fix]
  ASMedia XHCI USB controller PME# doesn't work under D0, so remove its cap by 
quirk.

  [Test]
  Verified on the target machine, USB 3 storage works.

  [Regression Potential]
  Low, it only affects target chip.

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

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

[Kernel-packages] [Bug 1861344] Re: uvcvideo: IPEVO Ziggi-HD document camera stops working on kernel 4.4.0-171

[Kai-Heng Feng]

The fix commit is
commit 2548288b4fb059b2da9ceada172ef763077e8a59
Author: Alan Stern 
Date:   Mon Jan 6 10:43:42 2020 -0500

USB: Fix: Don't skip endpoint descriptors with maxpacket=0


It's in 4.4.0-174.204, which is in xenial-proposed. Please enable proposed and 
see if it fixes the 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/1861344

Title:
  uvcvideo: IPEVO Ziggi-HD document camera stops working on kernel
  4.4.0-171

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a IPEVO Ziggi-HD document camera (1778:0207) that refuses to
  operate on kernel 4.4.0-171 or newer. On such kernels, uvcvideo fails
  with the kernel message 'uvcvideo: No streaming interface found for
  terminal 2' and no `/dev/videoX` device is created.

  The camera operates correctly on kernel 4.4.0-170.

  Ubuntu release: 16.04.6 LTS

  Attached in a tarball:

  * a relevant /var/log/syslog fragment captured when device plugged in
  * `cat /proc/version_signature`
  * `sudo lspci -vnvn`

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

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

[Kernel-packages] [Bug 1863621] [NEW] Add sysfs attribute to show remapped NVMe

[Kai-Heng Feng]

Public bug reported:

[Impact]
Intel Rapid Storage Technology hides NVMe behind AHCI controller, to
provide firmware base "fusion drive", like combining with Intel Optane.

There's a driver to support this but upstream doesn't like it for
reasons like NVMe quirks can't be applied when NVMe are behind AHCI
controller.

So we need to devise a mechanism to ask users to change BIOS storage
settings. This patch only provides a new attribute to let userspace like
distro installer know NVMe is remapped behind AHCI.
 
[Fix]
Add a new attribute to show that how many NVMes are remapped.

[Test]  
After applying the patch, there's a new "remapped_nvme" under the AHCI PCI
device sysfs.

If there's no remapped NVMe:
$ cat remapped_nvme
0

If there are two remapped NVMes:
$ cat remapped_nvme
2
 
[Regression Potential]
Low. It adds a new read only sysfs attribute, no actual functional 
change to the AHCI driver.

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

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

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

** Also affects: linux (Ubuntu Focal)
   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/1863621

Title:
  Add sysfs attribute to show remapped NVMe

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

Bug description:
  [Impact]
  Intel Rapid Storage Technology hides NVMe behind AHCI controller, to
  provide firmware base "fusion drive", like combining with Intel Optane.

  There's a driver to support this but upstream doesn't like it for
  reasons like NVMe quirks can't be applied when NVMe are behind AHCI
  controller.

  So we need to devise a mechanism to ask users to change BIOS storage
  settings. This patch only provides a new attribute to let userspace like
  distro installer know NVMe is remapped behind AHCI.
   
  [Fix]
  Add a new attribute to show that how many NVMes are remapped.

  [Test]  
  After applying the patch, there's a new "remapped_nvme" under the AHCI PCI
  device sysfs.

  If there's no remapped NVMe:
  $ cat remapped_nvme
  0
  
  If there are two remapped NVMes:
  $ cat remapped_nvme
  2
   
  [Regression Potential]
  Low. It adds a new read only sysfs attribute, no actual functional 
  change to the AHCI driver.

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

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

[Kernel-packages] [Bug 1859126] Re: Reduce s2idle power consumption when ethernet cable is connected on e1000e

[Kai-Heng Feng]

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

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

Title:
  Reduce s2idle power consumption when ethernet cable is connected on
  e1000e

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

Bug description:
  [Impact]
  When ethernet cable is connected, power consumption is quite high under 
suspend-to-idle.

  [Fix]
  Enable s0ix support for e1000e.

  [Test]
  When ethernet cable is connected, the power consumption is ~2.5w.
  After applying the patch, it can be lowered to ~1.8w.

  [Regression Potential]
  Low. This fix is limited to fairly recent I219 hardwares.

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

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

[Kernel-packages] [Bug 1863420] Re: WiFi Realtek RTL8723DE adapter support issue.

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1780590
   Add support for Realtek 8723DE wireless adapter

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

Title:
  WiFi Realtek RTL8723DE adapter support issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  command $ ubuntu-bug linux
  this debug info has been generated using a tethered USB phone connection on a 
live ubuntu. It is a REGRESSION from previous versions also.
  I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some 
wireless connectivity problems with Realtek chips.
  My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
  Ubuntu live session can’t detect the card nor the post-installed OS does.
  Therefore, no wifi switch/icon.
  -

  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 1849 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 15 13:40:08 2020
  IwConfig:
   enp1s0no wireless extensions.

   enp0s20f0u3  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Laptop 14q-cs0xxx
  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
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 849A
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 74.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/27/2018:svnHP:pnHPLaptop14q-cs0xxx:pvrType1ProductConfigId:rvnHP:rn849A:rvrKBCVersion74.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14q-cs0xxx
  dmi.product.sku: 5DZ92PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1780590
   Add support for Realtek 8723DE wireless adapter

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

Title:
  WiFi module RTL8723DE not supported @live / installed session

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi
  I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some 
wireless connectivity problems with Realtek chips.
  My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
  Ubuntu live session can’t detect the card nor the post-installed OS does.
  Therefore, no wifi switch/icon.
  I would hope Ubuntu 20.04 LTS natively support this wireless chip.
  regards.

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

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

[Kernel-packages] [Bug 1871090] Re: Add Mute LED support for an HP laptop

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1866768 stella

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

Title:
  Add Mute LED support for an HP laptop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]
  Mute LED isn't on after the audio output is muted.

  [Fix]
  Use HDA codec to control GPIO 4 to enable mute LED support.

  [Test]
  After applying the patch, mute LED works with mute hotkey or disable
  sound in Gnome Control Center.
  
  [Regression Potential]
  Low. This fix only target at one specific laptop.

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

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

[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Kai-Heng Feng]

[+Subscribed Hans]

Hans, I think the issue is caused by:
[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own gpio for panel 
control

Would be appreciated if you can take a look.

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1871300] [NEW] ix authentication fail on Realtek WiFi 8723de

[Kai-Heng Feng]

Public bug reported:

[Impact]
When Realtek WiFi 8723de tries to authenticate, the AP may return the
exchanged key is wrong, either by "Reason 2" or "Reason 23".

[Fix] 
8723de specific fix to make sure auth TX is sent out and can be received
by AP.

[Test]
Loop to connect/disconnect as a reproducer.
After applying the fix, it can re-connect just fine over 1 times.
 
[Regression Potential]
Low. It's tested by Realtek internally, and they also made sure the
other two supported chip, 8822BE and 8822CE, work correctly.

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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Won't Fix

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

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

** Affects: linux-oem-osp1 (Ubuntu Focal)
 Importance: Undecided
 Status: Won't Fix

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

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

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

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

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

** Changed in: linux-oem-osp1 (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  ix authentication fail on Realtek WiFi 8723de

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  When Realtek WiFi 8723de tries to authenticate, the AP may return the
  exchanged key is wrong, either by "Reason 2" or "Reason 23".

  [Fix] 
  8723de specific fix to make sure auth TX is sent out and can be received
  by AP.

  [Test]
  Loop to connect/disconnect as a reproducer.
  After applying the fix, it can re-connect just fine over 1 times.
   
  [Regression Potential]
  Low. It's tested by Realtek internally, and they also made sure the
  other two supported chip, 8822BE and 8822CE, work correctly.

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

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

[Kernel-packages] [Bug 1871300] Re: Fix authentication fail on Realtek WiFi 8723de

[Kai-Heng Feng]

** Summary changed:

- ix authentication fail on Realtek WiFi 8723de
+ Fix authentication fail on Realtek WiFi 8723de

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

Title:
  Fix authentication fail on Realtek WiFi 8723de

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

Bug description:
  [Impact]
  When Realtek WiFi 8723de tries to authenticate, the AP may return the
  exchanged key is wrong, either by "Reason 2" or "Reason 23".

  [Fix] 
  8723de specific fix to make sure auth TX is sent out and can be received
  by AP.

  [Test]
  Loop to connect/disconnect as a reproducer.
  After applying the fix, it can re-connect just fine over 1 times.
   
  [Regression Potential]
  Low. It's tested by Realtek internally, and they also made sure the
  other two supported chip, 8822BE and 8822CE, work correctly.

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

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

[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Kai-Heng Feng]

** Attachment added: "config-5.6.0-8-generic"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5348572/+files/config-5.6.0-8-generic

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Kai-Heng Feng]

Thank you, Hans.

The difference is CONFIG_GPIO_CRYSTAL_COVE=m, so we need to make it
builtin or make it load before i915 in initramfs.

I'll build another kernel for testing.

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Kai-Heng Feng]

Hi Phuc Minh Cai,

Please remove the old kernel and test this one:
https://people.canonical.com/~khfeng/lp1860754-3/

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Kai-Heng Feng]

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

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Won't Fix
Status in linux package in Arch Linux:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems have a "phantom" Nvidia UCSI, which prevent systems from
  suspending. 

  [Fix]
  ucsi_ccg is stuck in its probe routine because of the i2c bus never
  timeouts. Let it timeouts and probe can fail since it's just a phantom
  device.

  [Test]
  After applying this patch system can suspend/resume succesfully.

  [Regression Potential]
  Low. It's a trivial change to correctly handle timeout.

  === Original Bug Report ===

  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.

  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
   nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
   mem_sleep_default=deep  # suspend to RAM; suspend-to-idle has 
its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

   [  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
   [  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

   [  299.331393] ata1.00: configured for UDMA/100
   

   [  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
   [  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 [ucsi_ccg] 
returns -110
   [  346.133042] PM: Device 0-0008 failed to resume: error -110
   ...
   [  346.141504] Restarting tasks ... done.
   [  346.340221] PM: suspend exit

  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation

[Kernel-packages] [Bug 1868217] Re: Make Dell WD19 dock more reliable after suspend

[Kai-Heng Feng]

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

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

Title:
   Make Dell WD19 dock more reliable after suspend

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

Bug description:
  [Impact]
  When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub
  used internally may stop working after suspend.

  [Fix]
  Disable LPM on the Realtek USB Hub, and let xHCI controller make sure
  the link state transition is completed.

  [Test]
  After applying the patches, the Dell WD19 works reliably after thousand
  times for suspend/resume cycle.

  [Regression Potential]
  Low. This replaces the currently "msleep" way with more robust
  mechanism. I also test other systems and nothing breaks.

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

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

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[Kai-Heng Feng]

Just wait for that commit lands in Ubuntu 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/1870140

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.445143] RDX:  RSI: 0001 RDI: 
0008
  [  567.445146] RBP:  R08:  R09: 
c9477ce0
  [  567.445149] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.445152] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.445156] FS:  () GS:888

[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040

[Kai-Heng Feng]

Please test mainline kernel 5.6.

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

Title:
  Intel GPU causes BUG: kernel NULL pointer dereference, address:
  0040

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After playing Gurumin: A Monstrous Adventure for some time, the system
  crashed in an unrecoverable way. REISUB was required to get some logs.

  This crash happened with default Ubuntu's kernel, default Mesa and
  default Xorg session. I never observed a crash this serious using the
  intel Xorg driver. However, using the default (modesetting), the
  following unrecoverable crash happened after two hours:

  The syslog contains the following:

  Apr  2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php 
session files...
  Apr  2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: 
Succeeded.
  Apr  2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php 
session files.
  Apr  2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: 
Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel 
NULL pointer dereference, address: 0040
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: 
supervisor read access in kernel mode
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: 
error_code(0x) - not-present page
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops:  
[#1] SMP PTI
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 
200385 Comm: xfwm4 Tainted: P   O  5.4.0-21-generic #25-Ubuntu
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware 
name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 
0010:i915_active_acquire+0xe/0x80 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 
c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 
0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 
01 f0 0f b1 53 38 75 f2 45 31
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 
0018:bd8446f979c8 EFLAGS: 00010286
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: 
 RBX: 9c477afaca80 RCX: 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 
9c4633bfc500 RSI: 9c477afaca80 RDI: 0008
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: 
bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 
00014000 R11: 9c47d1918b00 R12: 9c4633bfc500
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 
0008 R14: 9c4633bfc500 R15: 9c47d6f4db00
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS:  
7f99a3564a80() GS:9c47de28() knlGS:
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS:  0010 DS: 
 ES:  CR0: 80050033
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 
0040 CR3: 000556ca0001 CR4: 003606e0
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: 
 DR1:  DR2: 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: 
 DR6: fffe0ff0 DR7: 0400
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace:
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477]  
i915_active_ref+0x24/0x200 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521]  
i915_vma_move_to_active+0x74/0xf0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564]  
eb_submit+0xff/0x440 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608]  
i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615]  ? 
sock_def_readable+0x40/0x70
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618]  ? 
__kmalloc_node+0x205/0x320
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668]  
i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717]  ? 
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284742]  
drm_ioctl_kernel+0xae/0xf0 [drm]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284761]  
drm_ioctl+0x234/0x3d0 [drm]
  Apr  2 00:58:56 Lenovo-ideapad-310-

[Kernel-packages] [Bug 1871589] [NEW] Add DCPD backlight support for HP CML system

[Kai-Heng Feng]

Public bug reported:

[Impact]
PWM backlight doesn't work on an upcoming HP CML system.

[Fix]
Use DPCD to control backlight instead of PWM.

[Test]
With this patch applied, changing backlight sysfs can change the brightness.

[Regression Potential]
Low. This is specific to panel ID, which is unique.

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

Title:
  Add DCPD backlight support for HP CML system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  PWM backlight doesn't work on an upcoming HP CML system.

  [Fix]
  Use DPCD to control backlight instead of PWM.

  [Test]
  With this patch applied, changing backlight sysfs can change the brightness.

  [Regression Potential]
  Low. This is specific to panel ID, which is unique.

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

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

[Kernel-packages] [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys

[Kai-Heng Feng]

** Description changed:

+ === SRU Justification === 
+ [Impact]
+ PWM backlight doesn't work on Spectre x360 Convertible 13t-aw100.
+ 
+ [Fix]
+ Use DPCD to control backlight instead of PWM.
+ 
+ [Test]
+ With this patch applied, user confirmed the issue is fixed.
+ 
+ [Regression Potential]
+ Low. This is specific to panel ID, which is unique.
+ 
+ === Original Bug Report ===
+ 
  I cannot adjust the screen brightness using the keyboard keys or
  changing /sys/call/backlight/intel_backlight/brightness values. I've
  only been able to adjust the backlight using xrandr.
  
  Followed bug report on 
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and 
attached files. Additional information:
  1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change 
the screen brightness
  2. video.use_bios_initial_backlight=0 does not enable brightness to be changed
- 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work 
and on one boot "y"s were being continuously typed without any keys being 
depressed. It was odd. 
+ 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work 
and on one boot "y"s were being continuously typed without any keys being 
depressed. It was odd.
  4. video.use_native_backlight=1 does not enabel brightness to be changed
  5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no 
impact
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-generic 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jaredy 1649 F pulseaudio
-  /dev/snd/pcmC0D0p:   jaredy 1649 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jaredy 1649 F pulseaudio
+  /dev/snd/pcmC0D0p:   jaredy 1649 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 19 19:51:45 2020
  InstallationDate: Installed on 2020-01-03 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13t-aw100
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-26-generic N/A
-  linux-backports-modules-5.3.0-26-generic  N/A
-  linux-firmware1.183.3
+  linux-restricted-modules-5.3.0-26-generic N/A
+  linux-backports-modules-5.3.0-26-generic  N/A
+  linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw100
  dmi.product.sku: 6YG70AV
  dmi.sys.vendor: HP

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

Title:
  Backlight brightness cannot be adjusted using keys

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  === SRU Justification === 
  [Impact]
  PWM backlight doesn't work on Spectre x360 Convertible 13t-aw100.

  [Fix]
  Use DPCD to control backlight instead of PWM.

  [Test]
  With this patch applied, user confirmed the issue is fixed.

  [Regression Potential]
  Low. This is specific to panel ID, which is unique.

  === Original Bug Report ===

  I cannot adjust the screen brightness using the keyboard keys or
  changing /sys/call/backlight/intel_backlight/brightness values. I've
  only been able to adjust the backlight using xrandr.

  Followed bug report on 
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and 
attached files. Additional information:
  1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change 
the screen brightness
  2. video.use_bios_initial_backlight=0 does not enable brightness to be changed
  3. Cannot login to when using kernel paramater acpi_osi=. Login does not work 
and on one boot "y"s were being continuously typed without any keys being 
depressed. It was

[Kernel-packages] [Bug 1871589] Re: Add DCPD backlight support for HP CML system

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1867082 stella

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

Title:
  Add DCPD backlight support for HP CML system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  PWM backlight doesn't work on an upcoming HP CML system.

  [Fix]
  Use DPCD to control backlight instead of PWM.

  [Test]
  With this patch applied, changing backlight sysfs can change the brightness.

  [Regression Potential]
  Low. This is specific to panel ID, which is unique.

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

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

[Kernel-packages] [Bug 1870786] Re: Kernel BUG sometimes during pluging in a DP Splitter

[Kai-Heng Feng]

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

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

Title:
  Kernel BUG sometimes during pluging in a DP Splitter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, during plugging in a DP -> 2x HDMI splitter, I get a kernel
  BUG with a NULL pointer dereference. Most times it works, through.

  I'm using Ubuntu 20.04

  I've a 1920x1200 (eDP) display in my laptop, and a 2560x1440 and a
  1920x1080 display on the splitter.

  Its a Intel(R) Core(TM) i5-8250U CPU platform.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=/dev/mapper/sda5_crypt
  MachineType: Default string Default string
  Package: linux-meta (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  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.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: audio mythtv
  WpaSupplicantLog:
   
  _MarkForUpload: True
  dmi.bios.date: 01/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2019:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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

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

[Kernel-packages] [Bug 1871667] Re: Touchpad disabled after ovrnight suspend

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1867448
   Tauchpad not functioning after overnight suspend

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

Title:
  Touchpad disabled after ovrnight suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Although the mouse does work - it seems touchpad never wakes up or
  engaged when the spacebar key is pressed to wake up

  This problem has been persistent for past 4 or 5 months

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-47-generic 5.3.0-47.39
  ProcVersionSignature: Ubuntu 5.3.0-47.39-generic 5.3.18
  Uname: Linux 5.3.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user-meir   1563 F pulseaudio
   /dev/snd/controlC0:  user-meir   1563 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Wed Apr  8 08:42:24 2020
  InstallationDate: Installed on 2019-10-18 (172 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3180
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic 
root=UUID=8b17e198-3430-4a53-9e4a-1da7d792458b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-47-generic N/A
   linux-backports-modules-5.3.0-47-generic  N/A
   linux-firmware1.183.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown

[Kai-Heng Feng]

Sorry, should rephrase to "Can you please see if shutdown works when
there's no previous suspend attempt?"

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

Title:
  Ubuntu 19.10 doesn't shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello guys,

  I can't shutdown Ubuntu 19.10. When I try, the shutdown screen
  appears. The first two dots below the ubuntu logo, turn orange and
  then it freezes. Reboot works fine.

  The debug-shell is no use, because at the freeze point I can't type in
  commands.  When I press ESC to see what's going on during shutdown,
  the last message to appear ist "[Some weird number] reboot: power
  down. Last time I pressed ESC during shutdown the "weird number" was
  85.270119. I also tried to shutdown with the terminal commands "sudo
  shutdown now", "sudo shutdown -P now", "sudo shutdown -h now",
  "poweroff" and "sudo poweroff -f". All of them had the effect as
  describe above except the command "sudo poweroff -f". After I typed in
  the command, I authenticated and following messages appeared:
  "Powering off...". At this point it freezed. I could still see the
  desktop and every visible window, but I couldn't perform any actions;
  not even keyboard shortcuts worked. It also did not help to change
  'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to
  'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run
  "update-grub".

  Once the following command combo did work: "sudo swapoff -a &&
  systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't
  work any more.

  In the application "Additional Drivers" I selected the proprietary
  and tested driver of NVIDIA, but I can't to this for my WLAN-Card
  (correct word?), because the "Additional Drivers" says it's not working,
  but my WLAN works fine. I've got only Bluetooth problems. The displayed
  name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band
  Wireless-AC 7260)". I also tried to manually install a driver it didn't
  help.

   When I wake up the laptop, a black screen appears with some error
  messages, but only for a very short time so I can't make a photo of it.
  I tried once and the text was unreadable.

  I have the latest BIOS and my Computer model is MSI PX60 2QD.

  It doesn't work with Arch Linux either.

  Thanks for your help :)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leonard1724 F pulseaudio
   /dev/snd/controlC1:  leonard1724 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-18 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. PX60 2QD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H6IMS.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H6
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: PX60 2QD
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV: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/1860800/+subscriptions

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

[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend

[Kai-Heng Feng]

So it also happens to 3.13 and 4.4 kernel? Comment #52 doesn't state it
explicitly...

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning.

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

  Each wake up, motherboard (back panel) USB ports 3.1 Gen 1 don't work.

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

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

  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:

  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---

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

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

[Kernel-packages] [Bug 1870616] Re: [MEDION E122X] hibernate/resume failure

[Kai-Heng Feng]

Wonder if resume= and resume_offset= are set correctly?

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

Title:
  [MEDION E122X] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Had terminal and firefox open.

  Then atemmepted to see if i could hibernate with

  pm-hibernate

  just to see if it worked

  ProblemType: KernelOops
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkyere   1121 F pulseaudio
  Date: Fri Apr  3 21:57:45 2020
  DuplicateSignature: hibernate/resume:MEDION E122X:Medion-E122X_0107
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2020-04-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  InterpreterPath: /usr/bin/python3.8
  MachineType: MEDION E122X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/LubuntuRootLVM-Root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  Title: [MEDION E122X] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Medion-E122X_0107
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: E122X
  dmi.board.vendor: MEDION
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMedion-E122X_0107:bd05/11/2010:svnMEDION:pnE122X:pvrVer01.07:rvnMEDION:rnE122X:rvrRev1.0:cvnMEDION:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: E122X
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver: 01.07
  dmi.sys.vendor: MEDION

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

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

[Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown

[Kai-Heng Feng]

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

If mainline kernel doesn't work, usually there are some driver prevent
the system from shutting down.

Unload driver one by one to see which one is the culprit.

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

Title:
  Ubuntu 19.10 doesn't shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello guys,

  I can't shutdown Ubuntu 19.10. When I try, the shutdown screen
  appears. The first two dots below the ubuntu logo, turn orange and
  then it freezes. Reboot works fine.

  The debug-shell is no use, because at the freeze point I can't type in
  commands.  When I press ESC to see what's going on during shutdown,
  the last message to appear ist "[Some weird number] reboot: power
  down. Last time I pressed ESC during shutdown the "weird number" was
  85.270119. I also tried to shutdown with the terminal commands "sudo
  shutdown now", "sudo shutdown -P now", "sudo shutdown -h now",
  "poweroff" and "sudo poweroff -f". All of them had the effect as
  describe above except the command "sudo poweroff -f". After I typed in
  the command, I authenticated and following messages appeared:
  "Powering off...". At this point it freezed. I could still see the
  desktop and every visible window, but I couldn't perform any actions;
  not even keyboard shortcuts worked. It also did not help to change
  'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to
  'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run
  "update-grub".

  Once the following command combo did work: "sudo swapoff -a &&
  systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't
  work any more.

  In the application "Additional Drivers" I selected the proprietary
  and tested driver of NVIDIA, but I can't to this for my WLAN-Card
  (correct word?), because the "Additional Drivers" says it's not working,
  but my WLAN works fine. I've got only Bluetooth problems. The displayed
  name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band
  Wireless-AC 7260)". I also tried to manually install a driver it didn't
  help.

   When I wake up the laptop, a black screen appears with some error
  messages, but only for a very short time so I can't make a photo of it.
  I tried once and the text was unreadable.

  I have the latest BIOS and my Computer model is MSI PX60 2QD.

  It doesn't work with Arch Linux either.

  Thanks for your help :)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leonard1724 F pulseaudio
   /dev/snd/controlC1:  leonard1724 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-18 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. PX60 2QD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H6IMS.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H6
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: PX60 2QD
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV: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/1860800/+subscriptions

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

[Kernel-packages] [Bug 1871804] Re: WiFi adapter doesn't work with linux kernel version 5.3.0-46

[Kai-Heng Feng]

Please attach output of `dpkg -l | grep linux-modules`, thanks!

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

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

Title:
  WiFi adapter doesn't work with linux kernel version 5.3.0-46

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing new kernel version 5.3.0-46 in linux mint 19 and reboot, 
wifi adapter stop working. I tried to install driver but it didn't helped. Then 
i rebooted with kernel 5.3.0-45 and this helped.
  Wifi adapter's chip is rtl8188eu
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u-chan 1246 F pulseaudio
   /dev/snd/controlC1:  u-chan 1246 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dca72a9e-6a81-4c62-968b-64c2cd4d58ac
  InstallationDate: Installed on 2019-12-28 (102 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  IwConfig:
   enp0s2f1u4  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 003: ID 2357:010c  
   Bus 001 Device 007: ID 2717:ff80  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b57e519b-3434-422b-87a3-6c25c8ab086a ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  RfKill:
   
  Tags:  tara
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.2
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.1
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd09/13/2007:svnMSI:pnMS-7369:pvr1.1:rvnMSI:rnMS-7369:rvr1.1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7369
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.1
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1871819] [NEW] Make efi-pstore builtin

[Kai-Heng Feng]

Public bug reported:

[Impact]
efi-pstore isn't loaded by default, however it's really useful to collect 
kernel oops.

[Fix]
Make efi-pstore builtin.

[Test]
# echo c > /proc/sysrq-trigger

Reboot, and we can found kernel oops are in /sys/fs/pstore.

[Regression Potential]
Low. We can still disable it via kernel parameter "efi-pstore.pstore_disable=1".

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

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

Title:
  Make efi-pstore builtin

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  efi-pstore isn't loaded by default, however it's really useful to collect 
kernel oops.

  [Fix]
  Make efi-pstore builtin.

  [Test]
  # echo c > /proc/sysrq-trigger

  Reboot, and we can found kernel oops are in /sys/fs/pstore.

  [Regression Potential]
  Low. We can still disable it via kernel parameter 
"efi-pstore.pstore_disable=1".

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

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

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Kai-Heng Feng]

Should be fixed by LP: #1840854.

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

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

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  blk_update_request error when mount nvme partition

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

Bug description:
  As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel
  endless blk_update_request error will exists in kernel dmesg.
  the nvme module: PC400 NVMe SK hynix 512GB

  While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (11 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200330)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT 
mode device
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: Dell Inc. Precision 3930 Rack
  Package: linux-generic 5.4.0.21.25
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  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.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3930 Rack
  dmi.product.sku: 0873
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1872462] Re: rtl8723de wifi and bluetooth not working simultaneously

[Kai-Heng Feng]

The older kernel with rtw88 8723de support is 5.0 based linux-oem-osp1
kernel. Can you please install it from bionic-updates repo, and see if
both WiFi and Bluetooth work?

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

Title:
  rtl8723de wifi and bluetooth not working simultaneously

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8723DE wifi+bluetooth adapter works only with one of the two
  components enabled. This is a common bug encountered in all distros
  after installing dkms module from lwfinger/rtlwifi_new repo. Ubuntu
  20.04 fixed this in previous kernel releases (only distribution to do
  so) and gave support for rtl8723de out of the box. Unfortunately, Bug
  shows up again after doing sudo apt dist-upgrade. I presume this is a
  kernel issue, as a new version was released recently. Since then,
  bluetooth is able to scan for devices but cannot connect if wifi is
  enabled first and vice versa.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seba   1449 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 13 09:31:54 2020
  InstallationDate: Installed on 2020-04-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 04f2:b5d5 Chicony Electronics Co., Ltd HP TrueVision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14-bs0xx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=10f9e70b-7750-4172-9b6f-9c1647d6e763 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 831C
  dmi.board.vendor: HP
  dmi.board.version: 17.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd02/26/2018:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831C:rvr17.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-bs0xx
  dmi.product.sku: 2RH45LA#AKH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake

[Kai-Heng Feng]

Focal kernel is already frozen at Apr. 9th, so...

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

Title:
  Can not see the storage with Intel RAID On mode enabled on Intel Comet
  Lake

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

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled in the BIOS.

  The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
  the ID[1] in the kernel.

  [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
  h...@endlessm.com/.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 09:55:02 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: Dell Inc. Latitude 5310
  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 --- toram
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5310
  dmi.product.sku: 099F
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake

[Kai-Heng Feng]

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
 Assignee: Kai-Heng Feng (kaihengfeng)
   Status: 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/1871812

Title:
  Can not see the storage with Intel RAID On mode enabled on Intel Comet
  Lake

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled in the BIOS.

  The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
  the ID[1] in the kernel.

  [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
  h...@endlessm.com/.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 09:55:02 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: Dell Inc. Latitude 5310
  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 --- toram
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5310
  dmi.product.sku: 099F
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1856370] Re: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend

[Kai-Heng Feng]

ohad, can you please attach dmesg after it failed? Thanks.

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

Title:
  [nvidia] Black screen with message "GPU has fallen off the bus" after
  resuming from suspend

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

Bug description:
  Every time I suspend my laptop, after I resume it, a black screen
  shows with the error message

  - GPU has fallen off the bus

  It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590
  with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5

  Description:  Ubuntu 19.10
  Release:  19.10
  nvidia driver 435

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 16:31:58 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell Device [1028:0905]
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

[Kai-Heng Feng]

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

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

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

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake

[Kai-Heng Feng]

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ ID is missing so the devcie isn't bound to AHCI driver.
+ Without the driver, we can't check the existence of remapped NVMe.
+ 
+ [Fix]
+ Add one missing ID.
+ 
+ [Test]
+ Use lspci to see if the device is bound to ahci driver. Test positive
+ after applying the patch.
+ 
+ [Regression Potential]
+ Low. This is a trivial fix which limits to one specific device.
+ 
+ === Original Bug Report ===
+ 
  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled in the BIOS.
  
  The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
  the ID[1] in the kernel.
  
  [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
  h...@endlessm.com/.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 09:55:02 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: Dell Inc. Latitude 5310
  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 --- toram
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5310
  dmi.product.sku: 099F
  dmi.sys.vendor: Dell Inc.

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

Title:
  Can not see the storage with Intel RAID On mode enabled on Intel Comet
  Lake

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  ID is missing so the devcie isn't bound to AHCI driver.
  Without the driver, we can't check the existence of remapped NVMe.

  [Fix]
  Add one missing ID.

  [Test]
  Use lspci to see if the device is bound to ahci driver. Test positive
  after applying the patch.

  [Regression Potential]
  Low. This is a trivial fix which limits to one specific device.

  === Original Bug Report ===

  Can not see the storage on Dell Latitude 5310 with Intel RAID On mode
  enabled in the BIOS.

  The Dell Latitude 5310 is an Intel Comet Lake platform, which missing
  the ID[1] in the kernel.

  [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian-
  h...@endlessm.com/.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1536 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 09:55:02 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405)
  MachineType: Dell Inc. Latitude 5310
  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 --- toram
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5310
  dmi.product.sku: 099F
  dmi.sys.vendor: Dell Inc.

To manage notific

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Kai-Heng Feng]

Please test kernel here:
https://people.canonical.com/~khfeng/lp1872984/

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

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

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for networ

[Kernel-packages] [Bug 1811236] Re: System wakes from suspend without user initialization

[Kai-Heng Feng]

This should be addressed by later kernel and firmware releases. Please
check whether the issue still happen on up-to-date system.

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

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

Title:
  System wakes from suspend without user initialization

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use `systemctl suspend` for taking my laptop to sleep. Suspend seems
  to work fine, but after a random amount of time, the system resumes
  without me pressing any buttons, moving a mouse etc.

  Some other methods have been attempted, but all end up with the same
  result, ie. system resumes unwanted.

  Here is a /var/log/syslog excerpt, hope I managed to grab everything
  valuable. The bug was filed with `ubuntu-bug linux-
  image-4.18.0-13-generic`, which is the linux image currently in use.
  Please let me know if something is missing due to incorrect package
  selection or otherwise.

  ---

  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3067] 
manager: sleep: sleep requested (sleeping: no  enabled: yes)
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3069] device 
(enp0s20f0u2c2): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3126] device 
(wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3415] device 
(enp0s20f0u4): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jan 10 13:48:35 caolila NetworkManager[869]:   [1547120915.3453] 
manager: NetworkManager state is now ASLEEP
  Jan 10 13:48:35 caolila systemd[1]: Reached target Sleep.
  Jan 10 13:48:35 caolila systemd[1]: Starting Suspend...
  Jan 10 13:48:35 caolila whoopsie[1352]: [13:48:35] offline
  Jan 10 13:48:35 caolila systemd-sleep[32606]: Suspending system...
  Jan 10 13:48:35 caolila kernel: [19604.933999] PM: suspend entry (deep)
  Jan 10 13:48:35 caolila kernel: [19604.934001] PM: Syncing filesystems ... 
done.
  Jan 10 13:48:35 caolila wpa_supplicant[868]: nl80211: deinit ifname=wlp0s20f3 
disabled_11b_rates=0
  Jan 10 13:53:55 caolila kernel: [19607.067269] Freezing user space processes 
... (elapsed 0.004 seconds) done.
  Jan 10 13:53:55 caolila kernel: [19607.071592] OOM killer disabled.
  Jan 10 13:53:55 caolila kernel: [19607.071593] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan 10 13:53:55 caolila kernel: [19607.072971] Suspending console(s) (use 
no_console_suspend to debug)
  Jan 10 13:53:55 caolila kernel: [19607.160541] e1000e: EEE TX LPI TIMER: 
0011
  Jan 10 13:53:55 caolila kernel: [19607.502557] thunderbolt :07:00.0: 
stopping RX ring 0
  Jan 10 13:53:55 caolila kernel: [19607.502575] thunderbolt :07:00.0: 
disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1)
  Jan 10 13:53:55 caolila kernel: [19607.502581] thunderbolt :07:00.0: 
stopping TX ring 0
  Jan 10 13:53:55 caolila kernel: [19607.502605] thunderbolt :07:00.0: 
disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0)
  Jan 10 13:53:55 caolila kernel: [19607.502608] thunderbolt :07:00.0: 
control channel stopped
  Jan 10 13:53:55 caolila kernel: [19607.502808] ACPI: EC: interrupt blocked
  Jan 10 13:53:55 caolila kernel: [19607.684603] ACPI: Preparing to enter 
system sleep state S3
  Jan 10 13:53:55 caolila kernel: [19607.688265] ACPI: EC: event blocked
  Jan 10 13:53:55 caolila kernel: [19607.688267] ACPI: EC: EC stopped
  Jan 10 13:53:55 caolila kernel: [19607.688268] PM: Saving platform NVS memory
  Jan 10 13:53:55 caolila kernel: [19607.688301] Disabling non-boot CPUs ...
  Jan 10 13:53:55 caolila kernel: [19607.704406] IRQ 122: no longer affine to 
CPU1
  Jan 10 13:53:55 caolila kernel: [19607.704426] IRQ 187: no longer affine to 
CPU1
  Jan 10 13:53:55 caolila kernel: [19607.705447] smpboot: CPU 1 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.728394] IRQ 189: no longer affine to 
CPU2
  Jan 10 13:53:55 caolila kernel: [19607.729415] smpboot: CPU 2 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.752349] IRQ 177: no longer affine to 
CPU3
  Jan 10 13:53:55 caolila kernel: [19607.753377] smpboot: CPU 3 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.780410] IRQ 179: no longer affine to 
CPU4
  Jan 10 13:53:55 caolila kernel: [19607.781438] smpboot: CPU 4 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.804344] IRQ 185: no longer affine to 
CPU5
  Jan 10 13:53:55 caolila kernel: [19607.805385] smpboot: CPU 5 is now offline
  Jan 10 13:53:55 caolila kernel: [19607.828255] IRQ 183: no longer affine to 
CPU6
  Jan 10 13:53:55 caolila kernel: [19607.828271] IRQ 195: no longer affine to 
CPU6
  Jan 10 

[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown

[Kai-Heng Feng]

Seems like it's Ice Lake, the support was added to thermald 1.9.

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

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

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

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

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown

[Kai-Heng Feng]

Hmm, does the overheat still happen after thermald gets enabled?

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

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

Bug description:
  On a bit higher load and especially if Laptop is charging, very often
  Kernel does an emergency thermal shutdown.

  thermal thermal_zone3: critical temperature reached (80 C), shutting
  down

  It says 80 C, but sensors command shows that temperatures hovering
  close to 100C before the shutdown happens.

  dmesg is often also full of these (for each core):
  mce: CPU2: Core temperature above threshold, cpu clock throttled (total 
events = 246766)

  When I boot to Windows, it seems that CPU is throttled more
  aggressively on load and thermal shutdown doesn't happen with a
  similar load, but CPU frequencies drop to 1600 range, while in Ubuntu
  they are 2800 range.

  I would rather have more throttling that computer shutting down
  randomly without the ability to save work.

  Is there a workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton  1874 F pulseaudio
   /dev/snd/pcmC0D0p:   anton  1874 F...m pulseaudio
   /dev/snd/pcmC0D6c:   anton  1874 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:54:21 2020
  InstallationDate: Installed on 2019-11-29 (137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q9
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition

[Kai-Heng Feng]

I cannot reproduce the issue after several reboots...

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

Title:
  blk_update_request error when mount nvme partition

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

Bug description:
  Can't install on this nvme with a focal server installer.

  As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel
  endless blk_update_request error will exists in kernel dmesg.
  the nvme module: PC400 NVMe SK hynix 512GB

  While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (11 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200330)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT 
mode device
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: Dell Inc. Precision 3930 Rack
  Package: linux-generic 5.4.0.21.25
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  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.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3930 Rack
  dmi.product.sku: 0873
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Kai-Heng Feng]

Ok. Can you please blacklist rtw_pci and attach `sudo lspci -vv` 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/1872984

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for networks and error occurs when attempting to 
turn on/off wifi in settings:

[Kernel-packages] [Bug 1873316] Re: I can't get bluetooth to work

[Kai-Heng Feng]

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

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

Title:
  I can't get bluetooth to work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't get bluetooth to work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Apr 16 12:04:07 2020
  DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] 
[1458:d000]
  InstallationDate: Installed on 2018-11-09 (523 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XM-D3HP
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jul 24 17:33:18 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1873360] Re: Ethernet driver not loaded at boot

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1871182
   [RTL810xE] No ethernet connection

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

Title:
  Ethernet driver not loaded at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running a test on Focal Daily build 16.04.2020

  the ethernet driver was not loaded at boot - attached is the dmesg.log

  - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD
  Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller
  integrated on system board, WiFi 802.11 b/g/N,

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

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

[Kernel-packages] [Bug 1872817] Re: Workqueue: events dp_altmode_work [typec_displayport]

[Kai-Heng Feng]

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

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

Title:
  Workqueue: events dp_altmode_work [typec_displayport]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting the following was present in dmesg:

  [  242.931199] INFO: task kworker/6:2:174 blocked for more than 120 seconds.
  [  242.931210]   Tainted: G   OE 5.4.0-21-generic #25-Ubuntu
  [  242.931214] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.931218] kworker/6:2 D0   174  2 0x80004000
  [  242.931239] Workqueue: events dp_altmode_work [typec_displayport]
  [  242.931243] Call Trace:
  [  242.931260]  __schedule+0x2e3/0x740
  [  242.931270]  schedule+0x42/0xb0
  [  242.931278]  schedule_preempt_disabled+0xe/0x10
  [  242.931282]  __mutex_lock.isra.0+0x182/0x4f0
  [  242.931288]  ? __switch_to_asm+0x34/0x70
  [  242.931291]  ? __switch_to_asm+0x34/0x70
  [  242.931295]  ? __switch_to_asm+0x40/0x70
  [  242.931299]  ? __switch_to_asm+0x40/0x70
  [  242.931302]  __mutex_lock_slowpath+0x13/0x20
  [  242.931305]  mutex_lock+0x2e/0x40
  [  242.931315]  ucsi_send_command+0x2a/0x60 [typec_ucsi]
  [  242.931323]  ucsi_displayport_enter+0x90/0x180 [typec_ucsi]
  [  242.931334]  typec_altmode_enter+0x4f/0x60 [typec]
  [  242.931339]  dp_altmode_work+0xde/0xf0 [typec_displayport]
  [  242.931346]  process_one_work+0x1eb/0x3b0
  [  242.931352]  worker_thread+0x4d/0x400
  [  242.931357]  kthread+0x104/0x140
  [  242.931362]  ? process_one_work+0x3b0/0x3b0
  [  242.931365]  ? kthread_park+0x90/0x90
  [  242.931370]  ret_from_fork+0x35/0x40
  [  242.931384] INFO: task kworker/4:2:328 blocked for more than 120 seconds.
  [  242.931389]   Tainted: G   OE 5.4.0-21-generic #25-Ubuntu
  [  242.931391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.931394] kworker/4:2 D0   328  2 0x80004000
  [  242.931405] Workqueue: events_long ucsi_init [typec_ucsi]
  [  242.931407] Call Trace:
  [  242.931422]  __schedule+0x2e3/0x740
  [  242.931436]  schedule+0x42/0xb0
  [  242.931441]  schedule_timeout+0x203/0x2f0
  [  242.931449]  ? ttwu_do_activate+0x5b/0x70
  [  242.931455]  wait_for_completion+0xb1/0x120
  [  242.931461]  ? wake_up_q+0x70/0x70
  [  242.931467]  __flush_work+0x123/0x1d0
  [  242.931473]  ? worker_detach_from_pool+0xb0/0xb0
  [  242.931481]  __cancel_work_timer+0x10e/0x190
  [  242.931489]  ? kernfs_put+0xf1/0x180
  [  242.931499]  cancel_work_sync+0x10/0x20
  [  242.931507]  dp_altmode_remove+0x23/0x30 [typec_displayport]
  [  242.931520]  typec_remove+0x4b/0x8d [typec]
  [  242.931531]  device_release_driver_internal+0xf0/0x1d0
  [  242.931540]  device_release_driver+0x12/0x20
  [  242.931546]  bus_remove_device+0xe1/0x150
  [  242.931552]  device_del+0x165/0x370
  [  242.931559]  ? kfree+0x22b/0x240
  [  242.931565]  device_unregister+0x1b/0x60
  [  242.931576]  typec_unregister_altmode+0x30/0x40 [typec]
  [  242.931582]  ucsi_unregister_altmodes+0x42/0xa0 [typec_ucsi]
  [  242.931588]  ucsi_unregister_partner.part.0+0x17/0x30 [typec_ucsi]
  [  242.931594]  ucsi_init+0x179/0x1c0 [typec_ucsi]
  [  242.931600]  process_one_work+0x1eb/0x3b0
  [  242.931605]  worker_thread+0x4d/0x400
  [  242.931609]  kthread+0x104/0x140
  [  242.931614]  ? process_one_work+0x3b0/0x3b0
  [  242.931617]  ? kthread_park+0x90/0x90
  [  242.931622]  ret_from_fork+0x35/0x40

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nikolaj2154 F pulseaudio
   /dev/snd/controlC0:  nikolaj2154 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 22:16:08 2020
  InstallationDate: Installed on 2019-11-15 (151 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (10 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr

[Kernel-packages] [Bug 1872375] Re: AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi encoding backend is being used

[Kai-Heng Feng]

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

Particularly, to test the commit:
commit 487eca11a321ef33bcf4ca5adb3c0c4954db1b58
Author: Prike Liang 
Date:   Tue Apr 7 20:21:26 2020 +0800

drm/amdgpu: fix gfx hang during suspend with video playback (v2)

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

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

Title:
  AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi
  encoding backend is being used

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good morning, I'm writing this because is pretty much easily
  reproduceable in this hardware

  I discovered this when I set up an automatic permanent replay-
  recording in OBS, using FFMPEG VAAPI backend

  I usually put the system to sleep, and pretty much 100% of the times
  so far when OBS is recording something AND is using the ffmpeg-vaapi
  backend, putting the system to sleep and then waking it back, causes
  the amdgpu driver to crash no matter what

  Any other sleep/standby test made without recording using ffmpeg-vaapi
  (even using default ffmpeg software x264 backend) has not made the
  driver crash so far

  My setup:
  CPU: AMD Ryzen 5 1600
  GPU: AMD Sapphire RX 580 8GB
  RAM: 12GB DDR4 (3x4GB)
  System: Ubuntu 20.04 Focal Fossa
  Desktop: GNOME 3.36.1
  Kernel: 5.4.0-21-generic #25-Ubuntu
  Display server: X.org

  Here is the system crashing logs dmesg

  (Don't mind the hostname, it's a desktop PC not a thinkpad)

  Apr 13 01:49:02 haru-ThinkPad-T440s kernel: [   64.100393] PM: suspend entry 
(deep)
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.108441] Filesystems sync: 
0.008 seconds
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.108716] Freezing user 
space processes ... (elapsed 0.002 seconds) done.
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.111290] OOM killer 
disabled.
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.111291] Freezing remaining 
freezable tasks ... (elapsed 0.000 seconds) done.
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.112125] printk: Suspending 
console(s) (use no_console_suspend to debug)
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.113085] serial 00:04: 
disabled
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.113317] parport_pc 00:03: 
disabled
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.151545] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.151713] sd 1:0:0:0: [sdc] 
Synchronizing SCSI cache
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.151720] sd 10:0:0:0: [sdd] 
Synchronizing SCSI cache
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.151724] sd 11:0:0:0: [sdb] 
Synchronizing SCSI cache
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.151807] sd 0:0:0:0: [sda] 
Stopping disk
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.152043] sd 1:0:0:0: [sdc] 
Stopping disk
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.157544] sd 10:0:0:0: [sdd] 
Stopping disk
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.612461] ACPI: Preparing to 
enter system sleep state S3
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.925094] PM: Saving 
platform NVS memory
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.925117] Disabling non-boot 
CPUs ...
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.927049] smpboot: CPU 1 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.931788] smpboot: CPU 2 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.934941] IRQ 37: no longer 
affine to CPU3
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.935968] smpboot: CPU 3 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.940098] smpboot: CPU 4 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.943503] IRQ 27: no longer 
affine to CPU5
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.943510] IRQ 28: no longer 
affine to CPU5
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.944533] smpboot: CPU 5 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.947662] IRQ 44: no longer 
affine to CPU6
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.948697] smpboot: CPU 6 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.952180] IRQ 30: no longer 
affine to CPU7
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.953216] smpboot: CPU 7 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.957820] smpboot: CPU 8 is 
now offline
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.961177] IRQ 39: no longer 
affine to CPU9
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.961187] IRQ 63: no longer 
affine to CPU9
  Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [   64.962201] smpboot: CPU 9 is 
now offline
  Apr 13 01:49:08 har

[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040

[Kai-Heng Feng]

Can you please test 5.4.0-24?

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

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

Title:
  Intel GPU causes BUG: kernel NULL pointer dereference, address:
  0040

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After playing Gurumin: A Monstrous Adventure for some time, the system
  crashed in an unrecoverable way. REISUB was required to get some logs.

  This crash happened with default Ubuntu's kernel, default Mesa and
  default Xorg session. I never observed a crash this serious using the
  intel Xorg driver. However, using the default (modesetting), the
  following unrecoverable crash happened after two hours:

  The syslog contains the following:

  Apr  2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php 
session files...
  Apr  2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: 
Succeeded.
  Apr  2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php 
session files.
  Apr  2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: 
Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel 
NULL pointer dereference, address: 0040
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: 
supervisor read access in kernel mode
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: 
error_code(0x) - not-present page
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops:  
[#1] SMP PTI
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 
200385 Comm: xfwm4 Tainted: P   O  5.4.0-21-generic #25-Ubuntu
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware 
name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 
0010:i915_active_acquire+0xe/0x80 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 
c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 
0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 
01 f0 0f b1 53 38 75 f2 45 31
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 
0018:bd8446f979c8 EFLAGS: 00010286
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: 
 RBX: 9c477afaca80 RCX: 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 
9c4633bfc500 RSI: 9c477afaca80 RDI: 0008
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: 
bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 
00014000 R11: 9c47d1918b00 R12: 9c4633bfc500
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 
0008 R14: 9c4633bfc500 R15: 9c47d6f4db00
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS:  
7f99a3564a80() GS:9c47de28() knlGS:
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS:  0010 DS: 
 ES:  CR0: 80050033
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 
0040 CR3: 000556ca0001 CR4: 003606e0
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: 
 DR1:  DR2: 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: 
 DR6: fffe0ff0 DR7: 0400
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace:
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477]  
i915_active_ref+0x24/0x200 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521]  
i915_vma_move_to_active+0x74/0xf0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564]  
eb_submit+0xff/0x440 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608]  
i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615]  ? 
sock_def_readable+0x40/0x70
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618]  ? 
__kmalloc_node+0x205/0x320
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668]  
i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717]  ? 
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284742]  
drm_ioctl_kernel+0xae/0xf0 [drm]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284761]

[Kernel-packages] [Bug 1864288] Re: No boot after an update.

[Kai-Heng Feng]

If it can't even reach GRUB, is it a bug to Linux kernel?

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

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

Title:
  No boot after an update.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After an update, my computer will no longer boot. I only see a black screen.  
No grub menu. After a couple of forced restarts, the file system gets corrupt. 
This happens both on XUbuntu 18.04.4 and 19.10.
  I am not sure if it had something to do with RAM upgrade or was it just a 
coincidence that I replaced a 4GB RAM module for an 8GB module and the next day 
my computer would not boot after an update. With clean install to any version 
everything works fine. It might be of some significance to know that my Assus 
VivoBook with Ryzen3 CPU has 4GB somewhere embedded and a separate 4GB module 
in the SODIMM slot, so it reports 8GB of RAM. After upgrading the RAM module to 
8GB, it reports 12GB of RAM. I no longer had the patience to test if this would 
happen with the old 4GB module. 

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown]
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sat Feb 22 10:57:29 2020
  InstallationDate: Installed on 2020-02-22 (0 days ago)
  InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-update
  UpgradeStatus: No upgrade log present (fresh install) as update crashes.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rada   1170 F pulseaudio
   /dev/snd/controlC0:  rada   1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-22 (0 days ago)
  InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/08/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  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.:bvrX512DA.302:bd03/08/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rada   1170 F pulseaudio
   /dev/snd/controlC0:  rada   1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-22 (0 days ago)
  InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/08/2019
  dmi.bios.vendor: American Megatrends Inc.
  d

[Kernel-packages] [Bug 1861219] Re: QLogic FC paths added when issue_lip

[Kai-Heng Feng]

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

Particularly,
commit 3c75ad1d87c7d277c6174051b98757fe981d592d
Author: Himanshu Madhani 
Date:   Tue Dec 17 14:06:04 2019 -0800

scsi: qla2xxx: Remove defer flag to indicate immeadiate port loss

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

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

Title:
  QLogic FC paths added when issue_lip

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My QLogic direct-connect SANboot host with Ubuntu Server 18.04 LTS is
  seeing paths added during testing.  Specifically added when running
  the command below:

  echo 1 > /sys/class/fc_host/host15/issue_lip

  There should be four paths total but if I run the command above five
  times, I will see nine total paths.  The server will hang and require
  a reboot eventually as multiple hung_task_timeout errors show up in
  logs.

  Information on HBAs below:

  root@ICTM1607S02H4:~# cat /sys/class/fc_host/host*/symbolic_name
  QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k
  QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k
  QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k
  QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k

  An example of what a volume looks like in multipath -ll after the
  issue_lip occurs:

  root@ICTM1607S02H4:~# multipath -ll
  36d039ea0003ebb14009e58b1fabf dm-3 NETAPP,INF-01-00
  size=160G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' 
wp=rw
  |-+- policy='service-time 0' prio=50 status=active
  | |- 13:0:0:0   sdl 8:176  active ready running
  | |- 15:0:0:0   sdq 65:0   active ready running
  | `- 15:0:1:0   sdv 65:80  active ready running
  `-+- policy='service-time 0' prio=10 status=enabled
|- 12:0:0:0   sdb 8:16   active ready running
`- 14:0:0:0   sdc 8:32   active ready running

  Notice how a path is added after issue_lip.

  1) version_signature.log
  Ubuntu 4.15.0-74.84-generic 4.15.18

  2) lspci -vnvn output is in a file attached.

  
  root@ICTM1607S02H4:~# lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  
  root@ICTM1607S02H4:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 4.15.0.74.76
Candidate: 4.15.0.74.76
Version table:
   *** 4.15.0.74.76 500
  500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-updates/main 
amd64 Packages
  500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-security/main 
amd64 Packages
  100 /var/lib/dpkg/status
   4.15.0.20.23 500
  500 http://repomirror-ict.eng.netapp.com/ubuntu bionic/main amd64 
Packages

  I expected the bus reset to quickly add and remove, but it seems
  removal is not happening.  The number of paths grow after each bus
  reset causing instability with the OS.

  I have attached logs.zip which contains four files.

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

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

[Kernel-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem

[Kai-Heng Feng]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  Ubuntu 18.04 and 19.04 new ethernet problem

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

Bug description:
  Ubuntu 19.04 (64 bit) on OptiPlex-7010
  On every power on I have no wired Ethernet connection or even an icon to 
enable it. After a restart (soft boot) it comes back again. This appears to be 
different from another bug reported which states that the Ethernet cable has to 
be unplugged during power on. In my issue, I can leave the Ethernet cable 
plugged in and it works fine. It just doesn't work during first power on boot.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-01-26 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.1.1 dev eno1 proto dhcp metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-74-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  bea41631-df6c-3de0-ac4c-7606d1313303  ethernet  
1580229876  Tue 28 Jan 2020 08:44:36 AM PST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  bea41631-df6c-3de0-ac4c-7606d1313303  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

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

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

Status in linux package in Ubuntu:
  Triaged

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Kai-Heng Feng]

Please test this kernel:
https://people.canonical.com/~khfeng/lp1872984-2/

Which disables L0s.

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

Title:
  RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04
  - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  
  Device is unable to scan for networks and error occurs when attempting to 
turn on

[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

[Kai-Heng Feng]

Please test latest 20.04. SoF DMIC should work now.

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

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions

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

[Kernel-packages] [Bug 1872758] Re: System doesn't wake up after suspend on HP Pavillon 15-CS1022NL

[Kai-Heng Feng]

Can you please attach `journalctl -b -1 -k` after the issue happened.

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

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

Title:
  System doesn't wake up after suspend on HP Pavillon 15-CS1022NL

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1)
  lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  2)
  I think the bug is in the Kernel 5.3.0-46:

  apt-cache policy linux-headers-5.3.0-46-generic
  linux-headers-5.3.0-46-generic:
    Installato: 5.3.0-46.38~18.04.1
    Candidato:  5.3.0-46.38~18.04.1
    Tabella versione:
    *** 5.3.0-46.38~18.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) When I wake up the laptop from suspension the laptop wakes up
  correctly.

  4) When I wake up the laptop from suspension the laptop doesn't wake
  up: I can hear the fans and I can see the keyboard backlight (and
  Power light) on but the screen is black.

  Furthermore I tried different Kernels and almost each version has the
  same problem. The first one which doesn't have this bug is the
  4.18.20-041820-generic version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-46-generic 5.3.0-46.38~18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Apr 14 17:30:12 2020
  InstallationDate: Installed on 2020-02-24 (49 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1868134] Re: Headphones Audio Out Not Delivering Sound

[Kai-Heng Feng]

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

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

Title:
  Headphones Audio Out Not Delivering Sound

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  DELL M5510

  ~ $ cat /proc/asound/cards
   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xddc28000 irq 128

  4.15.0-91
  Exhibits no sound via headphones

  4.15.0-88
  No issue with sound via headphones

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  

  *** Problem in linux-image-4.15.0-88-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Press any key to continue... ^C

  ~ $ cat /proc/version_signature > version.log
  ~ $ sudo lspci -vnvn > lspci-vnvn.log
  [sudo] password:   
  ~ $ 

  Not sure why the above commands are not creating the required info.

  Thanks

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

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

[Kernel-packages] [Bug 1870816] Re: received update then got stuck on blackscreen in login screen. Changed "qiuet splash" to "radeon.modeset=0" in order to boot normally.

[Kai-Heng Feng]

Can you please test previous kernel versions?

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

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

Title:
  received update then got stuck on blackscreen in login screen. Changed
  "qiuet splash" to "radeon.modeset=0" in order to boot normally.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I received an update yesterday 3/4/2020 that had important security
  and kernel updates, so I launched it as I usually do with any security
  or kernel updates I receive. It downloaded and installed the necessary
  files and requested a restart.

  I restarted and kept receiving a black screen with only my mouse
  visible on the login screen and nothing I tried worked until I went to
  Grub and pressed "e" then changed the "qiuet splash" to
  "radeon.modeset=0" (since my graphics card is ATI Radeon) in order to
  boot normally. And it worked!

  But that means that there's a bug in the latest update release and I
  don't like to change in the system files in order to boot my laptop.
  So please fix and let me know when can I revert back what I did and
  login normally without the change I made.

  Thank you

  Version: Ubuntu 19.10
  GNOME: 3.34.2

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:06:55 2020
  InstallationDate: Installed on 2020-03-11 (24 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-04-04 08:56:31.608736
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   None

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

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

[Kernel-packages] [Bug 1862669] Re: wifi and bluetooth problem hp probook 4520s, chipset rt3090

[Kai-Heng Feng]

Unload btusb and see if it helps.

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

Title:
  wifi and bluetooth problem hp probook 4520s, chipset rt3090

Status in linux package in Ubuntu:
  Expired

Bug description:
  with the rt3090 wifi chip there is a conflict, which makes the wifi
  extremely slow, the bluetooth cannot be deactivated independent of the
  wifi and does not detect devices.

  I tried many methods to fix it, but I definitely think it's the kernel
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horacio1707 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-09 (3 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Hewlett-Packard HP ProBook 4520s
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic 
root=UUID=766b6c57-4110-40d6-a8f1-2d236a3e2188 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-76-generic N/A
   linux-backports-modules-4.15.0-76-generic  N/A
   linux-firmware 1.173.14
  Tags:  tricia
  Uname: Linux 4.15.0-76-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.61
  dmi.board.name: 1413
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.37:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horacio1707 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 19.3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-09 (3 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Hewlett-Packard HP ProBook 4520s
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic 
root=UUID=766b6c57-4110-40d6-a8f1-2d236a3e2188 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-76-generic N/A
   linux-backports-modules-4.15.0-76-generic  N/A
   linux-firmware 1.173.14
  Tags:  tricia
  Uname: Linux 4.15.0-76-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.61
  dmi.board.name: 1413
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.37:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

[Kai-Heng Feng]

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [RTL810xE] No ethernet connection

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions

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

[Kernel-packages] [Bug 1872634] Re: Webcam Z-Star 305b doesn't work in Ubuntu (again)

[Kai-Heng Feng]

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

  lsmod |grep gspca output is:

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

  lsusb output is:

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

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

  I've tried cheese, vlc and guvcview.

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

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

  Thanks in advance!

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

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

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

[Kernel-packages] [Bug 1807155] Re: Laptop doesn't wake up from deep sleep.

[Kai-Heng Feng]

Anton,

Can you please test 20.04? It should improve a lot.

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

Title:
  Laptop doesn't wake up from deep sleep.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While on battery power, Asus Zenbook UX461U laptop can't wake up from
  suspend with mem_sleep_default=deep kernel option.

  Upon opening the lid or pressing the power button the power LED
  switches from blinking to constant light, the keyboard LEDs blink
  instantly, but nothing more happens. Apart from the power LED the
  laptop doesn't show any signs of operation. The keyboard backlight
  doesn't work. The only way out of this state is powering the laptop
  off by long pressing the power button.

  On AC power, the laptop resumes from deep sleep normally.

  Deep sleep is crucial, because without the mem_sleep_default=deep
  option battery drain is very high (several percent per hour).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-12-generic 4.18.0-12.13
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  misha  2527 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  6 16:24:58 2018
  HibernationDevice: RESUME=UUID=28642731-be8e-4c6b-9cfe-74d637c87bf0
  InstallationDate: Installed on 2018-07-30 (129 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX461UA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-12-generic N/A
   linux-backports-modules-4.18.0-12-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-12-01 (5 days ago)
  dmi.bios.date: 03/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX461UA.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX461UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX461UA.312:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnUX461UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX461UA
  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/1807155/+subscriptions

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

[Kernel-packages] [Bug 1870185] Re: [Z97-HD3, Intel Haswell HDMI, Digital Out, HDMI] Sound is distorted

[Kai-Heng Feng]

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

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

Title:
  [Z97-HD3, Intel Haswell HDMI, Digital Out, HDMI] Sound is distorted

Status in linux package in Ubuntu:
  New

Bug description:
  I get horribly cracking sound and distortion with my mb Gigabyte
  Z97-HD3. This MB is using the Realtek ALC1150 Chipset. I run linux
  kernel 5.5 and Ubuntu 18 and I tried all the answers from this post
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421 but it
  didnt work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.0-050500-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juse   2276 F pulseaudio
   /dev/snd/controlC2:  juse   2276 F pulseaudio
   /dev/snd/controlC0:  juse   2276 F pulseaudio
    juse  20415 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 18:29:39 2020
  InstallationDate: Installed on 2020-03-25 (6 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Audio Interno - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [Z97-HD3, Intel Haswell HDMI, Digital Out, HDMI] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-01T18:24:32.365284


  
  Alsa information: 
http://alsa-project.org/db/?f=34993509f6ec8878f4d804039b1633d3e140db16

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

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

[Kernel-packages] [Bug 1852420] Re: /var/log/syslog and /var/log/kern.log reports millions of nvme errors

[Kai-Heng Feng]

anydoby,

Does your system use the same Samsung NVMe?

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

Title:
  /var/log/syslog and /var/log/kern.log reports millions of nvme errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, 
  since upgrading Ubuntu from 18.04 to 19.10 I see tons of error messages in 
/var/log/syslog and /var/log/kern.log saying:

  Nov 13 11:18:50 detlef-Precision-5520 kernel: [ 2342.863294] pcieport 
:00:1d.0: AER: Corrected error received: :04:00.0
  Nov 13 11:18:50 detlef-Precision-5520 kernel: [ 2342.863305] nvme 
:04:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
(Receiver ID)
  Nov 13 11:18:50 detlef-Precision-5520 kernel: [ 2342.863309] nvme 
:04:00.0: AER:   device [144d:a804] error status/mask=0001/6000
  Nov 13 11:18:50 detlef-Precision-5520 kernel: [ 2342.863312] nvme 
:04:00.0: AER:[ 0] RxErr 
  Nov 13 11:18:50 detlef-Precision-5520 kernel: [ 2342.895923] pcieport 
:00:1d.0: AER: Corrected error received: :04:00.0

  
  Im running on
  5.3.0-22-generic #24-Ubuntu SMP Sat Nov 9 17:34:30 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  I have a Samsung SSD 960 Evo in my system and it worked fine before upgrading.
  However the system runs fine  ( no crashes or other errors) but these 
messages are very annoying and it lead to a "no space left on device" once with 
crashing entirely.

  Thanks,
  detlef
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  detlef 1914 F pulseaudio
   /dev/snd/pcmC0D3p:   detlef 1914 F...m pulseaudio
   /dev/snd/pcmC0D0c:   detlef 1914 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-05 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Precision 5520
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic 
root=UUID=d5ce3ce0-94d8-45e4-b4c3-5446497c141b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-22-generic N/A
   linux-backports-modules-5.3.0-22-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd05/23/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1870014] Re: task blocked too long

[Kai-Heng Feng]

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

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

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

Title:
  task blocked too long

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I plugged in the EasyCap device, then started VLC to read from it.
  Nothing worked, and I saw the following call traces from the kernel:

  
  Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB 
device number 41 using xhci_hcd
  Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor 
read/64, error -71
  Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor 
read/64, error -71
  Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power 
cycle
  Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot 
enable. Maybe the USB cable is bad?
  Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot 
enable. Maybe the USB cable is bad?
  Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to 
enumerate USB device
  Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB 
device number 44 using xhci_hcd
  Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 
altsetting 1 bulk endpoint 0x83 has invalid maxpa
  cket 256
  Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device 
found, idVendor=1b71, idProduct=3002
  Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device 
strings: Mfr=3, Product=4, SerialNumber=2
  Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007
  Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: 
fushicai
  Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 
3002
  Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai 
USBTV007 Audio-Video Grabber
  Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, 
device number 44
  Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long 
(3978 > 3967), lowering kernel.perf_event_max_sam
  ple_rate to 50250
  Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 
blocked for more than 120 seconds.
  Mar 31 23:55:36 cerberus kernel: [50024.968512]   Tainted: G  IOE 
   4.15.0-94-generic #95-Ubuntu
  Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251  
1 0x
  Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace:
  Mar 31 23:55:36 cerberus kernel: [50024.968535]  __schedule+0x24e/0x880
  Mar 31 23:55:36 cerberus kernel: [50024.968539]  schedule+0x2c/0x80
  Mar 31 23:55:36 cerberus kernel: [50024.968542]  
schedule_preempt_disabled+0xe/0x10
  Mar 31 23:55:36 cerberus kernel: [50024.968547]  
__mutex_lock.isra.5+0x276/0x4e0
  Mar 31 23:55:36 cerberus kernel: [50024.968551]  
__mutex_lock_slowpath+0x13/0x20
  Mar 31 23:55:36 cerberus kernel: [50024.968554]  ? 
__mutex_lock_slowpath+0x13/0x20
  Mar 31 23:55:36 cerberus kernel: [50024.968557]  mutex_lock+0x2f/0x40
  Mar 31 23:55:36 cerberus kernel: [50024.968569]  _vb2_fop_release+0x29/0xa0 
[videobuf2_v4l2]
  Mar 31 23:55:36 cerberus kernel: [50024.968573]  vb2_fop_release+0x31/0x40 
[videobuf2_v4l2]
  Mar 31 23:55:36 cerberus kernel: [50024.968593]  v4l2_release+0x38/0x80 
[videodev]
  Mar 31 23:55:36 cerberus kernel: [50024.968600]  __fput+0xea/0x220
  Mar 31 23:55:36 cerberus kernel: [50024.968604]  fput+0xe/0x10
  Mar 31 23:55:36 cerberus kernel: [50024.968611]  task_work_run+0x9d/0xc0
  Mar 31 23:55:36 cerberus kernel: [50024.968620]  
exit_to_usermode_loop+0xc0/0xd0
  Mar 31 23:55:36 cerberus kernel: [50024.968623]  do_syscall_64+0x121/0x130
  Mar 31 23:55:36 cerberus kernel: [50024.968630]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447
  Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 
EFLAGS: 0293 ORIG_RAX: 0003
  Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX:  RBX: 
0064 RCX: 7f6411c26447
  Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX:  RSI: 
7f63da9bd930 RDI: 0064
  Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP:  R08: 
 R09: 
  Mar 31 23:55:36 cerberus kernel: [50024.968642] R10:  R11: 
0293 R12: 7f628d4c5fa0
  Mar 31 23:55:36 cerberus kernel: [50024.968644] R13:  R14: 
7f640422d381 R15: 7f63da9bd930
  Mar 31 23:55:36 cerberus kernel: [50024.96

[Kernel-packages] [Bug 1869993] Re: Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes entire system

[Kai-Heng Feng]

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

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

Title:
  Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes
  entire system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.

  While hunting for answers as to why this occurs I stumbled upon my
  dmesg log stating

  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel

  
  and

  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }

  
  and

  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

  Hope this helps.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1826 F pulseaudio
   /dev/snd/controlC2:  steve  1826 F pulseaudio
   /dev/snd/controlC1:  steve  1826 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-16 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=ce2b1a08-f3b8-4886-86fb-1c67ae558f66 ro
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd09/17/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1870208] Re: adding GUI to Ubuntu Server 20.04 results in no log in screen

[Kai-Heng Feng]

Isn't the fix in GDM already merged?

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

Title:
  adding GUI to Ubuntu Server 20.04 results in no log in screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apt install ubuntu-desktop on Servers with embedded Matrox G200
  Graphics Controller issue

  After install/reboot there is no gdm login displayed
  Editing /etc/gdm3/custom.conf to force gdm to use Xorg instead of Wayland 
fixed the issue

  Ubuntu 19.10 has the same problem
  Same issue found installing the Desktop Version

  Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery
  mode

  
  Conclusion being - should we try to fix this?

  There may already be a fix in process
  https://gitlab.gnome.org/GNOME/gdm/issues/364
  Here are three proposals if the above does not pan out, one of these should 
work, Number 3 is preferred
  1. Fix Wayland’s support for G200
  2. Rip out the broken support for Matrox G200 in Wayland
  3. Convince Canonical to blacklist the G200 from Wayland during install and 
force Xorg automatically

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

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

[Kernel-packages] [Bug 1870350] Re: Unable to reconnect to WiFI network after suspend

[Kai-Heng Feng]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Unable to reconnect to WiFI network after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After having the PC, A Dell XPS 15 suspend and hit deep sleep I then
  re-open the lid the morning after and every time after this use case
  it will fail to re-connect to WiFI, some times it does not even show
  any networks available.

  Only way to get the machine back on the WiFI network is to reboot.

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

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

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

[Kernel-packages] [Bug 1868898] Re: Ubuntu 20.04 clean install : autostandby feature

[Kai-Heng Feng]

Can you please test 5.4.0-24?

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

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

Title:
  Ubuntu 20.04 clean install : autostandby feature

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Have ubuntu 20.04 development branch on my laptop and my desktop.

  Noticed yesterday, my laptop was idle for a while and the power light
  was on and keypress didnt wake it up. Pressing power button didnt wake
  it up either.

  On my tower pc I use tandby on power press and it works great.

  Problem seems to be in auto standby feature. I remember this bug in 18.04 
development branch as well.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  1606 F pulseaudio
   /dev/snd/controlC0:  steve  1606 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-21 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Dell Inc. Inspiron 5765
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  StagingDrivers: exfat
  Tags:  focal staging
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/17/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0DM01M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5765
  dmi.product.sku: 076A
  dmi.product.version: 1.1.1
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1868534] Re: Ubuntu 18.04.4 boot stops at 'loading initial ramdisk' when AC is unplugged.

[Kai-Heng Feng]

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

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

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

Title:
  Ubuntu 18.04.4 boot stops at 'loading initial ramdisk' when AC is
  unplugged.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With AC plugged everything works. 
  With the AC plugged I can start the computer and just after the Ubuntu logo 
appears I can unplug  the AC. After the Ubuntu logo everything works fine 
without AC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pep2001 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5491
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.173.16
  Tags:  bionic
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0WCMKT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0WCMKT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1856413] Re: Asus UX580 touchpad stops working

[Kai-Heng Feng]

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

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

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

Title:
  Asus UX580 touchpad stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Periodically after restart touchpad on my UX580 laptop stops working 
completely. 
  Closing the lid and letting the laptop to suspend, and then re-opening the 
lid activates the touchpad.
  Attached xinput list output.

  This is Ubuntu 19.10, latest kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pavel  2048 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (47 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2706 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9909f5be-7ef4-4a37-b5c1-c07caf97ff8f ro quiet splash 
resume=UUID=cc044a08-3549-4c51-9964-c4e396792368 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  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.:bvrUX550GDX.308:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  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/1856413/+subscriptions

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

[Kernel-packages] [Bug 1870451] Re: I accepted SW update and now doesnt exit sleep

[Kai-Heng Feng]

Can you please test 4.15.0-96?

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

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

Title:
  I accepted SW update and now doesnt exit sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I very recently accepted a SW update from Ubuntu after that when my
  laptop goes to sleep i cant wake it , i have to power cycle.. This was
  working before the update.

  HP ELiteBook 8440p
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-91-generic 4.15.0-91.92
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 17:01:25 2020
  InstallationDate: Installed on 2018-10-11 (539 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=ac0d7bbe-3453-4b2e-ad03-06d82cda4739 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-91-generic N/A
   linux-backports-modules-4.15.0-91-generic  N/A
   linux-firmware 1.173.17
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.11
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.31
  dmi.chassis.asset.tag: AG021536
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1870538] Re: ryzen 5 3600x hard lockup

[Kai-Heng Feng]

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

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

Title:
  ryzen 5 3600x hard lockup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System randomly freezes and requires a hard reset. Very frequently it
  happens when trying to wake it up from a period of inactivity. (after
  the screen has turned off). Almost daily occurrence.

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  
  Linux MartoBeast 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-45-generic 5.3.0-45.37
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2642 F pulseaudio
   /dev/snd/controlC0:  martin 2642 F pulseaudio
   /dev/snd/controlC2:  martin 2642 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 08:46:11 2020
  InstallationDate: Installed on 2019-12-08 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[Kai-Heng Feng]

Hmm, please try kernel parameter "dis_ucode_ldr" to disable microcode
loading.

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862888] Re: Boot hang on ASUS WS X299 SAGE

[Kai-Heng Feng]

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

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

Title:
  Boot hang on ASUS WS X299 SAGE

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Upstream kernels since 5.3 fail to boot on the ASUS WS X299 SAGE
  motherboard with firmware version 1201. This is the result of an
  infinite loop while trying to parse a malformed ACPI table. It is
  suspected to affect other ASUS motherboards, but I have no first
  hand proof of that.

  This is particularly troublesome for bionic HWE installs, which
  will then fail to boot after upgrading to the 5.3 series eoan
  kernel.

  [Test Case]

  Try to boot an ASUS WS X299 SAGE computer with firmware version 1201.

  Eoan and Focal kernels will fail to boot.

  Upstream kernel 5.6-rc1 will boot succressfully.

  
  [Fix]

  Cherry pick upstream  2b73ea379624 ("x86/boot: Handle malformed SRAT
  tables during early ACPI parsing")

  [Regression Potential]

  Low. Any system affected by this patch is already failing to boot.

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

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

[Kernel-packages] [Bug 1870350] Re: Unable to reconnect to WiFI network after suspend

[Kai-Heng Feng]

Please attach log after the wifi fails to work...

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

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

Title:
  Unable to reconnect to WiFI network after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After having the PC, A Dell XPS 15 suspend and hit deep sleep I then
  re-open the lid the morning after and every time after this use case
  it will fail to re-connect to WiFI, some times it does not even show
  any networks available.

  Only way to get the machine back on the WiFI network is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:25:52 2020
  InstallationDate: Installed on 2020-03-31 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  IpRoute:
   default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp59s0 scope link metric 1000 
   192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
   DORIAN  2c3f821d-0865-4747-974a-2f861ee0dc38  wifi  1585833939  tor  2 apr 
2020 15:25:39  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp59s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/DORIAN.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp59s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  DORIAN  
2c3f821d-0865-4747-974a-2f861ee0dc38  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp59s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcus 2665 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-31 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=8f9547c7-2727-47a9-859e-b743a8b8553c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[Kai-Heng Feng]

One possible choice is to use the 5.7 kernel here:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1876859] Re: Support DMIC micmute LED on HP platforms

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1866766 stella

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

Title:
  Support DMIC micmute LED on HP platforms

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:
  Incomplete
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  DMIC micmute LED on HP platforms doesn't work.

  [Fix]
  Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to 
control micmute.

  [Test]
  After applying the fix, micmute LED can correctly indicate the status of 
micmute.

  [Regression Potential]
  Low. For now it only affects one platform, and it doesn't touch any core part 
of the subsystem.

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

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

[Kernel-packages] [Bug 1876859] [NEW] Support DMIC micmute LED on HP platforms

[Kai-Heng Feng]

Public bug reported:

[Impact]
DMIC micmute LED on HP platforms doesn't work.

[Fix]
Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to 
control micmute.

[Test]
After applying the fix, micmute LED can correctly indicate the status of 
micmute.

[Regression Potential]
Low. For now it only affects one platform, and it doesn't touch any core part 
of the subsystem.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

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

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

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

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


** Tags: oem-priority originate-from-1866766 stella

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

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

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

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

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

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

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

Title:
  Support DMIC micmute LED on HP platforms

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:
  Incomplete
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  DMIC micmute LED on HP platforms doesn't work.

  [Fix]
  Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to 
control micmute.

  [Test]
  After applying the fix, micmute LED can correctly indicate the status of 
micmute.

  [Regression Potential]
  Low. For now it only affects one platform, and it doesn't touch any core part 
of the subsystem.

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

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

[Kernel-packages] [Bug 1876908] Re: Screen not locked after resume from suspend

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Screen not locked after resume from suspend

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Whenever I suspend my laptop, and then resume, I get directly to the
  gnome-shell desktop without having to log in.

  This used to work perfectly before the upgrade to 20.04.

  For information, I'm using pure gnome-shell, not Unity, in case that
  matters.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv1699 F pulseaudio
   /dev/snd/controlC0:  juloliv1699 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 14:08:39 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-07 (87 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-24 (10 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  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.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  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/gnome-shell/+bug/1876908/+subscriptions

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

[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake

[Kai-Heng Feng]

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

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

Title:
  Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in thermald package in Ubuntu:
  Incomplete

Bug description:
  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).

  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.

  If dptfxtract is executed, then power limit will be higher than power
  up value, but most of the users will use out of the box setup. So this
  need a workaround.

  This workaround will ignore any power limit less than the power up
  power limit.

  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

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

[Kernel-packages] [Bug 1812889] Re: WARNING: CPU: 0 PID: 1012 at /build/linux-pWDSBu/linux-3.13.0/include/drm/ttm/ttm_bo_driver.h:878 qxl_surface_id_alloc+0x37e/0x410 [qxl]()

[Kai-Heng Feng]

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

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

Title:
  WARNING: CPU: 0 PID: 1012 at /build/linux-
  pWDSBu/linux-3.13.0/include/drm/ttm/ttm_bo_driver.h:878
  qxl_surface_id_alloc+0x37e/0x410 [qxl]()

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [ cut here ]
  WARNING: CPU: 0 PID: 1012 at 
/build/linux-pWDSBu/linux-3.13.0/include/drm/ttm/ttm_bo_driver.h:878 
qxl_surface_id_alloc+0x37e/0x410 [qxl]()
  Modules linked in: snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
snd_page_alloc snd_seq_midi snd_seq_midi_event crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_rawmidi aesni_intel aes_x86_64 lrw gf128mul snd_seq 
glue_helper ablk_helper cryptd snd_seq_device snd_timer rfcomm bnep qxl 
bluetooth ttm drm_kms_helper serio_raw snd binfmt_misc mac_hid drm soundcore 
i2c_piix4 parport_pc ppdev lp parport psmouse pata_acpi floppy
  CPU: 0 PID: 1012 Comm: Xorg Not tainted 3.13.0-164-generic #214-Ubuntu
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 
04/01/2014
    880066bcfbf0 8173c0c8 
   0009 880066bcfc28 8106db6d 8800368d9c00
   0397 8800368d9c48 88006974 880069740a90
  Call Trace:
   [] dump_stack+0x64/0x80
   [] warn_slowpath_common+0x7d/0xa0
   [] warn_slowpath_null+0x1a/0x20
   [] qxl_surface_id_alloc+0x37e/0x410 [qxl]
   [] qxl_bo_check_id+0x32/0x50 [qxl]
   [] qxl_release_reserve_list+0x9c/0xe0 [qxl]
   [] qxl_execbuffer_ioctl+0x28a/0x8e0 [qxl]
   [] drm_ioctl+0x4a5/0x640 [drm]
   [] ? do_mmap_pgoff+0x381/0x400
   [] ? common_mmap+0x4b/0x60
   [] do_vfs_ioctl+0x2e3/0x4d0
   [] SyS_ioctl+0x81/0xa0
   [] system_call_fastpath+0x26/0x2b
  ---[ end trace b2f9eaa9fc130ca9 ]---

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

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

[Kernel-packages] [Bug 1876963] Re: Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04

[Kai-Heng Feng]

Proprietary wl driver might be a better choice:
$ sudo apt install bcmwl-kernel-source

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

Title:
  Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am am experiencing slow wifi for a Linksys WMP54GS v1.0 wireless PCI
  card with Ubuntu Server 20.04 installed, e.g. apt-get has taken 18
  minutes 41 seconds to fetch 459Kb.

  Following the advice from
  https://ubuntuforums.org/showthread.php?t=2214110, I have installed
  the firmware-b43-installer package. The card is recognised and is
  sometimes allocated an IP. When it is connected, it is very slow.

  Using the wireless-info tool the logs for the wireless system
  configuration is given below. As shown in the logs the b43-pci-bridge
  driver is outputting an error message concerning the swiotlb is full.

  Has anybody managed to get the Linksys WMP54GS v1.0 card working
  on Ubuntu Server 20.04 using the b43 firmware supplied in package 
firmware-b43-installer?

  Since the log was produced I have also tired setting the REG_DOMAIN in
  /etc/default/crda but still does not work.

  ## wireless info START ##

  Report from: 04 May 2020 09:24 UTC +

  Booted last: 04 May 2020 00:00 UTC +

  Script from: 22 Oct 2018 03:34 UTC +

  # release ###

  Distributor ID: Ubuntu
  Description: Ubuntu 20.04 LTS
  Release: 20.04
  Codename: focal

  # kernel 

  Linux 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020
  x86_64 x86_64 x86_64 GNU/Linux

  Parameters: ro, maybe-ubiquity

  # desktop ###

  sed: can't read /root/.dmrc: No such file or directory

  Could not be determined.

  # lspci #

  04:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10)
   Subsystem: Packard Bell B.V. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
[1631:e035]
   Kernel driver in use: 8139too

  04:07.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 
802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
   Subsystem: Linksys WMP54GS v1.0 802.11g Wireless-G PCI Adapter with 
SpeedBooster [1737:0015]
   Kernel driver in use: b43-pci-bridge

  # lsusb #

  Bus 001 Device 005: ID 040b:650a Weltrend Semiconductor
  Bus 001 Device 004: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link 
DUB-H4 USB 2.0 Hub
  Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 046a:010e Cherry GmbH USB Wireless Device
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  # PCMCIA card info ##

  'pccardctl' is not installed (package "pcmciautils").

  # rfkill 

  ./wireless-info: line 192: rfkill: command not found

  # secure boot ###

  'mokutil' is not installed (package "mokutil").

  # lsmod #

  b43 417792 0
  cordic 16384 1 b43
  bcma 65536 1 b43
  mac80211 843776 1 b43
  cfg80211 704512 2 b43,mac80211
  libarc4 16384 1 mac80211
  mxm_wmi 16384 1 nouveau
  wmi 32768 2 mxm_wmi,nouveau
  ssb 73728 1 b43

  # interfaces 

  # ifconfig ##

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback  brd 
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: eth_lan0:  mtu 1500 qdisc fq_codel 
state DOWN group default qlen 1000
  link/ether  brd 
  3: wlan0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
  link/ether  brd 

  # iwconfig ##

  eth_lan0 no wireless extensions.

  lo no wireless extensions.

  wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

  # route #

  # resolv.conf ###

  [777 root '/etc/resolv.conf' -> '../run/systemd/resolve/stub-
  resolv.conf']

  nameserver 127.0.0.53
  options edns0

  # network managers ##

  Installed:

   None found.

  Running:

   None found.

  # NetworkManager info #

[Kernel-packages] [Bug 1876963] Re: Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04

[Kai-Heng Feng]

Probably a good idea to attach full dmesg here...

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

Title:
  Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am am experiencing slow wifi for a Linksys WMP54GS v1.0 wireless PCI
  card with Ubuntu Server 20.04 installed, e.g. apt-get has taken 18
  minutes 41 seconds to fetch 459Kb.

  Following the advice from
  https://ubuntuforums.org/showthread.php?t=2214110, I have installed
  the firmware-b43-installer package. The card is recognised and is
  sometimes allocated an IP. When it is connected, it is very slow.

  Using the wireless-info tool the logs for the wireless system
  configuration is given below. As shown in the logs the b43-pci-bridge
  driver is outputting an error message concerning the swiotlb is full.

  Has anybody managed to get the Linksys WMP54GS v1.0 card working
  on Ubuntu Server 20.04 using the b43 firmware supplied in package 
firmware-b43-installer?

  Since the log was produced I have also tired setting the REG_DOMAIN in
  /etc/default/crda but still does not work.

  ## wireless info START ##

  Report from: 04 May 2020 09:24 UTC +

  Booted last: 04 May 2020 00:00 UTC +

  Script from: 22 Oct 2018 03:34 UTC +

  # release ###

  Distributor ID: Ubuntu
  Description: Ubuntu 20.04 LTS
  Release: 20.04
  Codename: focal

  # kernel 

  Linux 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020
  x86_64 x86_64 x86_64 GNU/Linux

  Parameters: ro, maybe-ubiquity

  # desktop ###

  sed: can't read /root/.dmrc: No such file or directory

  Could not be determined.

  # lspci #

  04:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10)
   Subsystem: Packard Bell B.V. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
[1631:e035]
   Kernel driver in use: 8139too

  04:07.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 
802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
   Subsystem: Linksys WMP54GS v1.0 802.11g Wireless-G PCI Adapter with 
SpeedBooster [1737:0015]
   Kernel driver in use: b43-pci-bridge

  # lsusb #

  Bus 001 Device 005: ID 040b:650a Weltrend Semiconductor
  Bus 001 Device 004: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link 
DUB-H4 USB 2.0 Hub
  Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 046a:010e Cherry GmbH USB Wireless Device
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  # PCMCIA card info ##

  'pccardctl' is not installed (package "pcmciautils").

  # rfkill 

  ./wireless-info: line 192: rfkill: command not found

  # secure boot ###

  'mokutil' is not installed (package "mokutil").

  # lsmod #

  b43 417792 0
  cordic 16384 1 b43
  bcma 65536 1 b43
  mac80211 843776 1 b43
  cfg80211 704512 2 b43,mac80211
  libarc4 16384 1 mac80211
  mxm_wmi 16384 1 nouveau
  wmi 32768 2 mxm_wmi,nouveau
  ssb 73728 1 b43

  # interfaces 

  # ifconfig ##

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback  brd 
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: eth_lan0:  mtu 1500 qdisc fq_codel 
state DOWN group default qlen 1000
  link/ether  brd 
  3: wlan0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
  link/ether  brd 

  # iwconfig ##

  eth_lan0 no wireless extensions.

  lo no wireless extensions.

  wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

  # route #

  # resolv.conf ###

  [777 root '/etc/resolv.conf' -> '../run/systemd/resolve/stub-
  resolv.conf']

  nameserver 127.0.0.53
  options edns0

  # network managers ##

  Installed:

   None found.

  Running:

   None found.

  # NetworkManager info ###

  NetworkManager is not insta

[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

[Kai-Heng Feng]

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

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: MACs ctos: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: MACs stoc: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-s

[Kernel-packages] [Bug 1871573] Re: [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found

[Kai-Heng Feng]

I don't find Nvidia card in lspci. Are we sure there's an Nvidia card in
the system?

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

Title:
  [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I know that you have certified version 18.04 and that 20.04 is not out yet.
  So this is more heads up.

  I am testing Ubuntu 20.04 on new Lenovo P1 2nd gen.
  Currently HDMI does not work.

  How do I know that problem is not in cable or monitor ?
  If I boot to windows, HDMI port works as expected.

  Thank you,
  Igor RACIC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 10:00:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
  InstallationDate: Installed on 2020-04-01 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: LENOVO 20QTCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1874221] Re: Fix potential null pointer dereference on kernfs

[Kai-Heng Feng]

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

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

Title:
  Fix potential null pointer dereference on kernfs

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  We are seeing a null kernel dereference on kernfs during system sleep
  stress.

  [Fix]
  Make sure kernfs root is not null.

  [Test]
  Run sleep stress. Not seeing the issue after the fix is applied.

  [Regression Potential]
  Low. Fix limits to kernfs, also the it has been in upstream kernel for
  quite a while.

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

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

[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work

[Kai-Heng Feng]

Please use hid-tools' hid-recorder on the Touchpad's hidraw node to
collect log.

[1] https://gitlab.freedesktop.org/libevdev/hid-tools

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

Title:
  [Dell Venue 11 Pro 7140] Trackpad does not work

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
  dock.  PopOS 20.04 fully updated.  I have experienced this bug on
  stock Ubuntu 20.04 as well as Kubuntu 20.04.

    When at the login page, the trackpad and keyboard operate as they
  should.  Once the login process is complete and the desktop is
  displayed, the keyboard still works as expected but the trackpad no
  longer controls the pointer.  The touch display still functions as
  expected but the trackpad on the keyboard dock doesn't work.

  The attached document is my device list, here is the evtest:

  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111
  Input device name: "Synaptics T Pad V 01.31 Touchpad"
  Supported events:
    Event type 0 (EV_SYN)
    Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 325 (BTN_TOOL_FINGER)
  Event code 330 (BTN_TOUCH)
  Event code 333 (BTN_TOOL_DOUBLETAP)
  Event code 334 (BTN_TOOL_TRIPLETAP)
    Event type 3 (EV_ABS)
  Event code 0 (ABS_X)
    Value483
    Min0
    Max 1056
    Resolution  12
  Event code 1 (ABS_Y)
    Value266
    Min0
    Max  516
    Resolution  12
  Event code 47 (ABS_MT_SLOT)
    Value  0
    Min0
    Max2
  Event code 53 (ABS_MT_POSITION_X)
    Value  0
    Min0
    Max 1056
    Resolution  12
  Event code 54 (ABS_MT_POSITION_Y)
    Value  0
    Min0
    Max  516
    Resolution  12
  Event code 55 (ABS_MT_TOOL_TYPE)
    Value  0
    Min0
    Max2
  Event code 57 (ABS_MT_TRACKING_ID)
    Value  0
    Min0
    Max65535
    Event type 4 (EV_MSC)
  Event code 5 (MSC_TIMESTAMP)
  Properties:
    Property type 0 (INPUT_PROP_POINTER)
    Property type 2 (INPUT_PROP_BUTTONPAD)
  Testing ... (interrupt to exit)

  I did try to remove xserver-xorg-input-synaptics, but it is not
  installed on 20.04.

  There is still an issue with Wayland and the trackpad, but it's different 
than Xorg so the problem may be in how Xorg is processing the trackpad (I 
honestly don't know) - in Wayland, it will work until I attempt to run the 
sofware center.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Pop!_OS 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5300 [1028:066b]
  MachineType: Dell Inc. Venue 11 Pro 7140
  Package: xorg-server (not installed)
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img 
root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 
5.4.30
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-7626-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XMVMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.product.sku: 066B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/

[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window

[Kai-Heng Feng]

Does the GA kernel (i.e. 4.15) have this issue?

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

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

Title:
  System Hangs when trying to kill a Window

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear Sirs,
  I'm a long term user of Ubuntu,
  I run a Client/Server system that my clients expect to be very stable.
  I ran under Trust Tahr for a long while with great success and no Hangups at 
all.
  I recently upgraded to Bionic Beaver and I find that I have a number of
  Hangups.
  They seem to occur mostly when switching between different users.
  The latest one that occurred last night that I want to show you here was
  caused by something else.
  I was watching a video from Youtube under Firefox.
  At the end of it I clicked the upper right hand button of the window
  to kill the screen. At this point the system froze on me.
  I could move the mouse around but none of the keys worked.
  I used the SysrRq - Magic Key combination to get the following information
  ALT + PrtScrn, ALT + CREISUB
  The system re-booted and gave me the following files in /var/crash
4096 May  9 23:38 202005092338
 349 May 10 11:01 kexec_cmd
   25387 May  9 23:39 linux-image-5.3.0-51-generic-202005092338.crash

   69696 May  9 23:38 dmesg.202005092338
   291014103 May  9 23:38 dump.202005092338

  I used the crash program with the Symbols file and in the backtrace section
 under the exception line it says:
 exception RIP mwait_idle+132
 in the disassembly of mwait_idle
  the line at +132 is
mov%gs:0x72774cb4(%rip),%r12d# 0x10350

  Any information that I can supply to you I will be glad to in order to
  aid you in solving this problem.

  I'm fairly computer literate and so I can follow any directions that
  you want to give to me.

  I have enjoyed using Ubutnu for many years but I do need a Stable
  environment for my Development work and for my users satisfaction.

  Yours truly,
  Frank Krauss

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.37
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 13:19:54 2020
  InstallationDate: Installed on 2020-04-20 (19 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fkrauss1808 F pulseaudio
   /dev/snd/controlC0:  fkrauss1808 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-20 (20 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   ens2  no wireless extensions.
   
   lono wireless extensions.
  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 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.17
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 02/08/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG31PR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD97573-306
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U

[Kai-Heng Feng]

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

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

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

Title:
  sporadic black screen freeze on lenovo e595 Ryzen 3700U

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have sporadic black screen freeze on my lenovo e595 3700U during reboot.
  The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT
  Problem occure also on 
  linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64
  and
  linux-image-unsigned-5.4.28-050428-generic_5.4.28-050428.202003250833_amd64

  19.10 was working with 5.0 kernel

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-24-generic 5.4.0-24.28
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gizzmo 1345 F pulseaudio
   /dev/snd/controlC1:  gizzmo 1345 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Apr 18 21:28:37 2020
  InstallationDate: Installed on 2020-04-18 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20NFCTO1WW
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic 
root=/dev/mapper/vgkubuntu-root ro nomodeset ip=dhcp
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-24-generic N/A
   linux-backports-modules-5.4.0-24-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET36W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E595
  dmi.product.name: 20NFCTO1WW
  dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595
  dmi.product.version: ThinkPad E595
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04

[Kai-Heng Feng]

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

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

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

Title:
  [radeon] X windows hangs following upgrade from 18.04 to 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following an upgrade from 18.04 to 20.04 when I boot, X windows comes
  to a point where I get a white background with a bunch of colored
  dots.  Nothing progresses from there.

  I can boot successfully by pressing escape after booting, going to
  advanced options, booting to 5.4.0-29 recovery mode.  When that menu
  appears, I select "root".  I press Enter for maintenance.

  When the root prompt appears I immediately type EXIT to return to the
  menu and then RESUME followed by OK.

  The system then starts the desktop properly.

  I would be happy to provide boot logs and/or Xorg.0.logs if desired.
  It appears to me that there are out of memory errors occurring along
  with some addressing issues.

  I am on an HP EliteBook 8570w laptop 15.6 G memory.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.19
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 10:22:37 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-22 (595 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-05-09 09:07:41.355959
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   None

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

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

[Kernel-packages] [Bug 1878147] Re: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED

[Kai-Heng Feng]

I wonder if the following helps...
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6343a6d4b2130be9323f347d60af8a7ba8f7242c
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=57a29df341466b5cca43ba3d2d7064426727d7c3
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fd5d781964b05ab586e690923dba6eca3cc16723

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

Title:
  Realtek 8723DE [10ec:d723] subsystem [10ec:d738]  disconnects
  unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Invalid
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [ 7.002889] wlp5s0: authenticate with a4:56:30:cc:0f:30
  [ 7.146619] wlp5s0: send auth to a4:56:30:cc:0f:30 (try 1/3)
  [ 7.258747] wlp5s0: authenticated
  [ 7.262852] wlp5s0: associate with a4:56:30:cc:0f:30 (try 1/3)
  [ 7.266190] wlp5s0: RX AssocResp from a4:56:30:cc:0f:30 (capab=0x431 status=0 
aid=4)
  [ 7.266205] rtw_pci :05:00.0: sta a4:56:30:cc:0f:30 joined with macid 0
  [ 7.266425] rtw_pci :05:00.0: failed to send h2c command
  [ 7.266437] wlp5s0: associated
  [ 7.299291] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready

  That error "failed to send h2c command" is only observed multiple
  times in current oem-osp1 kernel for multiple times during the test
  rounds, and is never found with the OOT module built from
  https://github.com/rtlwifi-linux/rtw88_8723de/tree/master-coex-trial2.
  And so is following error when reproduced against Ubuntu kernels:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1050.53
  ProcVersionSignature: Ubuntu 5.0.0-1050.55-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1050-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1667 F pulseaudio
u  3061 F pulseaudio
   /dev/snd/controlC0:  gdm1667 F pulseaudio
u  3061 F pulseaudio
  Date: Tue May 12 14:59:32 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-grenn+X39
  InstallationDate: Installed on 2020-04-10 (31 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. 
   Bus 001 Device 003: ID 0bda:d739 Realtek Semiconductor Corp. 
   Bus 001 Device 005: ID 062a:4c01 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3888
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1050-oem-osp1 
root=UUID=17e0a095-201d-4dca-a2e7-6e16dcd6a797 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1050-oem-osp1 N/A
   linux-backports-modules-5.0.0-1050-oem-osp1  N/A
   linux-firmware   1.173.18
  SourcePackage: linux-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.19.29
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.19.29:bd02/13/2020:svnDellInc.:pnVostro3888:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3888
  dmi.product.sku: 09B2
  dmi.sy

[Kernel-packages] [Bug 1878059] Re: ALC892 audio device not reachable after wake up

[Kai-Heng Feng]

Can you please test the PulseAudio in focal-proposed?

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

Title:
  ALC892 audio device not reachable after wake up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome shell
  On older Ubuntu releases (<= 19.10), all is working fine.

  After waking up from suspend mode when I play music or a video, the
  system changed playing sound at my monitor speakers, detected as „card
  2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“.

  Here is the full list:
  $ LANG=C aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0

  I can only choose the HDMI device in gnome-control-center or pavucontrol. The 
other devices are gone, why what ever.
  When I restart the pulseaudio process, all devices will come back:
  $ sudo killall -9 pulseaudio # (many times, because pa restarts itself)
  $ /usr/bin/pulseaudio --daemonize=no --log-target=journal
  ^Z
  [1]+  Angehalten  /usr/bin/pulseaudio --daemonize=no 
--log-target=journal
  $ bg 1

  This behavior is new in 20.04.

  Before I establish the behavior of pulseaudio, I logged off and on
  again and all devices are shown.

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

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

[Kernel-packages] [Bug 1877388] Re: If DVD drive is present system very often fails to start-up

[Kai-Heng Feng]

Are kernels from 18.04 are still installed? Please boot those older
kernels from grub menu.

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

Title:
  If DVD drive is present system very often fails to start-up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I power down, upon next boot the system just hangs with
  Ubuntu at the bottom of the screen and the circle above going around
  and around forever.

  It happens nearly every ime I power down, but not every single time.
  Rebooting rather that powering down works quite often.

  At first when thing hung I would just hard power off by holding down
  the power key.  Then I'd use the live usb I installed with to run
  Disks app.  More often than not the vfat W95 FAT32 partition at sda1
  was damaged. The first repair would fail. The second repair would
  succeed.  And then I'd be able to boot into my system again.

  After chatting about it a little with EriC^^ in #ubuntu on IRC I
  learned how to do Alt+Fn+PrtSc S, U, B or S, U, O.  Sometimes just
  doing either of those on the hang screen would result in it booting up
  fine next time.  Sometimes not.

  After installing 20.04 (a fresh install on a brand new Samsung 860 EVO
  1TB sdd hard drive) I copied back all the files in my home direct that
  I'd backed from 18.04, including hidden files.  This confused Firefox
  so I had to delete related folders and then unintall and reinstall to
  stop Firefox being confused.  This might have nothing whatsoever to do
  with this issue, just mentioning it just in case something else is
  similarly confused.  EriC^^ suggested I try adding another user and
  seeing if the issue went away.  On the first test (and some but not
  all subsequent tests) it did seem that TestUser could power down and
  reboot fine. But actually it didn't seem that different.

  I powered down, rebooted, used live usb to repair Disk over and over
  again for hours trying to find a pattern as to when it happened and
  when it didn't, but failed to find any fixed pattern.

  Eventually at one point it was taking a while to power down (or
  reboot, I forget) and so I hit Esc and spotted that it had failed to
  unmount /cdrom  ...

  ... so then I thought I'd try completely removing my DVD/CDRW drive
  and that made the issue go away.

  Before filing this I put the DVD drive back in (but haven't since
  rebooted), so not sure if apport has picked up it's details or not?
  Perhaps I'll need to re-file the bug after booting with it present?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 15:09:23 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-26 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
   |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: LENOVO 4384WCV
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4384WCV
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO

[Kernel-packages] [Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U

[Kai-Heng Feng]

Please file an upstream bug at
https://gitlab.freedesktop.org/drm/amd/issues

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

Title:
  sporadic black screen freeze on lenovo e595 Ryzen 3700U

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have sporadic black screen freeze on my lenovo e595 3700U during reboot.
  The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT
  Problem occure also on 
  linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64
  and
  linux-image-unsigned-5.4.28-050428-generic_5.4.28-050428.202003250833_amd64

  19.10 was working with 5.0 kernel

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-24-generic 5.4.0-24.28
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gizzmo 1345 F pulseaudio
   /dev/snd/controlC1:  gizzmo 1345 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Apr 18 21:28:37 2020
  InstallationDate: Installed on 2020-04-18 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20NFCTO1WW
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic 
root=/dev/mapper/vgkubuntu-root ro nomodeset ip=dhcp
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-24-generic N/A
   linux-backports-modules-5.4.0-24-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET36W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E595
  dmi.product.name: 20NFCTO1WW
  dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595
  dmi.product.version: ThinkPad E595
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1877388] Re: If DVD drive is present system very often fails to start-up

[Kai-Heng Feng]

Let's start from testing mainline kernel like Daniel instructed in
comment #10.

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

Title:
  If DVD drive is present system very often fails to start-up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I power down, upon next boot the system just hangs with
  Ubuntu at the bottom of the screen and the circle above going around
  and around forever.

  It happens nearly every ime I power down, but not every single time.
  Rebooting rather that powering down works quite often.

  At first when thing hung I would just hard power off by holding down
  the power key.  Then I'd use the live usb I installed with to run
  Disks app.  More often than not the vfat W95 FAT32 partition at sda1
  was damaged. The first repair would fail. The second repair would
  succeed.  And then I'd be able to boot into my system again.

  After chatting about it a little with EriC^^ in #ubuntu on IRC I
  learned how to do Alt+Fn+PrtSc S, U, B or S, U, O.  Sometimes just
  doing either of those on the hang screen would result in it booting up
  fine next time.  Sometimes not.

  After installing 20.04 (a fresh install on a brand new Samsung 860 EVO
  1TB sdd hard drive) I copied back all the files in my home direct that
  I'd backed from 18.04, including hidden files.  This confused Firefox
  so I had to delete related folders and then unintall and reinstall to
  stop Firefox being confused.  This might have nothing whatsoever to do
  with this issue, just mentioning it just in case something else is
  similarly confused.  EriC^^ suggested I try adding another user and
  seeing if the issue went away.  On the first test (and some but not
  all subsequent tests) it did seem that TestUser could power down and
  reboot fine. But actually it didn't seem that different.

  I powered down, rebooted, used live usb to repair Disk over and over
  again for hours trying to find a pattern as to when it happened and
  when it didn't, but failed to find any fixed pattern.

  Eventually at one point it was taking a while to power down (or
  reboot, I forget) and so I hit Esc and spotted that it had failed to
  unmount /cdrom  ...

  ... so then I thought I'd try completely removing my DVD/CDRW drive
  and that made the issue go away.

  Before filing this I put the DVD drive back in (but haven't since
  rebooted), so not sure if apport has picked up it's details or not?
  Perhaps I'll need to re-file the bug after booting with it present?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 15:09:23 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-26 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
   |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: LENOVO 4384WCV
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4384WCV
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4384WCV:p

[Kernel-packages] [Bug 1877388] Re: If DVD drive is present system very often fails to start-up

[Kai-Heng Feng]

Download the following deb and install them:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc5/linux-image-unsigned-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc5/linux-modules-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb

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

Title:
  If DVD drive is present system very often fails to start-up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I power down, upon next boot the system just hangs with
  Ubuntu at the bottom of the screen and the circle above going around
  and around forever.

  It happens nearly every ime I power down, but not every single time.
  Rebooting rather that powering down works quite often.

  At first when thing hung I would just hard power off by holding down
  the power key.  Then I'd use the live usb I installed with to run
  Disks app.  More often than not the vfat W95 FAT32 partition at sda1
  was damaged. The first repair would fail. The second repair would
  succeed.  And then I'd be able to boot into my system again.

  After chatting about it a little with EriC^^ in #ubuntu on IRC I
  learned how to do Alt+Fn+PrtSc S, U, B or S, U, O.  Sometimes just
  doing either of those on the hang screen would result in it booting up
  fine next time.  Sometimes not.

  After installing 20.04 (a fresh install on a brand new Samsung 860 EVO
  1TB sdd hard drive) I copied back all the files in my home direct that
  I'd backed from 18.04, including hidden files.  This confused Firefox
  so I had to delete related folders and then unintall and reinstall to
  stop Firefox being confused.  This might have nothing whatsoever to do
  with this issue, just mentioning it just in case something else is
  similarly confused.  EriC^^ suggested I try adding another user and
  seeing if the issue went away.  On the first test (and some but not
  all subsequent tests) it did seem that TestUser could power down and
  reboot fine. But actually it didn't seem that different.

  I powered down, rebooted, used live usb to repair Disk over and over
  again for hours trying to find a pattern as to when it happened and
  when it didn't, but failed to find any fixed pattern.

  Eventually at one point it was taking a while to power down (or
  reboot, I forget) and so I hit Esc and spotted that it had failed to
  unmount /cdrom  ...

  ... so then I thought I'd try completely removing my DVD/CDRW drive
  and that made the issue go away.

  Before filing this I put the DVD drive back in (but haven't since
  rebooted), so not sure if apport has picked up it's details or not?
  Perhaps I'll need to re-file the bug after booting with it present?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 15:09:23 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-26 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
   |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: LENOVO 4384WCV
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4384WCV
  dmi.board.vendor: LENOVO
  dmi.board.ver

[Kernel-packages] [Bug 1877192] Re: RTL8723bs bluetooth not working on 20.04

[Kai-Heng Feng]

Ubfan,
Can you please attach dmesg under 5.4 (working) and 5.5 (not working)?

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

Title:
  RTL8723bs bluetooth not working on 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Ubuntu 20.04 installed on atom-based tablet ACER Aspire Switch 10. And 
bluetooth does not work. In fact it looks like ubuntu does not recognize 
bluetooth HW at all. But the system does have bluetooth module which under 
windows is recognized as RTK8723 (ACPI\RTK8723\some-id)
  At the same time WiFi works without issues (the same module, if I am not 
mistaken).

  $ lsb_release -d
  Description:Ubuntu 20.04 LTS
  $ uname -vr
  5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
  $ dmesg | grep -i 8723
  [8.087918] r8723bs: module is from the staging directory, the quality is 
unknown, you have been warned.
  [8.088914] r8723bs: module verification failed: signature and/or required 
key missing - tainting kernel
  [8.092667] RTL8723BS: module init start
  [8.092671] RTL8723BS: rtl8723bs 
v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
  [8.092673] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
  [8.303955] RTL8723BS: rtw_ndev_init(wlan0)
  [8.304653] RTL8723BS: module init ret =0
  [   13.200223] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
  [   17.832536] RTL8723BS: rtw_set_802_11_connect(wlan0)  fw_state = 0x0008
  [   17.889893] RTL8723BS: start auth
  [   17.892815] RTL8723BS: auth success, start assoc
  [   17.901012] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found 
!!
  [   17.901053] RTL8723BS: assoc success
  [   17.913846] RTL8723BS: send eapol packet
  [   17.939873] RTL8723BS: send eapol packet
  [   17.942652] RTL8723BS: set pairwise key camid:4, addr:50:c7:bf:31:a1:fa, 
kid:0, type:AES
  [   17.944712] RTL8723BS: set group key camid:5, addr:50:c7:bf:31:a1:fa, 
kid:1, type:TKIP
  $ rfkill list all
  0: acer-wireless: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: acer-bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: no
  2: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1288 F pulseaudio
   /dev/snd/controlC0:  user   1288 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lspci-vt:
   -[:00]-+-00.0  Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC 
Transaction Register
  +-02.0  Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display
  +-14.0  Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron 
N2000 Series USB xHCI
  +-1a.0  Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Trusted Execution Engine
  \-1f.0  Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:2968 Synaptics, Inc. 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 3: Dev 3, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
   |__ Port 3: Dev 3, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: Acer Aspire SW5-012
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=140a1a3c-1a0a-4aab-b323-f621e6497a7e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  StagingDrivers: r8723bs
  Tags:  focal staging
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Fendi2
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrV1.20:bd03/01/

[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work

[Kai-Heng Feng]

Can you please attach reports for all hidraw*?

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

Title:
  [Dell Venue 11 Pro 7140] Trackpad does not work

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
  dock.  PopOS 20.04 fully updated.  I have experienced this bug on
  stock Ubuntu 20.04 as well as Kubuntu 20.04.

    When at the login page, the trackpad and keyboard operate as they
  should.  Once the login process is complete and the desktop is
  displayed, the keyboard still works as expected but the trackpad no
  longer controls the pointer.  The touch display still functions as
  expected but the trackpad on the keyboard dock doesn't work.

  The attached document is my device list, here is the evtest:

  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111
  Input device name: "Synaptics T Pad V 01.31 Touchpad"
  Supported events:
    Event type 0 (EV_SYN)
    Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 325 (BTN_TOOL_FINGER)
  Event code 330 (BTN_TOUCH)
  Event code 333 (BTN_TOOL_DOUBLETAP)
  Event code 334 (BTN_TOOL_TRIPLETAP)
    Event type 3 (EV_ABS)
  Event code 0 (ABS_X)
    Value483
    Min0
    Max 1056
    Resolution  12
  Event code 1 (ABS_Y)
    Value266
    Min0
    Max  516
    Resolution  12
  Event code 47 (ABS_MT_SLOT)
    Value  0
    Min0
    Max2
  Event code 53 (ABS_MT_POSITION_X)
    Value  0
    Min0
    Max 1056
    Resolution  12
  Event code 54 (ABS_MT_POSITION_Y)
    Value  0
    Min0
    Max  516
    Resolution  12
  Event code 55 (ABS_MT_TOOL_TYPE)
    Value  0
    Min0
    Max2
  Event code 57 (ABS_MT_TRACKING_ID)
    Value  0
    Min0
    Max65535
    Event type 4 (EV_MSC)
  Event code 5 (MSC_TIMESTAMP)
  Properties:
    Property type 0 (INPUT_PROP_POINTER)
    Property type 2 (INPUT_PROP_BUTTONPAD)
  Testing ... (interrupt to exit)

  I did try to remove xserver-xorg-input-synaptics, but it is not
  installed on 20.04.

  There is still an issue with Wayland and the trackpad, but it's different 
than Xorg so the problem may be in how Xorg is processing the trackpad (I 
honestly don't know) - in Wayland, it will work until I attempt to run the 
sofware center.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Pop!_OS 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5300 [1028:066b]
  MachineType: Dell Inc. Venue 11 Pro 7140
  Package: xorg-server (not installed)
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img 
root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 
5.4.30
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-7626-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XMVMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.product.sku: 066B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU

[Kai-Heng Feng]

[5.294969] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to
init link iDisp1: -517

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

Title:
  No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7
  CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New focal installation on a new Acer Swift 3 laptop with core i7-1065G7.
  No sound detected, KDE/pavucontrol shows Dummy output.
  External headset also not detected.

  I've googled around and tried to reinstall alsa and pulseaudio, tried
  alsa force-reload as well. Nothing helps.

  With snd_hda_intel.dmic_detect=0 speakers start working but microphone
  is not detected. External headset detected with both headphones and
  mic. I use this as a workaround for a time being.

  I've checked
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It
  is closed  and use  recent kernel and firmware  but it does not fix my
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May  9 18:56:15 2020
  InstallationDate: Installed on 2020-04-24 (15 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Swift SF314-57G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57G
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work

[Kai-Heng Feng]

Can you please test kernel parameter "usbcore.autosuspend=-1" and see if
it helps?

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

Title:
  [Dell Venue 11 Pro 7140] Trackpad does not work

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
  dock.  PopOS 20.04 fully updated.  I have experienced this bug on
  stock Ubuntu 20.04 as well as Kubuntu 20.04.

    When at the login page, the trackpad and keyboard operate as they
  should.  Once the login process is complete and the desktop is
  displayed, the keyboard still works as expected but the trackpad no
  longer controls the pointer.  The touch display still functions as
  expected but the trackpad on the keyboard dock doesn't work.

  The attached document is my device list, here is the evtest:

  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111
  Input device name: "Synaptics T Pad V 01.31 Touchpad"
  Supported events:
    Event type 0 (EV_SYN)
    Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 325 (BTN_TOOL_FINGER)
  Event code 330 (BTN_TOUCH)
  Event code 333 (BTN_TOOL_DOUBLETAP)
  Event code 334 (BTN_TOOL_TRIPLETAP)
    Event type 3 (EV_ABS)
  Event code 0 (ABS_X)
    Value483
    Min0
    Max 1056
    Resolution  12
  Event code 1 (ABS_Y)
    Value266
    Min0
    Max  516
    Resolution  12
  Event code 47 (ABS_MT_SLOT)
    Value  0
    Min0
    Max2
  Event code 53 (ABS_MT_POSITION_X)
    Value  0
    Min0
    Max 1056
    Resolution  12
  Event code 54 (ABS_MT_POSITION_Y)
    Value  0
    Min0
    Max  516
    Resolution  12
  Event code 55 (ABS_MT_TOOL_TYPE)
    Value  0
    Min0
    Max2
  Event code 57 (ABS_MT_TRACKING_ID)
    Value  0
    Min0
    Max65535
    Event type 4 (EV_MSC)
  Event code 5 (MSC_TIMESTAMP)
  Properties:
    Property type 0 (INPUT_PROP_POINTER)
    Property type 2 (INPUT_PROP_BUTTONPAD)
  Testing ... (interrupt to exit)

  I did try to remove xserver-xorg-input-synaptics, but it is not
  installed on 20.04.

  There is still an issue with Wayland and the trackpad, but it's different 
than Xorg so the problem may be in how Xorg is processing the trackpad (I 
honestly don't know) - in Wayland, it will work until I attempt to run the 
sofware center.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Pop!_OS 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5300 [1028:066b]
  MachineType: Dell Inc. Venue 11 Pro 7140
  Package: xorg-server (not installed)
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img 
root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 
5.4.30
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-7626-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XMVMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.product.sku: 066B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.n

[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

[Kai-Heng Feng]

Please add kernel parameter "dyndbg='file drivers/usb/* +p'
log_buf_len=16M", and attach dmesg after reproducing the 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/1877887

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  EDIT: Ignore the two more issue below, however I'm leaving them in the
  post in case they end up being relevant.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 seconds or so before staying on properly.

  As previously mentioned, these issues are fairly new and did not occur
  in older versions of ubuntu. I have confirmed that the audio interface
  works fine under windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 14:09:28 2020
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB-Audio - microKEY-37
  Symptom_PulseAudioLog:

  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp37s0   no wireless extensions.

   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:

  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.