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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  irq/126-aerdrv always eating 30-40 % of a CPU core

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion - 14-al103ne
  Ubuntu 20.04

  'top' command shows irq/126-aerdrv always running eating a lot of CPU.
  Have attached 'powertop' and 'watch -n 1 cat /proc/interrupts' screenshots. 

  Thank you. Please get back for more information

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rahul  1825 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 12:06:46 2020
  HibernationDevice: RESUME=UUID=cc93af0a-17fa-47e4-ae6c-5eb166c23eb9
  InstallationDate: Installed on 2020-05-23 (2 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=4c6e6336-c458-4c50-b8de-561e8608eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-26 (0 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8214
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8214:rvr83.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: Z9D49EA#ABV
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

[You-Sheng Yang]

focal-proposed version 5.4.0-33.37 doesn't include this fix yet.
Included in 5.4.0-34.38 instead.

bionic-proposed version 4.15.0-102.103 has.

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

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

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

Title:
  'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

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

Bug description:
  [SRU Justification]

  [Impact]
  Touchpad function unavailable on some platforms with new ELAN touchpad
  HIDs.

  [Fix]
  
https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/
  required to match these currently unsupported IDs.

  [Test Case]
  1. check if platform is affected, e.g. with ELAN0634:

 $ sudo acpidump | grep -C3 ELAN
 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF
 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._
 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2.
 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634..
 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U
 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h.
 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions

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

[Kernel-packages] [Bug 1880656] [NEW] Fix incorrect speed/duplex when I210 device is runtime suspended

[Kai-Heng Feng]

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-oem-5.6 (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: New

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

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


** Tags: oem-priority originate-from-1857680 somerville

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

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

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

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

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

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

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

** Tags added: oem-priority originate-from-1857680 somerville

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

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

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

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

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

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

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

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

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

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1880656

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53

[Kai-Heng Feng]

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

** This bug is no longer a duplicate of bug 1879997
   HP-255-G7-Notebook-PC 5.3.0-51-generic
** This bug has been marked a duplicate of bug 1879807
   5.3.0-53 Kernel system falis to reboot after install

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

Title:
  System hangs on shut down Kernel 5.3.0-53

Status in linux package in Ubuntu:
  New

Bug description:
  System does not shut down properly with this Kernel: Kernel 5.3.0-51
  seems to work OK

  This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working.
  Attached is version.log and the output of inxi
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toni   1676 F pulseaudio
   /dev/snd/controlC1:  toni   1676 F pulseaudio
   /dev/snd/controlC0:  toni   1676 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00
  InstallationDate: Installed on 2019-07-25 (301 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711
  IwConfig:
   enp8s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash 
processor.max_cstate=5 vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-53-generic N/A
   linux-backports-modules-5.3.0-53-generic  N/A
   linux-firmware1.173.18
  RfKill:
   
  Tags:  tricia
  Uname: Linux 5.3.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare 
saned scanner ssh sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  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/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M 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/1880119/+subscriptions

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

[Kernel-packages] [Bug 1880005] Re: Shutdown/Poweroff Failed with Kernel 5.0.3-53

[Kai-Heng Feng]

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

** This bug is no longer a duplicate of bug 1879997
   HP-255-G7-Notebook-PC 5.3.0-51-generic
** This bug has been marked a duplicate of bug 1879807
   5.3.0-53 Kernel system falis to reboot after install

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

Title:
  Shutdown/Poweroff Failed with Kernel 5.0.3-53

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Linux Mint Mate 19.3 (Tricia, 64-bits).

  When I upgraded the Kernel to version 5.3.0-53, the on / off function
  failed, the screen is off but the laptop is still working, the light
  of manual shutdown button is still lit.

  There is no problem with the previous version of the kernel: 5.3.0-51.

  My laptop is Lenovo YOGA 530-14ARR with precessor AMD Ryzen 5 2500U
  with Radeon Vega Mobile Gfx × 8

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

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

[Kernel-packages] [Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install

[Kai-Heng Feng]

Ubuntu-5.3.0-54.48 will fix it:
commit adfa5c21954fc496c64b5c492bd95d9e18c0d33f
Author: Prike Liang 
Date: Mon Apr 13 21:41:14 2020 +0800

drm/amdgpu: fix the hw hang during perform system reboot and reset

BugLink: https://bugs.launchpad.net/bugs/1876321

commit b2a7e9735ab2864330be9d00d7f38c961c28de5d upstream.

The system reboot failed as some IP blocks enter power gate before perform
hw resource destory. Meanwhile use unify interface to set device CGPG to 
ungate
state can simplify the amdgpu poweroff or reset ungate guard.

Fixes: 487eca11a321ef ("drm/amdgpu: fix gfx hang during suspend with video 
playback (v2)")
Signed-off-by: Prike Liang 
Tested-by: Mengbing Wang 
Tested-by: Paul Menzel 
Acked-by: Alex Deucher 
Signed-off-by: Alex Deucher 
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Kamal Mostafa 
Signed-off-by: Kleber Sacilotto de Souza 

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

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

Status in linux package in Ubuntu:
  Confirmed

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

[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[RickyUnix]

Dell XPS 15 7590 - 5.3.0-53-generic #47~18.04.1-Ubuntu

I can say that the problem is solved now

it no longer has hangs and the CPU has returned to work without overloads.
The fans work normally and the PC is no longer overheated

Thank you

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Released

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
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 dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT

[Kernel-packages] [Bug 1879997] Re: HP-255-G7-Notebook-PC 5.3.0-51-generic

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1879807
   5.3.0-53 Kernel system falis to reboot after install

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

Title:
  HP-255-G7-Notebook-PC 5.3.0-51-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HP-255-G7-Notebook-PC System wont reboot or shutdown after kernel
  5.3.0-53 update

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

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

[Kernel-packages] [Bug 1880660] [NEW] security: lockdown: remove trailing semicolon before function body

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

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

[Test case]

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

[Fix]

Fix by removing the trailing semicolon.

[Regression potential]

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

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

-- 
security: lockdown: remove trailing semicolon before function body
https://bugs.launchpad.net/bugs/1880660
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1880660] [NEW] security: lockdown: remove trailing semicolon before function body

[Andrea Righi]

Public bug reported:

[Impact]

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

[Test case]

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

[Fix]

Fix by removing the trailing semicolon.

[Regression potential]

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Andrea Righi (arighi)
 Status: Confirmed

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Andrea Righi (arighi)
 Status: Confirmed

** Package changed: linux-oem-5.6 (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

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

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

Bug description:
  [Impact]

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

  [Test case]

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

  [Fix]

  Fix by removing the trailing semicolon.

  [Regression potential]

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

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

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

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

[Ike Panhc]

Here are kernel debs: https://kernel.ubuntu.com/~ikepanhc/lp1867591.2/
and the kernel branch: 
https://kernel.ubuntu.com/git/ikepanhc/public.git/log/?h=lp1867591.2

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

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

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

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

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

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

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

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

[Kernel-packages] [Bug 1880653] Re: irq/126-aerdrv always eating 30-40 % of a CPU core

[Kai-Heng Feng]

Can you please attach `sudo lspci -vvv`? 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/1880653

Title:
  irq/126-aerdrv always eating 30-40 % of a CPU core

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HP Pavilion - 14-al103ne
  Ubuntu 20.04

  'top' command shows irq/126-aerdrv always running eating a lot of CPU.
  Have attached 'powertop' and 'watch -n 1 cat /proc/interrupts' screenshots. 

  Thank you. Please get back for more information

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rahul  1825 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 12:06:46 2020
  HibernationDevice: RESUME=UUID=cc93af0a-17fa-47e4-ae6c-5eb166c23eb9
  InstallationDate: Installed on 2020-05-23 (2 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=4c6e6336-c458-4c50-b8de-561e8608eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-26 (0 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8214
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8214:rvr83.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: Z9D49EA#ABV
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1876707] Re: NULL pointer dereference in nvme reset work-queue when VMD raid mode and SecureBoot turned on simultaneously on TigerLake

[You-Sheng Yang]

Pushed proposed build to ppa and verified both (unstable, oem-5.6) with
SecureBoot ON+DeployMode.

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

Title:
  NULL pointer dereference in nvme reset work-queue when VMD raid mode
  and SecureBoot turned on simultaneously on TigerLake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  This is found on a Dell TigerLake platform that when VMD raid mode is
  turned on along with SecureBoot, either deploy mode or audit mode,
  kernel dumps warnings and null pointer deref errors at boot. While it
  happens, it blocks systemd-udevd worker processes until killed due to
  timeout. System still boots to multi-users.target.

  Kernel bisect shows commit e3560ee4cfb2 ("iommu/vt-d: Remove VMD child
  device sanity check") merged in v5.6-rc1 is the first commit to fail,
  and is still reproducible on v5.7-rc3.

  kernel: Secure boot disabled
  ...
  kernel: [ cut here ]
  kernel: WARNING: CPU: 1 PID: 8 at drivers/iommu/intel-iommu.c:625 
domain_get_iommu+0x4b/0x60
  kernel: Modules linked in: rc_core r8169(+) intel_lpss nvme crc32_pclmul(+) 
psmouse intel_ish_ipc(+) i2c_hid i2c_i801(+) realtek idma64 drm virt_dma 
intel_ishtp vmd(+) nvme_core hid video wmi pinctrl_tigerlake pinctrl_intel
  kernel: CPU: 1 PID: 8 Comm: kworker/u8:0 Not tainted 5.7.0-050700rc3-generic 
#202004262131
  kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
  kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
  kernel: RIP: 0010:domain_get_iommu+0x4b/0x60
  kernel: Code: eb 22 48 8d 50 01 48 39 c8 74 1b 48 89 d0 8b 74 87 04 48 63 d0 
85 f6 74 e9 48 8b 05 ef 63 63 01 48 8b 04 d0 5d c3 31 c0 5d c3 <0f> 0b 31 c0 5d 
c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f
  kernel: RSP: 0018:b5f5c00fbcf8 EFLAGS: 00010202
  kernel: RAX: 9ebdaf100b00 RBX:  RCX: 
  kernel: RDX: 1000 RSI: 00036dd41000 RDI: 9ebdaf100b00
  kernel: RBP: b5f5c00fbcf8 R08:  R09: 9ebdadd41000
  kernel: R10: 8d069060 R11: 4879 R12: 9ebdadd810b0
  kernel: R13: 00036dd41000 R14:  R15: 9ebdaf100b00
  kernel: FS:  () GS:9ebdc168() 
knlGS:
  kernel: CS:  0010 DS:  ES:  CR0: 80050033
  kernel: CR2: 7f900d20e660 CR3: 00036e05a003 CR4: 00760ee0
  kernel: PKRU: 5554
  kernel: Call Trace:
  kernel:  __intel_map_single+0x47/0x1a0
  kernel:  intel_alloc_coherent+0xab/0x120
  kernel:  dma_alloc_attrs+0x4d/0x60
  kernel:  nvme_alloc_queue+0x63/0x180 [nvme]
  kernel:  nvme_reset_work+0x31a/0xa64 [nvme]
  kernel:  ? wake_up_process+0x15/0x20
  kernel:  ? swake_up_locked.part.0+0x17/0x30
  kernel:  process_one_work+0x1e8/0x3b0
  kernel:  worker_thread+0x4d/0x400
  kernel:  kthread+0x104/0x140
  kernel:  ? process_one_work+0x3b0/0x3b0
  kernel:  ? kthread_park+0x90/0x90
  kernel:  ret_from_fork+0x1f/0x40
  kernel: ---[ end trace caf06459a58aa8d4 ]---
  
  kernel: BUG: kernel NULL pointer dereference, address: 0018
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0 
  kernel: Oops:  [#2] SMP NOPTI
  kernel: CPU: 1 PID: 254 Comm: kworker/u8:4 Tainted: G  D W 
5.7.0-050700rc3-generic #202004262131
  kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
  kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
  kernel: RIP: 0010:__intel_map_single+0xa3/0x1a0
  kernel: Code: 89 d2 4c 89 55 d0 e8 ec b3 ff ff 4c 8b 55 d0 48 85 c0 49 89 c6 
0f 84 e9 00 00 00 41 b9 01 00 00 00 83 fb 01 76 14 48 8b 45 c0 <4c> 8b 48 18 49 
c1 e9 16 49 83 f1 01 41 83 e1 01 44 89 c8 4c 89 e9
  kernel: RSP: 0018:b5f5c050f878 EFLAGS: 00010202
  kernel: RAX:  RBX: 0002 RCX: 9ebdbf205140
  kernel: RDX: 9ebdbf205bc0 RSI: 0257 RDI: 9ebdaf100e30
  kernel: RBP: b5f5c050f8c0 R08: 9ebdae266f00 R09: 0001
  kernel: R10: 0001 R11: 0022 R12: 9ebdadd860b0
  kernel: R13: 00036ef0d000 R14: 000a R15: 9ebdaf100b00
  kernel: FS:  () GS:9ebdc168() 
knlGS:
  kernel: CS:  0010 DS:  ES:  CR0: 80050033
  kernel: CR2: 0018 CR3: 00036efd2001 CR4: 00760ee0
  kernel: PKRU: 5554
  kernel: Call Trace:
  kernel:  intel_map_page+0x86/0xa0
  kernel:  nvme_map_data+0x486/0x990 [nvme]
  ker

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

[il_santo]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1879559/+attachment/5376820/+files/CRDA.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] Re: net/bpfilter: remove superfluous testing message

[il_santo]

Same problem for me. Sending logs via apport-collect.

** Tags added: apport-collected bionic

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] AlsaInfo.txt

[il_santo]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376819/+files/AlsaInfo.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] apport information

[il_santo]

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ivanhoe6650 F pulseaudio
 /dev/snd/controlC0:  ivanhoe6650 F pulseaudio
CurrentDesktop: communitheme:ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-19 (767 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 80XS
Package: linux-hwe-5.0
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=65eb0627-07fc-4f15-848b-360615a73359 ro quiet splash 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-53-generic N/A
 linux-backports-modules-5.3.0-53-generic  N/A
 linux-firmware1.173.18
Tags:  bionic
Uname: Linux 5.3.0-53-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-05-04 (752 days ago)
UserGroups: adm cdrom dip docker input kvm libvirt lpadmin plugdev sambashare 
sudo video
_MarkForUpload: True
dmi.bios.date: 11/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 5QCN23WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15ABR
dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN23WW:bd11/06/2018:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
dmi.product.family: ideapad 320-15ABR
dmi.product.name: 80XS
dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR
dmi.product.version: Lenovo ideapad 320-15ABR
dmi.sys.vendor: LENOVO

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] ProcEnviron.txt

[il_santo]

apport information

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

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

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

[bugproxy]

--- Comment From niklas.schne...@ibm.com 2020-05-26 04:04 EDT---
(In reply to comment #12)
> Hi Niklas, please can you have a look at the SRU Justification that I've now
> added to the bug description, with special focus on Test Case and Regression
> Potential.
> Please let me know if is inaccurate or missing or in case additional
> information should be added (this is mandatory information needed for the
> SRU).
> Thx

Sounds good, maybe to add that this can be triggered with shipping user
space tools (including in the Ubuntu repos) e.g.:

1. install the rdma tools:
sudo apt-get install ibverbs-providers ibverbs-utils

2. verify you have some RDMA devices (requires ConnectX adapter)
pcidev@T224LP06:~$ ibv_devices
device node GUID
--  
mlx5_0  98039b0300c682b4

3. verify MIO instructions are enabled for the device
pcidev@T224LP06:~$ cat /sys/bus/pci/devices/\:00\:00.0/mio_enabled
1

4. try to run an RDMA application from user space, e.g. ibv_rc_pingpong

server process:
ibv_rc_pingpong -d mlx5_0 -g 0 &

client process:
ibv_rc_pingpong -d mlx5_0 -g 0 localhost

5. verify that the kernel crashes

[92406.190525] Unable to handle kernel pointer dereference in virtual kernel add
ress space
[92406.190529] Failing address: ed09 TEID: ed090403
[92406.190529] Fault in home space mode while using kernel ASCE.
[92406.190531] AS:000c1c98c007 R3:000ff3bd0007 S:000ff3bd6000 P:
0009013d

Also this patch made it into v5.7-rc7 and Linus himself commented:

"And none of the fixes look like there's anything particularly scary
going on. Most of it is very small, and the slightly larger patches
aren't huge either and are well-contained (the two slightly larger
patches are to s390 and rxrpc - and even those patches aren't really
all _that_ big)"

(this patch obviously being the bigger s390 change)

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

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

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

Bug description:
  SRU Justification:
  ==

  [Impact]

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

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

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

  [Fix]

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

  [Test Case]

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

  * A little user space program can be written to provoke this error
  situation using the RoCE adapter.

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

  [Regression Potential]

  * There is some regression potential with having code changes in the
  zPCI sub-system.

  * However, the zPCI system is s390x only and the patch was accepted
  upstream (next-20200515).

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

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

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

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

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

[Kernel-packages] [Bug 1879559] PulseList.txt

[il_santo]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376830/+files/PulseList.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] ProcCpuinfo.txt

[il_santo]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376825/+files/ProcCpuinfo.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] ProcInterrupts.txt

[il_santo]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376828/+files/ProcInterrupts.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] Lspci.txt

[il_santo]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1879559/+attachment/5376823/+files/Lspci.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] CurrentDmesg.txt

[il_santo]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376821/+files/CurrentDmesg.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

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

[il_santo]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376826/+files/ProcCpuinfoMinimal.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] RfKill.txt

[il_santo]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1879559/+attachment/5376831/+files/RfKill.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] Lsusb.txt

[il_santo]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1879559/+attachment/5376824/+files/Lsusb.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] UdevDb.txt

[il_santo]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1879559/+attachment/5376832/+files/UdevDb.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] WifiSyslog.txt

[il_santo]

apport information

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

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1879559] IwConfig.txt

[il_santo]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376822/+files/IwConfig.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

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

[il_santo]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1879559/+attachment/5376829/+files/ProcModules.txt

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

Title:
   net/bpfilter: remove superfluous testing message

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
  usage for /dev/kmsg") but should've been deleted before patch submission.
  Although it doesn't cause any harm to the code or functionality itself, it's
  totally unpleasant to have it displayed on every loop iteration with no real
  use case. Thus remove it unconditionally.

  Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699

  [Test Case]

  Just check dmesg:

  [   10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
  [   15.306015] bpfilter: Loaded bpfilter_umh pid 1036
  [   15.306280] Started bpfilter
  [   15.306283] testing the buffer
  [   15.306458] testing the buffer
  [   15.306880] testing the buffer
  [   15.318003] testing the buffer
  [   15.318057] testing the buffer
  [   15.318814] testing the buffer
  [   15.442147] testing the buffer
  [   15.479556] testing the buffer
  [   15.479572] testing the buffer

  [Regression Potential]

  Very low. The fix is a one line upstream patch that removes one
  printf.

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

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

[Kernel-packages] [Bug 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available

[Frank Heimes]

Hi Niklas, thanks - I'll adjust the justification slightly and will
reference your comment - especially regarding the test and the now
upstream acceptance.

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

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

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

Bug description:
  SRU Justification:
  ==

  [Impact]

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

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

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

  [Fix]

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

  [Test Case]

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

  * A little user space program can be written to provoke this error
  situation using the RoCE adapter.

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

  [Regression Potential]

  * There is some regression potential with having code changes in the
  zPCI sub-system.

  * However, the zPCI system is s390x only and the patch was accepted
  upstream (next-20200515).

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

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

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

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

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

[Kernel-packages] [Bug 1853219] Re: [CML-H] Add intel_thermal_pch driver support Comet Lake -H

[quanxian]

** Tags removed: intel-kernel-20.10
** Tags added: intel-kernel-20.04

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

Title:
  [CML-H] Add intel_thermal_pch driver support Comet Lake -H

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

Bug description:
  [SRU Justification]

  [Impact]
  Missing thermal_zone info for Intel PCH on Comet Lake (CML) platform.

  [Fix]
  Commit 35709c4ee772 ("thermal: intel: intel_pch_thermal: Add Comet Lake
  (CML) platform support") from v5.6-rc1 to be backported.

  [Test Case]
  Check if sysfs thermal zone entry of type "pch_cometlake" exists:

    $ cat /sys/class/thermal/thermal_zone*/type | grep pch_cometlake

  [Regression Potential]
  Low. This affects only CML platforms.

  == original description ==

  Description
  Add intel_thermal_pch driver support Comet Lake -H

  Target Release: 20.10
  Target Kernel: 5.6

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

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

[Kernel-packages] [Bug 1880656] Re: Fix incorrect speed/duplex when I210 device is runtime suspended

[Stefan Bader]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[bugproxy]

--- Comment From niklas.schne...@ibm.com 2020-05-26 04:21 EDT---
I've only seen this happen with manually using the installkernel script with 
the commands included in my first comment. I will have to try if it also occurs 
with "make install" in a kernel tree. I currently have a small vacation, just 
keeping the critical bugs progressing, but will try once I'm working again.
As for different setups, I've seen this on two separate installations one on 
LPAR and one in z/VM,

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

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux-base package in Ubuntu:
  New

Bug description:
  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  # ls -l /boot
  total 178364
  -rw--- 1 root root135168 May  6 11:52 bootmap
  -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img -> 
initrd.img-5.4.0-29-generic   <== should point to new version
  -rw-r--r-- 1 root root  19663996 May  6 11:42 initrd.img-5.4.0-29-generic
  -rw-r--r-- 1 root root 125339494 May  6 11:52 
initrd.img-5.7.0-rc4-06500-gb67ea026badd
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img.old -> 
initrd.img-5.4.0-29-generic
  -rw--- 1 root root   3087920 Apr 29 15:34 System.map-5.4.0-29-generic
  -rw-r--r-- 1 root root   4031691 May  6 11:52 
System.map-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   4031691 May  6 11:49 
System.map-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root37 May  6 11:52 vmlinuz -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw--- 1 root root   8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic
  -rw-r--r-- 1 root root   9080832 May  6 11:52 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   9080832 May  6 11:49 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root41 May  6 11:52 vmlinuz.old -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old

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

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

[Kernel-packages] [Bug 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available

[Frank Heimes]

** Description changed:

  SRU Justification:
  ==
  
  [Impact]
  
  * Code that is using s390_pci_mmio_write/read system calls on a z15
  (that comes with enhanced PCI load/store instructions), fails with
  "Unable to handle kernel pointer dereference in virtual kernel address
  space".
  
  * This issue happens if enablement for z15 PCI enhancements is in place
  and where customers run workloads which access PCI adapters from user
  space, like RoCE/RDMA.
  
  * To solve this, the system call implementation needs to be improved to 
execute the enhanced PCI load/store instructions on behalf of the user space 
application,
    making use of the mappings into its virtual address space.
  
  [Fix]
  
  * f058599e22d59e594e5aae1dc10560568d8f4a8b f058599e22d5 "s390/pci: Fix
  s390_mmio_read/write with MIO"
  
  [Test Case]
  
  * Setting up a z15 with at least one PCI card (like RoCE) using an
  operating system that includes support and enablement for z15 (line
  20.04).
  
- * A little user space program can be written to provoke this error
- situation using the RoCE adapter.
+ * Install the rdma tools: sudo apt install ibverbs-providers ibverbs-
+ utils
+ 
+ * Verify you have some RDMA devices (requires ConnectX adapter)
+   $ ibv_devices
+   device node GUID
+   -- 
+   mlx5_0 98039b0300c682b4
+ 
+ * Verify MIO instructions are enabled for the device
+   $ cat /sys/bus/pci/devices/\:00\:00.0/mio_enabled
+   1
+ 
+ * Try to run an RDMA application from user space, e.g. ibv_rc_pingpong
+   server side:
+   ibv_rc_pingpong -d mlx5_0 -g 0 &
+   client side:
+   ibv_rc_pingpong -d mlx5_0 -g 0 localhost
+ 
+ * Verify whether the kernel crashes or not.
  
  * Verification needs to be done by IBM on z15 hardware.
  
  [Regression Potential]
  
  * There is some regression potential with having code changes in the
  zPCI sub-system.
  
- * However, the zPCI system is s390x only and the patch was accepted
- upstream (next-20200515).
+ * It could be that PCI hardware get harmed, but PCI hardware is not as
+ wide-spread on s390x than ccw hardware components.
  
- * Nevertheless, it could be that PCI hardware get harmed, but PCI
- hardware is not as wide-spread on s390x than ccw hardware components.
+ * Only z15 hardware is affected - no other s390x hardware that is
+ supported by Ubuntu.
  
- * Only z15 hardware is affected - no other s390x hardware thatis supported by 
Ubuntu.
+ * However, the zPCI system is s390x only and the patch was accepted upstream 
with v5.7-rc7 and Linus commented: "And none of the fixes look like there's 
anything particularly scary going on. Most of it is very small, and the 
slightly larger patches aren't huge either and are well-contained (the two 
slightly larger patches are to s390 and rxrpc - and even those patches aren't 
really all _that_ big)"
  __
  
  One of the PCI enhancements on Z15 are the enhanced PCI load/store
  instructions which can be executed directly from user space code. When
  these instructions are available and preexisting user space code still
  uses the old s390_pci_mmio_write/read system calls, the system calls
  fail with an "Unable to handle kernel pointer dereference in virtual
  kernel address space" in the kernel.  This issue affects distributions
  which have the enablement for Z15 PCI enhancements and where customers
  run workloads which accesses PCI adapters from user space, e.g. RDMA
  applications.  To solve this, the system call implementation needs to be
  enhanced to provide to execute enhanced PCI load/store instructions on
  behalf of the user space application making use of the mappings into its
  virtual address space

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

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

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

Bug description:
  SRU Justification:
  ==

  [Impact]

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

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

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

  [Fix]

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

  [Test Case]

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

[Kernel-packages] [Bug 1880666] [NEW] Power management: does not suspend

[Jarno Suni]

Public bug reported:

I am using Xubuntu 20.04.
xfce4-session-logout --suspend
exits with 0, but does not suspend. Same thing, if I choose suspend from menu 
(but it may lock screen depending on settings).

Reproduceable: at least sometimes; used to work at least sometimes with
this release.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jarnos 1125 F pulseaudio
 /dev/snd/controlC1:  jarnos 1125 F pulseaudio
 /dev/snd/controlC0:  jarnos 1125 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue May 26 11:33:29 2020
InstallationDate: Installed on 2020-05-03 (22 days ago)
InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Dell Inc. OptiPlex 745
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.6
dmi.board.name: 0RF703
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 745
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  Power management: does not suspend

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Xubuntu 20.04.
  xfce4-session-logout --suspend
  exits with 0, but does not suspend. Same thing, if I choose suspend from menu 
(but it may lock screen depending on settings).

  Reproduceable: at least sometimes; used to work at least sometimes
  with this release.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jarnos 1125 F pulseaudio
   /dev/snd/controlC1:  jarnos 1125 F pulseaudio
   /dev/snd/controlC0:  jarnos 1125 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue May 26 11:33:29 2020
  InstallationDate: Installed on 2020-05-03 (22 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1880663] [NEW] Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up

[AceLan Kao]

Public bug reported:

With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub.
There is no any log in journal when it fails to boot up, and earlyprintk shows 
nothing on the screen, either.

System Information
Manufacturer: Dell Inc.
Product Name: Latitude 7300
Version: Not Specified
Serial Number: J83ZST2
UUID: 4C4C4544-0038-3310-805A-CAC04F535432
Wake-up Type: Power Switch
SKU Number: 08E0
Family: Latitude

BIOS Information
Vendor: Dell Inc.
Version: 1.6.1
Release Date: 11/14/2019
Address: 0xF
Runtime Size: 64 kB
ROM Size: 24 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.6

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

** Affects: linux-oem (Ubuntu Bionic)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

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

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

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

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-oem (Ubuntu Bionic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
  Dell Latitude 7300 sometimes stuck at purple screen after grub and
  fails to boot up

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub.
  There is no any log in journal when it fails to boot up, and earlyprintk 
shows nothing on the screen, either.

  System Information
  Manufacturer: Dell Inc.
  Product Name: Latitude 7300
  Version: Not Specified
  Serial Number: J83ZST2
  UUID: 4C4C4544-0038-3310-805A-CAC04F535432
  Wake-up Type: Power Switch
  SKU Number: 08E0
  Family: Latitude

  BIOS Information
  Vendor: Dell Inc.
  Version: 1.6.1
  Release Date: 11/14/2019
  Address: 0xF
  Runtime Size: 64 kB
  ROM Size: 24 MB
  Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
  BIOS Revision: 1.6

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

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

Re: [Kernel-packages] [Bug 1879680] Re: Touchpad not detected on Wortmann 1460p

[Robert]

Hi, which information do you need?

Am Dienstag, den 26.05.2020, 06:29 + schrieb You-Sheng Yang:
> Hi, actually we cannot find any hint for your touchpad hardware from
> the
> logs. Do you have Windows installed on the same machine that touchpad
> is
> working? We may need some info from that.
>

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

Title:
  Touchpad not detected on Wortmann 1460p

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Touchpad is not detected on any Ubuntu Live or installed Version
  from 16.04 to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gabi   1399 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 12:52:57 2020
  InstallationDate: Installed on 2020-05-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. HD Webcam
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Wortmann_AG 1220615;1470142
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=/dev/mapper/vgubuntu-root ro i8042.reset quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 52.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: A35
  dmi.board.vendor: EA
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: EA
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr52.10:bd06/01/2018:svnWortmann_AG:pn1220615;1470142:pvr1460P;1470142:rvnEA:rnA35:rvrType2-BoardVersion:cvnEA:ct10:cvrChassisVersion:
  dmi.product.family: NB-TERRA;MOBILE-B;14
  dmi.product.name: 1220615;1470142
  dmi.product.sku: 4039407048694
  dmi.product.version: 1460P;1470142
  dmi.sys.vendor: Wortmann_AG

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Power management: does not suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Xubuntu 20.04.
  xfce4-session-logout --suspend
  exits with 0, but does not suspend. Same thing, if I choose suspend from menu 
(but it may lock screen depending on settings).

  Reproduceable: at least sometimes; used to work at least sometimes
  with this release.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jarnos 1125 F pulseaudio
   /dev/snd/controlC1:  jarnos 1125 F pulseaudio
   /dev/snd/controlC0:  jarnos 1125 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue May 26 11:33:29 2020
  InstallationDate: Installed on 2020-05-03 (22 days ago)
  InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up

[AceLan Kao]

Reproduce this issue on 4.15.0-1079-oem kernel and also on 4.15.0-101
Ubuntu kernel.

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

Title:
  Dell Latitude 7300 sometimes stuck at purple screen after grub and
  fails to boot up

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub.
  There is no any log in journal when it fails to boot up, and earlyprintk 
shows nothing on the screen, either.

  System Information
  Manufacturer: Dell Inc.
  Product Name: Latitude 7300
  Version: Not Specified
  Serial Number: J83ZST2
  UUID: 4C4C4544-0038-3310-805A-CAC04F535432
  Wake-up Type: Power Switch
  SKU Number: 08E0
  Family: Latitude

  BIOS Information
  Vendor: Dell Inc.
  Version: 1.6.1
  Release Date: 11/14/2019
  Address: 0xF
  Runtime Size: 64 kB
  ROM Size: 24 MB
  Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
  BIOS Revision: 1.6

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

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

[Kernel-packages] [Bug 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install

[Kleber Sacilotto de Souza]

Please note that Ubuntu-5.3.0-54.48 is not available in -proposed
anymore, the current version is 5.3.0-55.49 which does *not* contain the
fix mentioned on comment #8. This fix will be released to -proposed soon
with version 5.3.0-56.50.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0

[Viacheslav Semykrasov]

Dell Latitude 5500
Ubuntu 19.10, 5.3.0-53-generic - no freezing so far
Ubuntu 20.04, 5.4.0-31-generic - works perfectly too

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

Title:
  5.3.0-46-generic - i915 - frequent GPU hangs  / resets rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Released

Bug description:
  Hi,

  Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent
  (every couple of minutes) GPU hangs and reset manifesting as 2-3
  seconds freezes of the GUI (other than the mouse pointer).

  No particular triggers identified although have Chrome / Chromium
  running with Hardware Acceleration enabled does appear to increase the
  frequency.

  I have seen incidences of these hangs in jounralctl output using
  previous kernels in the 5.3.0-xx series but they were very infrequent
  (one or twice in a week of daily usage)

  System Info
  steve@steve-Inspiron-5580:~$ inxi -SCGxxxz
  System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 
compiler: gcc v: 7.5.0
     Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
Distro: Linux Mint 19.3 Tricia
     base: Ubuntu 18.04 bionic
  CPU:   Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT 
MCP arch: Kaby Lake rev: B
     L2 cache: 6144 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 28800
     Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 5: 800 6: 800 7: 800
     8: 800
  Graphics:  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:3ea0
     Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz
     OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 
GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0
     direct render: Yes

  steve@steve-Inspiron-5580:~$ journalctl -b | grep i915
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
deactivate vga console
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_04.bin (v1.4)
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 
20190619 for :00:02.0 on minor 0
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary 
device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb 
frame buffer device
  Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: 
ecode 9:0:0x, hang on rcs0
  Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0
  Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 
for hang on rcs0

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
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 dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.m

[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up

[AceLan Kao]

Reproduce this issue on 4.15.0-20-generic kernel.

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

Title:
  Dell Latitude 7300 sometimes stuck at purple screen after grub and
  fails to boot up

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub.
  There is no any log in journal when it fails to boot up, and earlyprintk 
shows nothing on the screen, either.

  System Information
  Manufacturer: Dell Inc.
  Product Name: Latitude 7300
  Version: Not Specified
  Serial Number: J83ZST2
  UUID: 4C4C4544-0038-3310-805A-CAC04F535432
  Wake-up Type: Power Switch
  SKU Number: 08E0
  Family: Latitude

  BIOS Information
  Vendor: Dell Inc.
  Version: 1.6.1
  Release Date: 11/14/2019
  Address: 0xF
  Runtime Size: 64 kB
  ROM Size: 24 MB
  Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
  BIOS Revision: 1.6

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

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

[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up

[AceLan Kao]

It's a grub issue.
After downgraded grub(2.02-2ubuntu8.15 -> 2.02-2ubuntu8) and 
shim(15+1533136590.3beb971-0ubuntu1 -> 13-0ubuntu2), can't reproduce this issue
   4.15.0-1081-oem (0/10)

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

Title:
  Dell Latitude 7300 sometimes stuck at purple screen after grub and
  fails to boot up

Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub.
  There is no any log in journal when it fails to boot up, and earlyprintk 
shows nothing on the screen, either.

  System Information
  Manufacturer: Dell Inc.
  Product Name: Latitude 7300
  Version: Not Specified
  Serial Number: J83ZST2
  UUID: 4C4C4544-0038-3310-805A-CAC04F535432
  Wake-up Type: Power Switch
  SKU Number: 08E0
  Family: Latitude

  BIOS Information
  Vendor: Dell Inc.
  Version: 1.6.1
  Release Date: 11/14/2019
  Address: 0xF
  Runtime Size: 64 kB
  ROM Size: 24 MB
  Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
  BIOS Revision: 1.6

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

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

[Kernel-packages] [Bug 1818407] Re: Cant access emmc, error -84

[Jam251]

Hi. I have a ASUS Tp202NA convertible and setting the emmc speed to
HS200 just made the internal disk discoverable. I'm going to install
kubuntu 19.10 on it to see if it works and report here. Thank you all
for your help!

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

Title:
  Cant access emmc, error -84

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings!

  I just got my new convertible(Asus TP202NAS, brand new) and wanted to install 
kubuntu 18.10 onto the internal storage, only to find that it cant see it. In 
dmesg i only got these two error:
  mc0: mmc_select_hs400 failed, error -84
  mc0: error -84 whilst initializing mmc card

  Tried to google around for a solution but i didnt found any solution
  to this, also tried the kubuntu IRC channel but didnt got any luck
  there too

  
  /EDIT
  Submitted from a live session.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-release-upgrader-core 1:18.10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  CrashDB: ubuntu
  Date: Sun Mar  3 13:59:13 2019
  LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kubuntu3661 F pulseaudio
  CasperVersion: 1.394
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:3501 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP202NAS
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP202NAS.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP202NAS
  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.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: TP202NAS
  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/1818407/+subscriptions

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

[Kernel-packages] [Bug 1879612] Re: Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade

[Raghavendra Bankapur]

Attaching full journal.log after a machine restart

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879612/+attachment/5376881/+files/journal.log

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

Title:
  Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection
  more often after the upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my ubuntu to 20.04 LTS. After the upgrade I keep seeing the wifi 
issues. More often it keeps getting disconnected and I will have to go on 
Airplane mode to re enable the connectivity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghavendra   2046 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-02 (230 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c6751bdb-dd90-489c-9932-b52487fb6eea ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd06/03/2014:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07921020561610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: B3H81PA#ACJ
  dmi.product.version: 07921020561610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1876844] Re: Speed up the process of s3 resume

[koba]

** Description changed:

  [Impact]
  Process of s3 resume take 7s and it's too long which is over 5s.
  
  [Fix]
- the commit is from 
https://lore.kernel.org/linux-pci/20200416083245.73957-1-mika.westerb...@linux.intel.com/
- 
  Reference link_active_reporting field of PCI device to determine whether 
delay is taken or not.
  Actual delay would be determined by taking maximum between 100ms and pci 
device's d3cold delay.
+ Instead of using the supported speeds to determine whether to wait for Link 
training, check whether the port supports DLL Link Active reporting.  The ports 
in question do not, so we'll wait only the 100 ms required for Ports that 
support Link speeds <= 5 GT/s.
+ 
+ This of course assumes these Ports always train the Link within 100 ms
+ even if they are operating at > 5 GT/s, which is not required by the
+ spec.
  
  [test]
  With the patch, the total time s3 resume is 3874.298 ms which is smaller than 
5s.
  
  [Regression Potential]
- Medium. This patch only changes the rules to determine whether delay is taken 
or not.
- Reference the right field(link_active_reporting), but not speed of pci device.
+ Low. Follow the PCI spec to check whether the device supports DLL Link Active 
reporting, then choose the time of delay.

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

Title:
  Speed up the process of s3 resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  Process of s3 resume take 7s and it's too long which is over 5s.

  [Fix]
  Reference link_active_reporting field of PCI device to determine whether 
delay is taken or not.
  Actual delay would be determined by taking maximum between 100ms and pci 
device's d3cold delay.
  Instead of using the supported speeds to determine whether to wait for Link 
training, check whether the port supports DLL Link Active reporting.  The ports 
in question do not, so we'll wait only the 100 ms required for Ports that 
support Link speeds <= 5 GT/s.

  This of course assumes these Ports always train the Link within 100 ms
  even if they are operating at > 5 GT/s, which is not required by the
  spec.

  [test]
  With the patch, the total time s3 resume is 3874.298 ms which is smaller than 
5s.

  [Regression Potential]
  Low. Follow the PCI spec to check whether the device supports DLL Link Active 
reporting, then choose the time of delay.

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

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

[Kernel-packages] [Bug 1845797] Re: Microphone not detected Lenovo Yoga S940

[Daniele Dellafiore]

I've recently upgraded to latest Lenovo Yoga S940, with Intel Core 7 10th gen. 
With Focal Fossa, both audio and mic worked properly until a few days ago. 

Now *sometimes* it loads with dummy audio and no mic at all. 
Now it loaded with only audio and no mic. 

It really seem random to me now.

There is this question that despite a different laptop, has a very similar 
config: 
https://askubuntu.com/questions/1238563/no-sound-pulseaudio-ubuntu-20-04-but-sound-with-pulseaudio-uninstalled

In fact my outputs are:

5.4.0-31-generic

Codec: Realtek ALC298
Codec: Intel Icelake HDMI

00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
Technology Audio Controller (rev 30)

 List of PLAYBACK Hardware Devices 
card 1: PCH [HDA Intel PCH], device 0: ALC298 Analog [ALC298 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 12: HDMI 6 [HDMI 6]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


Finally: 

$ pacmd list-cards 
1 card(s) available.
index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0x605717 irq 164"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "34c8"
device.product.name = "Smart Sound Technology Audio Controller"
device.form_factor = "internal"
device.string = "1"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"

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

Title:
  Microphone not detected Lenovo Yoga S940

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

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.

[Kernel-packages] [Bug 1880653] Re: irq/126-aerdrv always eating 30-40 % of a CPU core

[Rahul Iyer]

As requested, attached output of 'sudo lspci -vvv'

** Attachment added: "Output of 'sudo lspci -vvv'"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880653/+attachment/5376895/+files/sudo%20lspci%20-vvv.txt

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

Title:
  irq/126-aerdrv always eating 30-40 % of a CPU core

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HP Pavilion - 14-al103ne
  Ubuntu 20.04

  'top' command shows irq/126-aerdrv always running eating a lot of CPU.
  Have attached 'powertop' and 'watch -n 1 cat /proc/interrupts' screenshots. 

  Thank you. Please get back for more information

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rahul  1825 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 12:06:46 2020
  HibernationDevice: RESUME=UUID=cc93af0a-17fa-47e4-ae6c-5eb166c23eb9
  InstallationDate: Installed on 2020-05-23 (2 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=4c6e6336-c458-4c50-b8de-561e8608eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-26 (0 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8214
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8214:rvr83.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: Z9D49EA#ABV
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf

[Frank Heimes]

So you used installkernel directly rather than make install.
installkernel is shipped with debianutils
A quick look at the changelog (installkernel) didn't showed any changes this 
year.
So the script itself seems to be stable and unchanged...

You're obviously building and installing kernels in a different way that I do.
I compile and build deb packages directly, that I afterwards just install with 
apt ...

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

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux-base package in Ubuntu:
  New

Bug description:
  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  # ls -l /boot
  total 178364
  -rw--- 1 root root135168 May  6 11:52 bootmap
  -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img -> 
initrd.img-5.4.0-29-generic   <== should point to new version
  -rw-r--r-- 1 root root  19663996 May  6 11:42 initrd.img-5.4.0-29-generic
  -rw-r--r-- 1 root root 125339494 May  6 11:52 
initrd.img-5.7.0-rc4-06500-gb67ea026badd
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img.old -> 
initrd.img-5.4.0-29-generic
  -rw--- 1 root root   3087920 Apr 29 15:34 System.map-5.4.0-29-generic
  -rw-r--r-- 1 root root   4031691 May  6 11:52 
System.map-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   4031691 May  6 11:49 
System.map-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root37 May  6 11:52 vmlinuz -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw--- 1 root root   8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic
  -rw-r--r-- 1 root root   9080832 May  6 11:52 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   9080832 May  6 11:49 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root41 May  6 11:52 vmlinuz.old -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old

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

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

[Kernel-packages] [Bug 1878351] [NEW] System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

kchsieh@kchsieh-laptop:~$ lsb_release -rd
Description:Ubuntu 20.04 LTS (fossa-bulbasaur X23)
Release:20.04

kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
systemd:
  Installed: 245.4-4ubuntu3
  Candidate: 245.4-4ubuntu3
  Version table:
 *** 245.4-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

Expect: When press the button, the endSeesionDialog should show up.
Actual: The system shutdown directly.

When the issue happend:
endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-05-10 (3 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
MachineType: Dell Inc. Vostro 5301
Package: systemd 245.4-4ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
Tags:  focal
Uname: Linux 5.6.0-1010-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.1.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5301
dmi.product.sku: 09FC
dmi.sys.vendor: Dell Inc.

** Affects: oem-priority
 Importance: High
 Assignee: Kai-Chuan Hsieh (kchsieh)
 Status: Confirmed

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


** Tags: apport-collected focal oem-priority originate-from-1878141 somerville
-- 
System shutdown directly by pressing power button and releasing immediately on 
Dell Vostro 5301
https://bugs.launchpad.net/bugs/1878351
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301

[Kai-Heng Feng]

** Package changed: systemd (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/1878351

Title:
  System shutdown directly by pressing power button and releasing
  immediately on Dell Vostro 5301

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

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[AceLan Kao]

** Description changed:

  [Impact]
- iperf3 performance is only 70% of 1Gbps (Intel I219-LM [8086:15b7])
- 
- [Fix]
- Disable TSO on NIC and offload this task to CPU fix this issue.
+ The throughput measured by iperf3 is around 70% of 1Gbps (Intel I219-LM
+ [8086:15b7])
+ I219 is a rather cheap NIC and it impacts its throughput if TSO(TCP
+ segmentation offload) is enabled.  
+ 
+ [Fix]   
+ Disable TSO on NIC and move this task back to CPU fixes this issue.
  The impact of CPU loading is little to none.
- On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU usage 
of iperf3 increases from 1% to 4%
- 
+ On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU
+ usage of iperf3 increases from 1% to 4%
+ 
  [Verify]
  Origin
- [ ID] Interval   Transfer Bandwidth   Retr
- [  4] 0.00-10.00  sec   918 MBytes   770 Mbits/sec0sender
- [  4] 0.00-10.00  sec   916 MBytes   769 Mbits/secreceiver
+ [ ID] Interval Transfer Bandwidth Retr
+ [ 4] 0.00-10.00 sec 918 MBytes 770 Mbits/sec 0 sender
+ [ 4] 0.00-10.00 sec 916 MBytes 769 Mbits/sec receiver
  
  Becomes
- [ ID] Interval   Transfer Bandwidth   Retr
- [  4] 0.00-10.00  sec   1.09 GBytes  936 Mbits/sec0sender
- [  4] 0.00-10.00  sec   1.09 GBytes  934 Mbits/secreceiver
+ [ ID] Interval Transfer Bandwidth Retr
+ [ 4] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 0 sender
+ [ 4] 0.00-10.00 sec 1.09 GBytes 934 Mbits/sec receiver
  
  [Regression Potential]
- Low, disable TSO on Ethernet chip will offload the TCP segmentation task to 
CPU. This increase CPU loading a little bit, and should not introduce any 
regression.
+ Low, disable TSO on Ethernet chip will move the TCP segmentation task
+ to CPU. This increase CPU loading a little bit, and should not introduce
+ any regression. 
  
  =
  
  Testing with iperf3 send speed is only 750mbps while receive speed is
  normal - 940mbps.
  
  Ubuntu 18.04.1
  Msi b250m mortar
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  django 1016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp0s31f6  no wireless extensions.
  
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A69
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  RfKill:
  
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M MORTAR ARCTIC (MS-7A69)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A69
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

** No longer affects: linux (Ubuntu Bionic)

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

-- 
You received this bug notification because you are 

[Kernel-packages] [Bug 1880653] Re: irq/126-aerdrv always eating 30-40 % of a CPU core

[Rahul Iyer]

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

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

Title:
  irq/126-aerdrv always eating 30-40 % of a CPU core

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion - 14-al103ne
  Ubuntu 20.04

  'top' command shows irq/126-aerdrv always running eating a lot of CPU.
  Have attached 'powertop' and 'watch -n 1 cat /proc/interrupts' screenshots. 

  Thank you. Please get back for more information

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rahul  1825 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 12:06:46 2020
  HibernationDevice: RESUME=UUID=cc93af0a-17fa-47e4-ae6c-5eb166c23eb9
  InstallationDate: Installed on 2020-05-23 (2 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=4c6e6336-c458-4c50-b8de-561e8608eb42 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-26 (0 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8214
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8214:rvr83.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: Z9D49EA#ABV
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1879077] Re: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Seth Forshee]

I don't know anything about that package. You should file a new bug
against that package so the maintainers of the package can help.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-firmware 1.157.23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in casper package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  when I am trying to upgrade to 16.04 from 14  , i am getting below
  error

  
  Cmd : lsb_release -rd
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  
  What I expected to happen -- Ubuntu upgrades to 16.04 with upgraded kernel 4.4
 
  What happened instead : it upgraded to 16.04 but with old kernel only and my 
sound has stopped




  
  Setting up initramfs-tools (0.122ubuntu8.16) ...
  update-initramfs: deferring update (trigger activated)
  Setting up linux-firmware (1.157.23) ...
  update-initramfs: Generating /boot/initrd.img-3.13.0-38-generic
  E: amd64-microcode: unsupported kernel version!
  E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
  update-initramfs: failed for /boot/initrd.img-3.13.0-38-generic with 1.
  dpkg: error processing package linux-firmware (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up linux-image-4.4.0-178-generic (4.4.0-178.208) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.
   dpkg: 
dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-firmware; however:
Package linux-firmware is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-image-generic (= 4.4.0.178.186); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for initramfs-tools (0.122ubuntu8.16) ...
  update-initramfs: Generating /boot/initrd.img-3.13.0-38-generic
  E: amd64-microcode: unsupported kernel version!
  E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
  update-initramfs: failed for /boot/initrd.img-3.13.0-38-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Processing 
triggers for linux-image-4.4.0-178-generic (4.4.0-178.208) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 4.4.0-178-generic
  Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive 
which
  does not match this kernel/arch.  This indicates that it should not be built.
 ...done.
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.4.0-178-generic
  E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
  update-initramfs: failed for /boot/initrd.img-4.4.0-178-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-4.4.0-178-generic (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-firmware
   linux-image-generic
   linux-generic
   initramfs-tools
   linux-image-4.4.0-178-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.23
  ProcVersionSignature: Ubuntu 3.13.0-38.65somerville1-generic 3.13.11.9
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  Date: Sat May 16 21:00:04 2020
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script 

[Kernel-packages] [Bug 1880025] [NEW] apparmor="DENIED" on docker container files

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

% docker run -it ubuntu bash
yields:
kernel: audit: type=1400 audit(1590071666.897:72): apparmor="DENIED" 
operation="open" 
profile="snap.docker.dockerd" name="/root/.bashrc" pid=3497 comm="bash" 
requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
with:
vmlinuz-5.4.0-31-generic

Nearly all containers cannot start properly and hence malfunction.

With vmlinuz-5.4.0-29-generic its ok and containers can be started and
work properly.

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

-- 
apparmor="DENIED" on docker container files
https://bugs.launchpad.net/bugs/1880025
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1880025] Re: apparmor="DENIED" on docker container files

[Launchpad Bug Tracker]

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

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

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

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

Title:
  apparmor="DENIED" on docker container files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  % docker run -it ubuntu bash
  yields:
  kernel: audit: type=1400 audit(1590071666.897:72): apparmor="DENIED" 
operation="open" 
  profile="snap.docker.dockerd" name="/root/.bashrc" pid=3497 comm="bash" 
requested_mask="r" 
  denied_mask="r" fsuid=0 ouid=0
  with:
  vmlinuz-5.4.0-31-generic

  Nearly all containers cannot start properly and hence malfunction.

  With vmlinuz-5.4.0-29-generic its ok and containers can be started and
  work properly.

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

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

[Kernel-packages] [Bug 1875884] Re: Kernel log flood "ceph: Failed to find inode for 1"

[Michael Robertson]

Sorry Bot, I am unable to confirm this one myself. AKS images don't get access 
to upgrade kernel from bionic-proposed directly, that I can tell. The standard 
image is still xenial, and its preview bionic images use kernel 5.3.x.x, and do 
not have this issue. 
Flemming, are you able to check this? Any help is appreciated.

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

Title:
  Kernel log flood "ceph: Failed to find inode for 1"

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure-4.15 source package in Bionic:
  New

Bug description:
  OS provided by AKS is currently Ubuntu 16.04.6 LTS, kernel
  4.15.0-1077-azure.

  Every block written by a k8s pod to a ceph CSI volume generates 2 warning 
lines in the node's system logs (kern.log, syslog, messages, warn):
  "Apr 24 09:37:46 aks- kernel: [242123.654538] ceph: Failed to find 
inode for 1"

  Under production load, eventually the node succumbs to DiskPressure as
  the drive fills up. Also performance is noticeably degraded.

  Background here: https://tracker.ceph.com/issues/45283

  Luis Hernandez indicates 4 commits relating to this issue, just 2 of which 
have been backported to Ubuntu 16. 
  d557c48db730 ("ceph: quota: add counter for snaprealms with quota")   <==
  e3161f17d926 ("ceph: quota: cache inode pointer in ceph_snap_realm")
  0eb6bbe4d9cf ("ceph: fix root quota realm check") <==
  2596366907f8 ("ceph: don't check quota for snap inode")

  Quoth Luis:
  "I've done a quick test and, after compiling the bionic kernel 4.15.0-96.97 
(the latest released), I can reproduce the issue. Cherry-picking the 2 missing 
commits (2596366907f8 and e3161f17d926) fixes it."

  In my testing Ubuntu 18 does not exhibit the bug, but Azure support
  tells me it will be months before they make it GA in AKS.

  Can we get those commits backported to Ubuntu 16?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-azure (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-1077.82-azure 4.15.18
  Uname: Linux 4.15.0-1077-azure x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  Date: Wed Apr 29 12:45:12 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-azure
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux-azure-4.15
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1082-azure 
root=UUID=026eedeb-bd55-4fe3-9e65-0f5f76c13202 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  ProcVersionSignature: Ubuntu 4.15.0-1082.92~16.04.1-azure 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1082-azure N/A
   linux-backports-modules-4.15.0-1082-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.15.0-1082-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 2B0B428F-CF5B-3142-8500-028AFD70E74B
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1880025] Re: apparmor="DENIED" on docker container files

[Jamie Strandboge]

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

Actually, this is 1879690 which is a bug in the Ubuntu kernel.

** Project changed: snapd => linux (Ubuntu)

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

** This bug has been marked a duplicate of bug 1879690
   Docker registry doesn't stay up and keeps restarting

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

Title:
  apparmor="DENIED" on docker container files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  % docker run -it ubuntu bash
  yields:
  kernel: audit: type=1400 audit(1590071666.897:72): apparmor="DENIED" 
operation="open" 
  profile="snap.docker.dockerd" name="/root/.bashrc" pid=3497 comm="bash" 
requested_mask="r" 
  denied_mask="r" fsuid=0 ouid=0
  with:
  vmlinuz-5.4.0-31-generic

  Nearly all containers cannot start properly and hence malfunction.

  With vmlinuz-5.4.0-29-generic its ok and containers can be started and
  work properly.

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

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

[Kernel-packages] [Bug 1880695] [NEW] system hangs at shutdown or restart

[Chao Yao]

Public bug reported:

Release: Linux Mint 19.3 Tricia

What you expected to happen:
The OS is shut down and the computer is powered off when the shutdown button is 
clicked.

4) What happened instead
System hangs at a screen with logo or no screen signal after shutdown or reboot 
is commanded (via button or command line). The OS has no response, the computer 
is still on power as normal.
This issue occurs after a kernel update from 4.15.0 to 5.3.0.51 and keeps up to 
current kernel 5.3.0.53.

version:
Linux version 5.3.0-53-generic (buildd@lgw01-amd64-016) (gcc version 7.5.0 
(Ubuntu 7.5.0-3ubuntu1~18.04)) #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 
2020

pci:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) Root Complex [1022:1450]
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) Root Complex [1022:1450]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 59)
Subsystem: Gigabyte Technology Co., Ltd FCH SMBus Controller [1458:5001]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: nvme
Kernel modules: nvme

02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:43b9] (rev 02) (prog-if 30 [XHCI])
Subsystem: ASMedia Technology Inc. Device [1b21:1142]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: xhci_hcd

02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:43b5] (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: ASMedia Technology Inc. Device [1b21:1062]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

02:00.2 PCI bridge [06

[Kernel-packages] [Bug 1876707] Re: NULL pointer dereference in nvme reset work-queue when VMD raid mode and SecureBoot turned on simultaneously on TigerLake

[You-Sheng Yang]

https://lists.ubuntu.com/archives/kernel-team/2020-May/110244.html (unstable)
https://lists.ubuntu.com/archives/kernel-team/2020-May/110287.html (oem-5.6)

** Description changed:

+ [SRU Justfication]
+ 
+ [Impact]
+ 
+ On platforms with NVMe attached to VMD controller, enable SecureBoot
+ would also force enable iommu:
+ 
+   DMAR: Intel-IOMMU force enabled due to platform opt in
+ 
+ While devices behind the VMD controller, also a PCI bridge, maybe forced
+ to use a DMA domain by current Intel-IOMMU driver, this may break some
+ relationships between sub devices behind VMD controller and between the
+ VMD controller and its children devices, and finally caused undefined
+ system behavior.
+ 
+ On devices at hand, this results in kernel NULL dereference at
+ __intel_map_single called from nvme_reset_work and fails root device
+ lookup at boot.
+ 
+   kernel: BUG: kernel NULL pointer dereference, address: 0018
+   kernel: #PF: supervisor read access in kernel mode
+   kernel: #PF: error_code(0x) - not-present page
+   kernel: PGD 0 P4D 0
+   kernel: Oops:  [#2] SMP NOPTI
+   kernel: CPU: 1 PID: 254 Comm: kworker/u8:4 Tainted: G D W
+   5.7.0-050700rc3-generic #202004262131
+   kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
+   kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
+   kernel: RIP: 0010:__intel_map_single+0xa3/0x1a0
+   ...
+ 
+ [Fix]
+ 
+ Patchset[1] currently landed in iommu/next beginning with commit
+ 327d5b2fee91 ("iommu/vt-d: Allow 32bit devices to uses DMA domain")
+ gives the solution to this problem. However, it's based on a massive
+ subsystem rewrite in patchset[2], currently in iommu/next beginning with
+ commit 441ff2ff8327 ("Move default domain allocation to separate
+ function").
+ 
+ On v5.6, it also depends on yet a few more patch series landed in
+ v5.7-rc1 beginning with commit 098accf2da94 ("iommu: Use C99 flexible
+ array in fwspec") that rewrote private data access, changed struct
+ names, etc.
+ 
+ Yet a few additional patches included as fixes to above changes.
+ 
+ [1]: 
https://lore.kernel.org/linux-iommu/7928dd48-93da-62f0-b455-6e6b248d0...@linux.intel.com/
+ [2]: 
https://lore.kernel.org/linux-iommu/20200429133712.31431-1-j...@8bytes.org/
+ 
+ [Test Case]
+ 
+ Test on platforms with VMD/NVMe and enable SecureBoot. System should
+ boot normally rather than into initramfs emergency shell.
+ 
+ [Regression Potential]
+ 
+ For unstable, all the patches are from iommu-next and will probably be
+ merged in next few -rc releases, so should be safe to place a LOW here.
+ 
+ For oem-5.6, the fixing patchset is depending on iommu group setup
+ refactoring that touched almost every architecture/platform uses iommu
+ although we would only care amd64 among them. Even with follow-up fixes
+ included, this is still a 60-patches change and deserves some more
+ attention. Medium.
+ 
+ == Original Bug Description ==
+ 
  This is found on a Dell TigerLake platform that when VMD raid mode is
  turned on along with SecureBoot, either deploy mode or audit mode,
  kernel dumps warnings and null pointer deref errors at boot. While it
  happens, it blocks systemd-udevd worker processes until killed due to
  timeout. System still boots to multi-users.target.
  
  Kernel bisect shows commit e3560ee4cfb2 ("iommu/vt-d: Remove VMD child
  device sanity check") merged in v5.6-rc1 is the first commit to fail,
  and is still reproducible on v5.7-rc3.
  
  kernel: Secure boot disabled
  ...
  kernel: [ cut here ]
  kernel: WARNING: CPU: 1 PID: 8 at drivers/iommu/intel-iommu.c:625 
domain_get_iommu+0x4b/0x60
  kernel: Modules linked in: rc_core r8169(+) intel_lpss nvme crc32_pclmul(+) 
psmouse intel_ish_ipc(+) i2c_hid i2c_i801(+) realtek idma64 drm virt_dma 
intel_ishtp vmd(+) nvme_core hid video wmi pinctrl_tigerlake pinctrl_intel
  kernel: CPU: 1 PID: 8 Comm: kworker/u8:0 Not tainted 5.7.0-050700rc3-generic 
#202004262131
  kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
  kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
  kernel: RIP: 0010:domain_get_iommu+0x4b/0x60
  kernel: Code: eb 22 48 8d 50 01 48 39 c8 74 1b 48 89 d0 8b 74 87 04 48 63 d0 
85 f6 74 e9 48 8b 05 ef 63 63 01 48 8b 04 d0 5d c3 31 c0 5d c3 <0f> 0b 31 c0 5d 
c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f
  kernel: RSP: 0018:b5f5c00fbcf8 EFLAGS: 00010202
  kernel: RAX: 9ebdaf100b00 RBX:  RCX: 
  kernel: RDX: 1000 RSI: 00036dd41000 RDI: 9ebdaf100b00
  kernel: RBP: b5f5c00fbcf8 R08:  R09: 9ebdadd41000
  kernel: R10: 8d069060 R11: 4879 R12: 9ebdadd810b0
  kernel: R13: 00036dd41000 R14:  R15: 9ebdaf100b00
  kernel: FS:  () GS:9ebdc168() 
knlGS:
  kernel: CS:  0010 DS:  ES:  CR0: 80050033
  kernel: CR2: 7f900d20e660 CR3: 00

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

[Ubuntu Kernel Bot]

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

apport-collect 1880695

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

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

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

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

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

Title:
  system hangs at shutdown or restart

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release: Linux Mint 19.3 Tricia

  What you expected to happen:
  The OS is shut down and the computer is powered off when the shutdown button 
is clicked.

  4) What happened instead
  System hangs at a screen with logo or no screen signal after shutdown or 
reboot is commanded (via button or command line). The OS has no response, the 
computer is still on power as normal.
  This issue occurs after a kernel update from 4.15.0 to 5.3.0.51 and keeps up 
to current kernel 5.3.0.53.

  version:
  Linux version 5.3.0-53-generic (buildd@lgw01-amd64-016) (gcc version 7.5.0 
(Ubuntu 7.5.0-3ubuntu1~18.04)) #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 
2020

  pci:
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) Root Complex [1022:1450]
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) Root Complex [1022:1450]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

  00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 59)
Subsystem: Gigabyte Technology Co., Ltd FCH SMBus Controller [1458:5001]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel 

[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Medium

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

Title:
  Dell Latitude 7300 sometimes stuck at purple screen after grub and
  fails to boot up

Status in OEM Priority Project:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub.
  There is no any log in journal when it fails to boot up, and earlyprintk 
shows nothing on the screen, either.

  System Information
  Manufacturer: Dell Inc.
  Product Name: Latitude 7300
  Version: Not Specified
  Serial Number: J83ZST2
  UUID: 4C4C4544-0038-3310-805A-CAC04F535432
  Wake-up Type: Power Switch
  SKU Number: 08E0
  Family: Latitude

  BIOS Information
  Vendor: Dell Inc.
  Version: 1.6.1
  Release Date: 11/14/2019
  Address: 0xF
  Runtime Size: 64 kB
  ROM Size: 24 MB
  Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
  BIOS Revision: 1.6

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

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

[Kernel-packages] [Bug 1880445] Re: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04)

[Anton Martynenko]

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

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

Title:
  Hercules Classic Link does not work in recent Ubuntu versions (but
  does in 14.04 and 16.04)

Status in linux package in Ubuntu:
  New

Bug description:
  I've got a bug similar to this one here
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872634

  There's a detailed description here
  https://askubuntu.com/questions/1241552/making-hercules-classic-link-
  web-camera-work-with-ubuntu-19-10

  The strange thing is, it does not work in 19.10 and live-usb 20.04,
  but it does work in 14.04 and 16.04. The last one I tried from
  Virtualbox by adding a USB device in the settings - and it works just
  fine. When I do `lsmod | grep gspca` in 16.04, I get the following
  output:

  gspca_pac7302  20480  0
  gspca_main 36864  1 gspca_pac7302
  v4l2_common16384  2 gspca_main
  videodev  188416  3 gspca_main, gspca_pac7302, v4l2_common

  Whereas on my machine with 19.10 it's like this:

  gspca_pac7302  20480  0
  gspca_main 24576  1 gspca_pac7302
  videobuf2_vmalloc  20480  1 gspca_main
  videobuf2_v4l2 24576  1 gspca_main
  videobuf2_common   53248  2 gspca_main,videobuf2_v4l2
  videodev  208896  5 
gspca_main,gspca_pac7302,v4l2_common,videobuf2_v4l2,videobuf2_common

  I already tried modprobe -r for all videobuf2_* and gspca_* modules
  and adding v4l2, but it just restored the previous module config.

  Could you please advice how could I solve this? I'm not sure which way to 
follow from here.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mao3074 F pulseaudio
   /dev/snd/controlC0:  mao3074 F pulseaudio
   /dev/snd/controlC1:  mao3074 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  HibernationDevice: RESUME=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 
resume_offset=66347008
  InstallationDate: Installed on 2020-02-09 (105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 ro 
resume=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 resume_offset=66347008 quiet 
splash
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-53-generic N/A
   linux-backports-modules-5.3.0-53-generic  N/A
   linux-firmware1.183.5
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd netdev plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  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.:bvrF4:bd09/04/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/1880445/+subscriptions

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Hercules Classic Link does not work in recent Ubuntu versions (but
  does in 14.04 and 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got a bug similar to this one here
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872634

  There's a detailed description here
  https://askubuntu.com/questions/1241552/making-hercules-classic-link-
  web-camera-work-with-ubuntu-19-10

  The strange thing is, it does not work in 19.10 and live-usb 20.04,
  but it does work in 14.04 and 16.04. The last one I tried from
  Virtualbox by adding a USB device in the settings - and it works just
  fine. When I do `lsmod | grep gspca` in 16.04, I get the following
  output:

  gspca_pac7302  20480  0
  gspca_main 36864  1 gspca_pac7302
  v4l2_common16384  2 gspca_main
  videodev  188416  3 gspca_main, gspca_pac7302, v4l2_common

  Whereas on my machine with 19.10 it's like this:

  gspca_pac7302  20480  0
  gspca_main 24576  1 gspca_pac7302
  videobuf2_vmalloc  20480  1 gspca_main
  videobuf2_v4l2 24576  1 gspca_main
  videobuf2_common   53248  2 gspca_main,videobuf2_v4l2
  videodev  208896  5 
gspca_main,gspca_pac7302,v4l2_common,videobuf2_v4l2,videobuf2_common

  I already tried modprobe -r for all videobuf2_* and gspca_* modules
  and adding v4l2, but it just restored the previous module config.

  Could you please advice how could I solve this? I'm not sure which way to 
follow from here.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mao3074 F pulseaudio
   /dev/snd/controlC0:  mao3074 F pulseaudio
   /dev/snd/controlC1:  mao3074 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  HibernationDevice: RESUME=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 
resume_offset=66347008
  InstallationDate: Installed on 2020-02-09 (105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 ro 
resume=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 resume_offset=66347008 quiet 
splash
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-53-generic N/A
   linux-backports-modules-5.3.0-53-generic  N/A
   linux-firmware1.183.5
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd netdev plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  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.:bvrF4:bd09/04/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/1880445/+subscriptions

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

[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[John Chittum]

May 22nd was made available when I commented. Not sure why your update
didn't find it. Maybe there's lag with specific mirrors. Official
listings show them available:


https://app.vagrantup.com/ubuntu/boxes/focal64

https://app.vagrantup.com/ubuntu/boxes/eoan64

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

  Impact: When our kernel packaging was updated to build the virtualbox
  guest packages by downloading the dkms package, the modules were
  accidentally moved to linux-modules-extra instead of linux-modules.
  This has caused the modules to go missing in our Vagrant images.

  Fix: Move the modules back to linux-modules.

  Test Case: Build the kernel packages and confirm that the vboxguest
  and vboxsf drivers are now in linux-modules rather than linux-modules-
  extra.

  Regression Potential: Since linux-modules is required, anyone who is
  using the vbox drivers will continue to have them after this change.
  Therefore the risk of regression is extremely low.

  
  ---

  
  Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the 
`/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the 
Vagrant error message:

  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  : No such device

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[John Chittum]

apologies -- the 0518 Focal image has the fix as well. That may not have
been clear since the comments came on the 19th, and I updated on the
22nd. The eoan 22nd made it up on the 22nd, but there was lag with the
Focal 0522 serial syncing on our end. It's up there 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/1873506

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

  Impact: When our kernel packaging was updated to build the virtualbox
  guest packages by downloading the dkms package, the modules were
  accidentally moved to linux-modules-extra instead of linux-modules.
  This has caused the modules to go missing in our Vagrant images.

  Fix: Move the modules back to linux-modules.

  Test Case: Build the kernel packages and confirm that the vboxguest
  and vboxsf drivers are now in linux-modules rather than linux-modules-
  extra.

  Regression Potential: Since linux-modules is required, anyone who is
  using the vbox drivers will continue to have them after this change.
  Therefore the risk of regression is extremely low.

  
  ---

  
  Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the 
`/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the 
Vagrant error message:

  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  : No such device

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Simon Repp]

Correction for my last post: More investigation revealed that the issue
IS harmless after all - the error message just happened to be the only
message printed on an otherwise black and unresponsive screen for
multiple seconds before a timeout occurs that after further research
turned out to be caused by something else, not the decoding failure.
Regardless of that the rest of my previous post still applies. (The
"harmless message" exists and does not go away by following the steps
outlined by others, at least for me)

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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

[Kernel-packages] [Bug 1880381] [NEW] No full shutdown 5.3.0-53

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After shutdown the fan is still running. I need to push the power-button to 
final shutdown.
So I changed back to 5.3.0-51 and blocked update.

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


** Tags: bot-comment
-- 
No full shutdown 5.3.0-53
https://bugs.launchpad.net/bugs/1880381
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1880382] [NEW] Wake up from suspend restarts the machine

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Recently I have updated my system with sudo apt update and upgrade.
A new kernel was installed.
Before that i was able to suspend and wake up without a problem.
After the upgrade every time I wake from suspend, the monitor stay blank and 
don't even switch on and after maybe 30 seconds the systems just reboots.
I have to reopen all my applications again...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evince 3.36.0-2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 24 12:52:56 2020
InstallationDate: Installed on 2020-04-24 (29 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bot-comment focal third-party-packages
-- 
Wake up from suspend restarts the machine
https://bugs.launchpad.net/bugs/1880382
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Confirmed, it is available now and 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/1873506

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

  Impact: When our kernel packaging was updated to build the virtualbox
  guest packages by downloading the dkms package, the modules were
  accidentally moved to linux-modules-extra instead of linux-modules.
  This has caused the modules to go missing in our Vagrant images.

  Fix: Move the modules back to linux-modules.

  Test Case: Build the kernel packages and confirm that the vboxguest
  and vboxsf drivers are now in linux-modules rather than linux-modules-
  extra.

  Regression Potential: Since linux-modules is required, anyone who is
  using the vbox drivers will continue to have them after this change.
  Therefore the risk of regression is extremely low.

  
  ---

  
  Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the 
`/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the 
Vagrant error message:

  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  : No such device

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

[Kernel-packages] [Bug 1880381] Re: No full shutdown 5.3.0-53

[Brian Murray]

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

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

Title:
  No full shutdown 5.3.0-53

Status in linux package in Ubuntu:
  New

Bug description:
  After shutdown the fan is still running. I need to push the power-button to 
final shutdown.
  So I changed back to 5.3.0-51 and blocked update.

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

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

[Kernel-packages] [Bug 1880382] Re: Wake up from suspend restarts the machine

[Brian Murray]

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

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

Title:
  Wake up from suspend restarts the machine

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently I have updated my system with sudo apt update and upgrade.
  A new kernel was installed.
  Before that i was able to suspend and wake up without a problem.
  After the upgrade every time I wake from suspend, the monitor stay blank and 
don't even switch on and after maybe 30 seconds the systems just reboots.
  I have to reopen all my applications again...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 24 12:52:56 2020
  InstallationDate: Installed on 2020-04-24 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1880381

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

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

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

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

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

Title:
  No full shutdown 5.3.0-53

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After shutdown the fan is still running. I need to push the power-button to 
final shutdown.
  So I changed back to 5.3.0-51 and blocked update.

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

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

[Kernel-packages] [Bug 1880716] [NEW] modprobe sometimes fails to detect ather10k_pci during boot, causing Linux to not recognize my Wi-Fi card

[Seija Kijin]

Public bug reported:

During boot, Plymouth sometimes says "failed to init core (-1)" and
"failed to probe ath10k_pci",l and then after boot, my laptop has no wi-
fi, and the network center says it cannot find a wireless adapter.

Rebooting fixes the issue, but this shouldn't happen in the first place.
I also manually modprobed ath10k_pci to ensure next boot would have the
network card.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  seija  1497 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue May 26 11:11:09 2020
InstallationDate: Installed on 2020-05-07 (19 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.5
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  seija  1497 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-05-07 (19 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
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-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
Tags:  focal
Uname: Linux 5.4.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 02/20/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.5
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug apport-collected focal

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

** Tags added: apport-collected

** Description changed:

  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no wi-
  fi, and the network center says it cannot find a wireless adapter.
  
  Rebooting fixes the issue, but this shouldn't happen in the firs

[Kernel-packages] [Bug 1880716] CurrentDmesg.txt

[Seija Kijin]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376973/+files/CurrentDmesg.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspi

[Kernel-packages] [Bug 1880716] Lspci-vt.txt

[Seija Kijin]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376976/+files/Lspci-vt.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dm

[Kernel-packages] [Bug 1880716] WifiSyslog.txt

[Seija Kijin]

apport information

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

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron

[Kernel-packages] [Bug 1880716] ProcInterrupts.txt

[Seija Kijin]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376981/+files/ProcInterrupts.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: I

[Kernel-packages] [Bug 1880716] ProcCpuinfo.txt

[Seija Kijin]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376979/+files/ProcCpuinfo.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiro

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

[Seija Kijin]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376980/+files/ProcCpuinfoMinimal.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.f

[Kernel-packages] [Bug 1880716] RfKill.txt

[Seija Kijin]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1880716/+attachment/5376983/+files/RfKill.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.pro

[Kernel-packages] [Bug 1880716] Lsusb-v.txt

[Seija Kijin]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376978/+files/Lsusb-v.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.

[Kernel-packages] [Bug 1880716] AlsaInfo.txt

[Seija Kijin]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376971/+files/AlsaInfo.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dm

[Kernel-packages] [Bug 1880716] Lsusb-t.txt

[Seija Kijin]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376977/+files/Lsusb-t.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.

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

[Seija Kijin]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376982/+files/ProcModules.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiro

[Kernel-packages] [Bug 1880716] Lspci.txt

[Seija Kijin]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1880716/+attachment/5376975/+files/Lspci.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.produ

[Kernel-packages] [Bug 1880716] UdevDb.txt

[Seija Kijin]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1880716/+attachment/5376984/+files/UdevDb.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.pro

[Kernel-packages] [Bug 1880716] IwConfig.txt

[Seija Kijin]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1880716/+attachment/5376974/+files/IwConfig.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dm

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

[Seija Kijin]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1880716/+attachment/5376972/+files/CRDA.txt

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product

[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders

[Jake Cobb]

Yes, there is some lag.  Although the image is named 0522, it was not
available until the 25th of May, note the created message from your
link:

"v20200522.0.0 currently released version
This version was created about 24 hours ago."

I did test the 0518 focal image and it was not fixed, 0522 is the first
that works.

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

Title:
  ubuntu/focal64 fails to mount Vagrant shared folders

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

  Impact: When our kernel packaging was updated to build the virtualbox
  guest packages by downloading the dkms package, the modules were
  accidentally moved to linux-modules-extra instead of linux-modules.
  This has caused the modules to go missing in our Vagrant images.

  Fix: Move the modules back to linux-modules.

  Test Case: Build the kernel packages and confirm that the vboxguest
  and vboxsf drivers are now in linux-modules rather than linux-modules-
  extra.

  Regression Potential: Since linux-modules is required, anyone who is
  using the vbox drivers will continue to have them after this change.
  Therefore the risk of regression is extremely low.

  
  ---

  
  Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the 
`/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the 
Vagrant error message:

  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  : No such device

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  modprobe sometimes fails to detect ather10k_pci during boot, causing
  Linux to not recognize my Wi-Fi card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot, Plymouth sometimes says "failed to init core (-1)" and
  "failed to probe ath10k_pci",l and then after boot, my laptop has no
  wi-fi, and the network center says it cannot find a wireless adapter.

  Rebooting fixes the issue, but this shouldn't happen in the first
  place. I also manually modprobed ath10k_pci to ensure next boot would
  have the network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 26 11:11:09 2020
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1497 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=216a90ea-efc4-4b0a-af00-02776f1f88d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  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-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sk

[Kernel-packages] [Bug 1875863] Re: ceph -- Unable to mount ceph volume on s390x

[Frank Heimes]

@kernel-team and @ubuntu-archive just for clarification: the 
'verification-failed-focal' tag was only set because the kernel in proposed 
that should have the patch that is mentioned here included, needed to be 
revoked due to a regression and the kernel used for the verification didn't had 
it in.
So the verification was not possible, rather than failed.

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

Title:
  ceph -- Unable to mount ceph volume on s390x

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Unable to mount ceph volumes on big endian systems, like s390x.

  * The mount operation always fails with an IO error.

  * This is caused by an endiness issue in function handle_session where
  variable features is always little endian.

  * But test_bit assumes the host order of bytes, hence causes a problem
  on big endian systems.

  [Fix]

  * 0fa8263367db9287aa0632f96c1a5f93cc478150 0fa8263367db "ceph: fix
  endianness bug when handling MDS session feature bits"

  [Test Case]

  * Setup ceph on s390x.

  * Try to mount a ceph volume.

  * If it mounts correctly the patch is applied and working.

  * Without the patch a mount always fails on big endian / s390x.

  [Regression Potential]

  * There is regression potential with having code changes in ceph's
  session handler, which is common code.

  * However, the patch was accepted (slightly changed) by the ceph
  maintainers and with that got upstream accepted, too.

  * The patch is fairly limited (5 lines removed, 3 added), hence the
  changes are quite traceable.

  __

  When mounting a ceph volume, mount operation fails with an IO error.
  The problem is always reproducible.

  Identified potential root cause as kernel endian bug:

  In the function handle_session() variable @features always
  contains little endian order of bytes. Just because The feature
  mask sent by the MDS is little-endian (bits are packed bytewise
  from left to right in encode_supported_features()).

  However, test_bit(), called to check features availability, assumes
  the host order of bytes in that variable. This leads to problems on
  big endian architectures. Specifically it is impossible to mount
  ceph volume on s390.

  A fixup was proposed to convert little-endian order of bytes to the
  host one. That fixup was modified by ceph maintainers to use existing
  unpacking means for the conversion. The resulted patch attached.

  Related discussion in the ceph-development mailing list:
  https://marc.info/?l=ceph-devel&m=158815357301332&w=2

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

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

[Kernel-packages] [Bug 1880593] Re: TouchPad not working

[pablo josé blanco]

attaching journal -b output

Thanks!

** Attachment added: "journal -b output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880593/+attachment/5376999/+files/journal-b.out

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

Title:
  TouchPad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Support team, in a fresh installation in a lenovo laptop, touchpad
  is not working. mouse is working fine though.

  Attaching /proc/bus/input/devices as per debugging wiki.

  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

  Kind regards,
  Pablo.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pali   1214 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 15:05:38 2020
  InstallationDate: Installed on 2020-05-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless 
Mouse
   Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82C5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=3b0502a4-3082-45eb-ac7e-12a3c6b934ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
  dmi.product.family: V15-IIL
  dmi.product.name: 82C5
  dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL
  dmi.product.version: Lenovo V15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1880695] Re: system hangs at shutdown or restart

[Chao Yao]

Similar issue from other:
https://forums.linuxmint.com/viewtopic.php?t=291675

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

Title:
  system hangs at shutdown or restart

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release: Linux Mint 19.3 Tricia

  What you expected to happen:
  The OS is shut down and the computer is powered off when the shutdown button 
is clicked.

  4) What happened instead
  System hangs at a screen with logo or no screen signal after shutdown or 
reboot is commanded (via button or command line). The OS has no response, the 
computer is still on power as normal.
  This issue occurs after a kernel update from 4.15.0 to 5.3.0.51 and keeps up 
to current kernel 5.3.0.53.

  version:
  Linux version 5.3.0-53-generic (buildd@lgw01-amd64-016) (gcc version 7.5.0 
(Ubuntu 7.5.0-3ubuntu1~18.04)) #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 
2020

  pci:
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) Root Complex [1022:1450]
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) Root Complex [1022:1450]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

  00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

  00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 59)
Subsystem: Gigabyte Technology Co., Ltd FCH SMBus Controller [1458:5001]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: nvme
Kernel modules: nvme

  02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:43b9] (rev 02) (prog-if 30 [XHCI])
Subsystem: ASMedia Technology Inc. Device [1b21:1142]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: xhci_hcd

  02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:43b5] (

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

[bugproxy]

--- Comment From geral...@de.ibm.com 2020-05-26 12:40 EDT---
(In reply to comment #8)
> Is there a patch/commit out that disabled these messages/migration-warning?

No, and I do not see why this was mirrored at all. This is no bug, this
is absolutely normal behaviour since like forever.

These warnings will always show, for example, when trying to set a
memory block offline which is not removable, i.e. which contains
unmovable pages.

I can only assume that those might now show more often with current
kernels, as there has been some common code rework by David Hildenbrand,
which basically eliminates the previously present "removable yes/no"
heuristic, because it was very confusing and also racy and thus
unreliable. IIRC, now all memory blocks are reported as removable "yes",
because this cannot really be reported reliably at all.

So, now tools like chmem might try to set permanently un-removable
blocks offline more often, because they check the (unreliable) removable
attribute. Before the upstream common code change, such tools could have
missed removable blocks, but triggered less warnings. Now they will not
miss any, but also try offlining blocks that really are permanently un-
removable, thus triggering more warnings.

But the warning itself is not new or a bug at all. So, since all works
as designed, closing this bugzilla.

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

Title:
  [Ubuntu 20.04] memory hotplug triggers page migration warnings

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

Bug description:
  kernel:
  Linux t35lp11 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC 2020 
s390x s390x s390x GNU/Linux

  How to reproduce:
  1. Disable hotplugable memory
   # chmem -d 1G
  2. Look at the kernel messages
   # dmesg -T

  Then you should see the following:
  ...
  [Mon Apr 20 10:28:30 2020] page:03d08300 refcount:1 mapcount:0 
mapping:eb7f3600 index:0x0 compound_mapcount: 0
  [Mon Apr 20 10:28:30 2020] flags: 0x7fffe010200(slab|head)
  [Mon Apr 20 10:28:30 2020] raw: 07fffe010200 0100 
0122 eb7f3600
  [Mon Apr 20 10:28:30 2020] raw:  0035006a 
0001 
  [Mon Apr 20 10:28:30 2020] page dumped because: unmovable page
  [Mon Apr 20 10:28:30 2020] page:03d082564000 refcount:1 mapcount:0 
mapping:a88d3600 index:0x0 compound_mapcount: 0
  [Mon Apr 20 10:28:30 2020] flags: 0x7fffe010200(slab|head)
  [Mon Apr 20 10:28:30 2020] raw: 07fffe010200 0100 
0122 a88d3600
  [Mon Apr 20 10:28:30 2020] raw:  004e009c 
0001 
  [Mon Apr 20 10:28:30 2020] page dumped because: unmovable page
  [Mon Apr 20 10:28:30 2020] page:03d081fb refcount:1 mapcount:0 
mapping: index:0x0
  [Mon Apr 20 10:28:30 2020] flags: 0x3fffe00()
  [Mon Apr 20 10:28:30 2020] raw: 03fffe00 0100 
0122 
  [Mon Apr 20 10:28:30 2020] raw:   
0001 
  [Mon Apr 20 10:28:30 2020] page dumped because: unmovable page
  [Mon Apr 20 10:28:30 2020] page:03d08000 refcount:1 mapcount:0 
mapping: index:0x0
  [Mon Apr 20 10:28:30 2020] flags: 0x3fffe001000(reserved)
  [Mon Apr 20 10:28:30 2020] raw: 03fffe001000 03d08008 
03d08008 
  [Mon Apr 20 10:28:30 2020] raw:   
0001 
  [Mon Apr 20 10:28:30 2020] page dumped because: unmovable page

  ...

  --

  Maybe helpful information:

  --
  /proc/zoneinfo:
  Node 0, zone  DMA
per-node stats
nr_inactive_anon 37
nr_active_anon 10899
nr_inactive_file 60239
nr_active_file 12110
nr_unevictable 4237
nr_slab_reclaimable 19489
nr_slab_unreclaimable 21873
nr_isolated_anon 0
nr_isolated_file 0
workingset_nodes 0
workingset_refault 0
workingset_activate 0
workingset_restore 0
workingset_nodereclaim 0
nr_anon_pages 13413
nr_mapped19622
nr_file_pages 74144
nr_dirty 2
nr_writeback 0
nr_writeback_temp 0
nr_shmem 79
nr_shmem_hugepages 0
nr_shmem_pmdmapped 0
nr_file_hugepages 0
nr_file_pmdmapped 0
nr_anon_transparent_hugepages 0
nr_unstable  0
nr_vmscan_write 0
nr_vmscan_immediate_reclaim 0
nr_dirtied   18735
nr_written   17734
nr_kernel_misc_reclaimable 0
pages free 519949
  min  1066
  low  1590
  high 2114
  spanned  524288
  

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

[Silicomancer]

I got the same when installing uswsusp.

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

Title:
  update-initramfs complains of missing amdgpu firmware files

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

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

[Kernel-packages] [Bug 1877476] Re: HP 820 G3 resume from hibernation hangs with color bars

[Mike]

I have checked ppa mainline kernel 5.4.14 and 5.6 with the same resume
from hibernate problematic behavior(The i915 drivers are updated there).

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

Title:
  HP 820 G3 resume from hibernation hangs with color bars

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 5.4.0-29.33-generic 5.4.30

  I am using Legacy mode in BIOS to boot laptop. 
  I hibernate (I tried "systemctl hibernate" and "sudo hibernate") to swap file 
(allocated size 18GB  what is 2GB more than my RAM size) and both methods 
hibernates to file OK.
  After hibernation I want to resume.
  First resume always ends suspended on color bars after ca 1 min and 2 times 
backlighted screen meantime. Keyboard driver can accept CTL+ALT+DEL to restart 
or I can power off and power on again.
  Second restart always loads grub normally and after I choose default ooot 
option it correctly resumes from swap file but it should work in this way from 
the first resume try.

  I've tried updated grub with options: nosplash, noquiet, nomodeset and
  even keeping shift in BIOS to see what's going during failed resume
  but no success.

  nomodeset option doesn't show color bars, but finishes with backlighted black 
screen only.
  Keeping shift in BIOS shows: " RUB loading" without G but after minute it 
ends on blank backlighted screen. Keeping ESC doesn't help to see any line from 
boot even nosplash and noquiet is active.

  Normal suspend and resume from suspend works but hibernation not.

  Only dmesg line is concerning, but I think nomodeset should eliminate if it 
would be i915 problem.
  [   10.015720] i915 :00:02.0: [drm:intel_dp_aux_init_backlight_funcs 
[i915]] Panel advertises DPCD backlight support, but VBT disagrees. If your 
backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If 
your machine needs this, please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  Anyway backlight controls is working OK without nomodeset option.

  HP BIOS is updated from 01/05/2020 and laptop is about 4 years old.

  
  System:
Host: UB820 Kernel: 5.4.0-29-generic x86_64 bits: 64 Desktop: Gnome 3.36.1 
Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:
Type: Laptop System: HP product: HP EliteBook 820 G3 v: N/A 
serial:  
Mobo: HP model: 807C v: KBC Version 85.79 
serial:  UEFI [Legacy]: HP v: N75 Ver. 01.45 
date: 01/05/2020 
  Battery:
ID-1: BAT0 charge: 34.0 Wh condition: 35.1/35.1 Wh (100%) 
  CPU:
Topology: Dual Core model: Intel Core i5-6300U bits: 64 type: MT MCP 
L2 cache: 3072 KiB 
Speed: 800 MHz min/max: 400/3000 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel 
Display: x11 server: X.Org 1.20.8 driver: vesa unloaded: fbdev,modesetting 
resolution: 1366x768~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.0.4 
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
Sound Server: ALSA v: k5.4.0-29-generic 
  Network:
Device-1: Intel Ethernet I219-LM driver: e1000e 
IF: enp0s31f6 state: down mac: XX:XX:XX:XX:XX:XX 
Device-2: Intel Wireless 8260 driver: iwlwifi 
IF: wlp2s0 state: up mac: XX:XX:XX:XX:XX:XX 
Device-3: HP HP lt4120 Snapdragon X5 LTE type: USB driver: cdc_ether 
IF: enxda94de160772 state: up speed: N/A duplex: N/A 
mac: XX:XX:XX:XX:XX:XX 
  Drives:
Local Storage: total: 704.24 GiB used: 26.12 GiB (3.7%) 
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
ID-2: /dev/sdb vendor: Samsung model: MZNLN256HCHP-000H1 size: 238.47 GiB 
  Partition:
ID-1: / size: 457.45 GiB used: 26.12 GiB (5.7%) fs: ext4 dev: /dev/sda1 
  Sensors:
System Temperatures: cpu: 38.5 C mobo: 0.0 C 
Fan Speeds (RPM): N/A

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

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