[Kernel-packages] [Bug 1890237] [NEW] ubuntu 20.4 on lenovo ideapad3 doesn't see touchpad

2020-08-03 Thread Irene Meisel
Public bug reported:

ubuntu 20.4 on lenovo ideapad3 doesn't see touchpad

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  4 01:18:31 2020
InstallationDate: Installed on 2020-07-23 (11 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81W4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=f6d8bd72-5a9c-4e5d-ab03-0f4003c6d7ba ro quiet splash i8042.reset=1 
i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DZCN18WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 15ARE05
dmi.modalias: 
dmi:bvnLENOVO:bvrDZCN18WW:bd04/02/2020:svnLENOVO:pn81W4:pvrIdeaPad315ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad315ARE05:
dmi.product.family: IdeaPad 3 15ARE05
dmi.product.name: 81W4
dmi.product.sku: LENOVO_MT_81W4_BU_idea_FM_IdeaPad 3 15ARE05
dmi.product.version: IdeaPad 3 15ARE05
dmi.sys.vendor: LENOVO

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


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

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

Title:
  ubuntu 20.4 on lenovo ideapad3 doesn't see touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.4 on lenovo ideapad3 doesn't see touchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  4 01:18:31 2020
  InstallationDate: Installed on 2020-07-23 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81W4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=f6d8bd72-5a9c-4e5d-ab03-0f4003c6d7ba ro quiet splash i8042.reset=1 
i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DZCN18WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDZCN18WW:bd04/02/2020:svnLENOVO:pn81W4:pvrIdeaPad315ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad315ARE05:
  dmi.product.family: IdeaPad 3 15ARE05
  dmi.product.name: 81W4
  dmi.product.sku: LENOVO_MT_81W4_BU_idea_FM_IdeaPad 3 15ARE05
  dmi.product.version: IdeaPad 3 15ARE05
  dmi.sys.vendor: LENOVO

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

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


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

2020-08-03 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  ubuntu 20.4 on lenovo ideapad3 doesn't see touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.4 on lenovo ideapad3 doesn't see touchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  4 01:18:31 2020
  InstallationDate: Installed on 2020-07-23 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81W4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=f6d8bd72-5a9c-4e5d-ab03-0f4003c6d7ba ro quiet splash i8042.reset=1 
i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DZCN18WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDZCN18WW:bd04/02/2020:svnLENOVO:pn81W4:pvrIdeaPad315ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad315ARE05:
  dmi.product.family: IdeaPad 3 15ARE05
  dmi.product.name: 81W4
  dmi.product.sku: LENOVO_MT_81W4_BU_idea_FM_IdeaPad 3 15ARE05
  dmi.product.version: IdeaPad 3 15ARE05
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3

2020-08-03 Thread Andy Whitcroft
Does this system have wireguard or zfs tooling installed?

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

Title:
  ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-
  image-gke 5.3

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

Bug description:
  Hi,

  as summary says, today I got an upgrade to gke which broke my 18.04
  oem install (dell xps 13)...

  After upgrade i had

  ii  linux-image-4.15.0-1093-oem   4.15.0-1093.103 amd64   
Signed kernel image oem
  ii  linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64   
Signed kernel image GKE

  and had to use advanced boot options to get back to a usable setup...

  
  maybe useful:

  dpkg -l linux* | grep  ^ii
  ii  linux-base   4.5ubuntu1.2  all  
Linux image base package
  ii  linux-firmware   1.173.19  all  
Firmware for Linux kernel drivers
  ii  linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-4.15.0-1091-oem4.15.0-1091.101   amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-4.15.0-1093-oem4.15.0-1093.103   amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-oem4.15.0.1093.96amd64
OEM Linux kernel headers
  ii  linux-image-4.15.0-1030-oem  4.15.0-1030.35amd64
Signed kernel image oem
  ii  linux-image-4.15.0-1091-oem  4.15.0-1091.101   amd64
Signed kernel image oem
  ii  linux-image-4.15.0-1093-oem  4.15.0-1093.103   amd64
Signed kernel image oem
  ii  linux-image-5.3.0-1030-gke   5.3.0-1030.32~18.04.1 amd64
Signed kernel image GKE
  ii  linux-image-oem  4.15.0.1093.96amd64
OEM Linux kernel image
  ii  linux-libc-dev:amd64 4.15.0-112.113amd64
Linux Kernel Headers for development
  ii  linux-libc-dev:i386  4.15.0-112.113i386 
Linux Kernel Headers for development
  ii  linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1091-oem4.15.0-1091.101   amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1093-oem4.15.0-1093.103   amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64
Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP
  ii  linux-oem4.15.0.1093.96amd64
Complete OEM Linux kernel and headers
  ii  linux-oem-headers-4.15.0-10304.15.0-1030.35all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10904.15.0-1090.100   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10914.15.0-1091.101   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10934.15.0-1093.103   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-sound-base 1.0.25+dfsg-0ubuntu5  all  
base package for ALSA and OSS sound systems

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

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


[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic

2020-08-03 Thread Eko Adinugroho
** Information type changed from Public to Public Security

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1878480] Re: Centrino Wireless-N 1000 [Condor Peak]

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

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

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

Title:
  Centrino Wireless-N 1000 [Condor Peak]

Status in linux package in Ubuntu:
  Expired

Bug description:
  After upgrade to 20.04 my wireless starts to be very unstable, it goes
  from 65mbs to 1mbs. I need to reenable wirless

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-generic 5.4.0.29.34
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  miguel 2846 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 20:57:07 2020
  HibernationDevice: RESUME=UUID=0f71c458-758c-439d-9dd0-b7ddcd620218
  MachineType: Alienware M14xR1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=fcba8370-4563-4d59-8a53-f1a70ebb8e1d ro quiet splash 
nouveau.blacklist=1 nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2011
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.name: M14xR1
  dmi.board.vendor: Alienware
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd12/24/2011:svnAlienware:pnM14xR1:pvrA08:rvnAlienware:rnM14xR1:rvrA08:cvnAlienware:ct8:cvrA08:
  dmi.product.family: 103C_5335KV
  dmi.product.name: M14xR1
  dmi.product.sku: xxx123x#ABA
  dmi.product.version: A08
  dmi.sys.vendor: Alienware

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

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


[Kernel-packages] [Bug 1879680] Re: Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p

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

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

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

Title:
  Elantech PS/2 [ACPI/ETD0449] Touchpad not detected on Wortmann 1460p

Status in linux package in Ubuntu:
  Expired

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 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)

2020-08-03 Thread You-Sheng Yang
Still have issues with mainline kernel v5.8. Stay tuned.

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

Title:
  Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)

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

Bug description:
  Device from /sys/kernel/debug/usb/devices:

  T:  Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0032 Rev= 0.00

  Fix available upstream at:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875e16759005e3bdaa84eb2741281f37ba35b886

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

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


[Kernel-packages] [Bug 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)

2020-08-03 Thread You-Sheng Yang
** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Incomplete

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)

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

Bug description:
  Device from /sys/kernel/debug/usb/devices:

  T:  Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#=  3 Spd=12   MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0032 Rev= 0.00

  Fix available upstream at:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875e16759005e3bdaa84eb2741281f37ba35b886

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

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


[Kernel-packages] [Bug 1890231] [NEW] alsa: should not load sof driver if the internal mic connects to the codec

2020-08-03 Thread Hui Wang
Public bug reported:

This is for tracking purpose.

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

** Affects: linux-oem-5.6 (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Critical
 Status: In Progress


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

** Changed in: linux-oem-5.6 (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Importance: Undecided => Critical

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

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

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

** Summary changed:

- alsa: should not load sof driver if there the internal mic connects to the 
codec
+ alsa: should not load sof driver if the internal mic connects to the codec

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

Title:
  alsa: should not load sof driver if the internal mic connects to the
  codec

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

Bug description:
  This is for tracking purpose.

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

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


[Kernel-packages] [Bug 1879017] Re: dd caused systemd-udevd call trace

2020-08-03 Thread js1
Happening again on 5.4.0-42-generic

Aug  3 22:29:06 quad kernel: [ 4351.386094]   Tainted: P  IOE 
5.4.0-42-generic #46-Ubuntu
Aug  3 22:29:06 quad kernel: [ 4351.386096] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug  3 22:29:06 quad kernel: [ 4351.386098] systemd-udevd   D0  2999  1 
0x4124
Aug  3 22:29:06 quad kernel: [ 4351.386101] Call Trace:
Aug  3 22:29:06 quad kernel: [ 4351.386112]  __schedule+0x2e3/0x740
Aug  3 22:29:06 quad kernel: [ 4351.386115]  schedule+0x42/0xb0
Aug  3 22:29:06 quad kernel: [ 4351.386117]  schedule_preempt_disabled+0xe/0x10
Aug  3 22:29:06 quad kernel: [ 4351.386119]  __mutex_lock.isra.0+0x182/0x4f0
Aug  3 22:29:06 quad kernel: [ 4351.386124]  ? exact_lock+0x11/0x20
Aug  3 22:29:06 quad kernel: [ 4351.386130]  __mutex_lock_slowpath+0x13/0x20
Aug  3 22:29:06 quad kernel: [ 4351.386131]  mutex_lock+0x2e/0x40
Aug  3 22:29:06 quad kernel: [ 4351.386135]  __blkdev_get+0x78/0x550
Aug  3 22:29:06 quad kernel: [ 4351.386136]  blkdev_get+0x3d/0x140
Aug  3 22:29:06 quad kernel: [ 4351.386138]  ? blkdev_get_by_dev+0x50/0x50
Aug  3 22:29:06 quad kernel: [ 4351.386140]  blkdev_open+0x8f/0xa0
Aug  3 22:29:06 quad kernel: [ 4351.386144]  do_dentry_open+0x143/0x3a0
Aug  3 22:29:06 quad kernel: [ 4351.386145]  vfs_open+0x2d/0x30
Aug  3 22:29:06 quad kernel: [ 4351.386149]  do_last+0x194/0x900
Aug  3 22:29:06 quad kernel: [ 4351.386151]  path_openat+0x8d/0x290
Aug  3 22:29:06 quad kernel: [ 4351.386154]  do_filp_open+0x91/0x100
Aug  3 22:29:06 quad kernel: [ 4351.386157]  ? __alloc_fd+0x46/0x150
Aug  3 22:29:06 quad kernel: [ 4351.386159]  do_sys_open+0x17e/0x290
Aug  3 22:29:06 quad kernel: [ 4351.386161]  __x64_sys_openat+0x20/0x30
Aug  3 22:29:06 quad kernel: [ 4351.386165]  do_syscall_64+0x57/0x190
Aug  3 22:29:06 quad kernel: [ 4351.386168]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug  3 22:29:06 quad kernel: [ 4351.386170] RIP: 0033:0x7fe7ba478d1b
Aug  3 22:29:06 quad kernel: [ 4351.386176] Code: Bad RIP value.
Aug  3 22:29:06 quad kernel: [ 4351.386177] RSP: 002b:7fff7271b090 EFLAGS: 
0246 ORIG_RAX: 0101
Aug  3 22:29:06 quad kernel: [ 4351.386179] RAX: ffda RBX: 
7fff7271b1a0 RCX: 7fe7ba478d1b
Aug  3 22:29:06 quad kernel: [ 4351.386180] RDX: 000a0800 RSI: 
562de7371e90 RDI: ff9c
Aug  3 22:29:06 quad kernel: [ 4351.386181] RBP: 562de7371e90 R08: 
562de64740c0 R09: 
Aug  3 22:29:06 quad kernel: [ 4351.386182] R10:  R11: 
0246 R12: 000a0800
Aug  3 22:29:06 quad kernel: [ 4351.386183] R13: 562de7518880 R14: 
7fff7271b168 R15: 0001

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

Title:
  dd caused systemd-udevd call trace

Status in linux package in Ubuntu:
  Expired

Bug description:
  Using dd to copy an image onto sdcard seems to cause a kernel stack
  trace.  dd seems to hang.

  [ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 
seconds.
  [ 3747.220652]   Tainted: P  IOE 5.4.0-29-generic #33-Ubuntu
  [ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.   
 
  [ 3747.220656] systemd-udevd   D0  2451  1 0x4124
  [ 3747.220660] Call Trace:
  [ 3747.220670]  __schedule+0x2e3/0x740
  [ 3747.220673]  schedule+0x42/0xb0
  [ 3747.220675]  schedule_preempt_disabled+0xe/0x10
  [ 3747.220678]  __mutex_lock.isra.0+0x182/0x4f0
  [ 3747.220683]  ? exact_lock+0x11/0x20
  [ 3747.220685]  __mutex_lock_slowpath+0x13/0x20
  [ 3747.220687]  mutex_lock+0x2e/0x40
  [ 3747.220692]  __blkdev_get+0x78/0x550
  [ 3747.220694]  blkdev_get+0x3d/0x140
  [ 3747.220697]  ? blkdev_get_by_dev+0x50/0x50
  [ 3747.220699]  blkdev_open+0x8f/0xa0
  [ 3747.220704]  do_dentry_open+0x143/0x3a0
  [ 3747.220706]  vfs_open+0x2d/0x30
  [ 3747.220710]  do_last+0x194/0x900
  [ 3747.220713]  path_openat+0x8d/0x290
  [ 3747.220716]  do_filp_open+0x91/0x100
  [ 3747.220720]  ? __alloc_fd+0x46/0x150
  [ 3747.220722]  do_sys_open+0x17e/0x290
  [ 3747.220724]  __x64_sys_openat+0x20/0x30
  [ 3747.220729]  do_syscall_64+0x57/0x190
  [ 3747.220735]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 3747.220738] RIP: 0033:0x7f18e48a1d1b
  [ 3747.220745] Code: Bad RIP value.
  [ 3747.220746] RSP: 002b:7ffd19e936a0 EFLAGS: 0246 ORIG_RAX: 
0101
  [ 3747.220748] RAX: ffda RBX: 7ffd19e937b0 RCX: 
7f18e48a1d1b
  [ 3747.220749] RDX: 000a0800 RSI: 558d7f09f470 RDI: 
ff9c
  [ 3747.220750] RBP: 558d7f09f470 R08: 558d7d4740c0 R09: 

  [ 3747.220751] R10:  R11: 0246 R12: 
000a0800
  [ 3747.220752] R13: 558d7f0b2920 R14: 7ffd19e93778 R15: 

[Kernel-packages] [Bug 1882167] Re: ubuntu_zfs_xfs_generic / ubuntu_xftests_* failed to build on X-4.4

2020-08-03 Thread Po-Hsu Lin
Fix applied upstream:
https://lore.kernel.org/linux-fscrypt/20200803163434.GA1057@sol.localdomain/

Workarouds reverted:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=13720efa8789e63a65b6ea9251ce70b0df500d3a

Thus I am closing this bug.

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  ubuntu_zfs_xfs_generic / ubuntu_xftests_* failed to build on X-4.4

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The test compilation will fail with:
    cc: error: unrecognized command line option '-Wimplicit-fallthrough'

  This build issue does not exist with 4.4.0-180 + gcc
  5.4.0-6ubuntu1~16.04.12

  Please find attachment for the full build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-181-generic 4.4.0-181.211
  ProcVersionSignature: Ubuntu 4.4.0-181.211-generic 4.4.223
  Uname: Linux 4.4.0-181-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Jun  4 22:56:00 2020
  HibernationDevice: RESUME=/dev/mapper/mpatha1
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kernel01_vg-kernel01_lv crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-181-generic N/A
   linux-backports-modules-4.4.0-181-generic  N/A
   linux-firmware 1.157.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882167/+subscriptions

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


[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic

2020-08-03 Thread Eko Adinugroho
** 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/1890223

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1890223] Lsusb-t.txt

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1890223] Lspci-vt.txt

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1890223] Lsusb-v.txt

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2020-08-03 Thread Eko Adinugroho
apport information

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.82
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A3
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic

2020-08-03 Thread Eko Adinugroho
apport information

** Tags added: apport-collected

** Description changed:

- I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version
- 5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi
- Adapter cannot detect so I use bluetooth tethering to connect to the
- internet. I think the problem in driver package. I try to install driver
- with find information from many site such as documentation or
- stackoverflow but still failed. Can you help me to resolve this.
- Thankyou very much and I appreciated for it.
+ I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ IwConfig:
+  lono wireless extensions.
+  
+  bnep0 no wireless extensions.
+  
+  eno1  no wireless extensions.
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
+  Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: HP HP Pavilion Notebook
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-42-generic N/A
+  linux-backports-modules-5.4.0-42-generic  N/A
+  linux-firmware1.187.2
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 08/18/2016
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.82
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: 80A3
+ dmi.board.vendor: HP
+ dmi.board.version: 91.1E
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnInsyde:bvrF.82:bd08/18/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A3:rvr91.1E: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: P3V63PA#AR6
+ dmi.product.version: Type1ProductConfigId
+ dmi.sys.vendor: HP

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version 
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi Adapter 
cannot detect so I use bluetooth tethering to connect to the internet. I think 
the problem in driver package. I try to install driver with find information 
from many site such as documentation or stackoverflow but still failed. Can you 
help me to resolve this. Thankyou very much and I appreciated for it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekoadin   32543 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IwConfig:
   lono wireless extensions.
   
   bnep0 no wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=aba06a00-074b-4a90-8880-854f890802cf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1742089] Re: Third unkown screen

2020-08-03 Thread Daniel van Vugt
The log shows the "unknown" VGA monitor is connected to the modeset
driver, so that's the xorg-server package...

[31.457] (II) modeset(G0): EDID for output VGA-1-1
[31.457] (II) modeset(G0): Printing probed modes for output VGA-1-1
[31.457] (II) modeset(G0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[31.457] (II) modeset(G0): Modeline "800x600"x60.3   40.00  800 840 968 
1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[31.457] (II) modeset(G0): Modeline "800x600"x56.2   36.00  800 824 896 
1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[31.457] (II) modeset(G0): Modeline "848x480"x60.0   33.75  848 864 976 
1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[31.457] (II) modeset(G0): Modeline "640x480"x59.9   25.18  640 656 752 800 
 480 490 492 525 -hsync -vsync (31.5 kHz e)

** Package changed: nvidia-graphics-drivers-440 (Ubuntu) => xorg-server
(Ubuntu)

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

Title:
  Third unkown screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After updating a third unknown screen appeared, apparently connected
  to the vga port according to xrandr

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan  9 09:35:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-104-generic, x86_64: installed
   nvidia-384, 384.90, 4.4.0-104-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
  InstallationDate: Installed on 2017-01-03 (370 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=21e3988f-d702-4bae-b6e3-54620f292e02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0T3YTY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1742089/+subscriptions

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


[Kernel-packages] [Bug 1890220] Re: ASoC:amd:renoir: the dmic can't record sound after suspend and resume

2020-08-03 Thread Hui Wang
** Description changed:

- This bug is for tracking purpose.
+ [Impact]
+ We have backported the amd renoir audio driver to oem-5.6 and focal
+ kernel, recently we found if the dmic is working and we suspend and
+ resume, the dmic can't record the sound after resume.
+ 
+ [Fix]
+ After resuming, the driver needs to restore 2 more registers, then the
+ dmic could record the sound.
+ 
+ [Test Case]
+ Boot the kernel with this patch, open the sound-setting and run suspend
+ and resume, then use arecord to record the sound, verify the sound is
+ successfully recorded by aplaying it.
+ 
+ [Regression Risk]
+ Low, this patch is verified on the amd renoir machine, and this patch
+ got ack from AMD engineer.

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

Title:
  ASoC:amd:renoir:  the dmic can't record sound after suspend and resume

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

Bug description:
  [Impact]
  We have backported the amd renoir audio driver to oem-5.6 and focal
  kernel, recently we found if the dmic is working and we suspend and
  resume, the dmic can't record the sound after resume.

  [Fix]
  After resuming, the driver needs to restore 2 more registers, then the
  dmic could record the sound.

  [Test Case]
  Boot the kernel with this patch, open the sound-setting and run suspend
  and resume, then use arecord to record the sound, verify the sound is
  successfully recorded by aplaying it.

  [Regression Risk]
  Low, this patch is verified on the amd renoir machine, and this patch
  got ack from AMD engineer.

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

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


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

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

apport-collect 1890223

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

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

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

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

** Tags added: focal

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version
  5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi
  Adapter cannot detect so I use bluetooth tethering to connect to the
  internet. I think the problem in driver package. I try to install
  driver with find information from many site such as documentation or
  stackoverflow but still failed. Can you help me to resolve this.
  Thankyou very much and I appreciated for it.

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

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


[Kernel-packages] [Bug 1890223] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic

2020-08-03 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1890223

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

A Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version
  5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi
  Adapter cannot detect so I use bluetooth tethering to connect to the
  internet. I think the problem in driver package. I try to install
  driver with find information from many site such as documentation or
  stackoverflow but still failed. Can you help me to resolve this.
  Thankyou very much and I appreciated for it.

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

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


[Kernel-packages] [Bug 1890223] [NEW] No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-42-generic

2020-08-03 Thread Eko Adinugroho
Public bug reported:

I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version
5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi
Adapter cannot detect so I use bluetooth tethering to connect to the
internet. I think the problem in driver package. I try to install driver
with find information from many site such as documentation or
stackoverflow but still failed. Can you help me to resolve this.
Thankyou very much and I appreciated for it.

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

** Summary changed:

- No Wi-Fi Adapter Found
+ No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 
5.4.0-42-generic

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

Title:
  No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to
  version 5.4.0-42-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I use Ubuntu 20.04 in HP laptop and updated Linux kernel to version
  5.4.0-42-generic after that Wifi Menu can't find on Settings and Wifi
  Adapter cannot detect so I use bluetooth tethering to connect to the
  internet. I think the problem in driver package. I try to install
  driver with find information from many site such as documentation or
  stackoverflow but still failed. Can you help me to resolve this.
  Thankyou very much and I appreciated for it.

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

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


[Kernel-packages] [Bug 1890222] [NEW] Enlarge hisi_sec2 capability

2020-08-03 Thread Ike Panhc
Public bug reported:

[Impact]
Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress 
test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 
20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge 
the capability. 

[Fix]
https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg43093.html

[Test]
$ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded
$ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz 
--times --af-alg 0
$ echo $?

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
 Status: In Progress

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
   Status: In Progress

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  Enlarge hisi_sec2 capability

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress 
test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 
20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge 
the capability. 

  [Fix]
  https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg43093.html

  [Test]
  $ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded
  $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz 
--times --af-alg 0
  $ echo $?

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

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

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


[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

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

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   af_alg_accept+0x81/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  general protection fault:  [#1] SMP PTI
  ...
  RIP: 0010:__release_sock+0x54/0xe0
  ...
  Call Trace:
   release_sock+0x30/0xa0
   af_alg_accept+0x122/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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


[Kernel-packages] [Bug 1880519] Re: System stops responding while entering S3 with SD card installed

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  System stops responding while entering S3 with SD card installed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem 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:
  Fix Committed
Status in linux source package in Eoan:
  Won't Fix
Status in linux-oem source package in Eoan:
  Invalid
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Triaged
Status in linux-oem source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]
  The system stops responding while entering S3, screen will be lit up if 
touchpad is triggered by finger. Cursor could be seen with black background, 
but system is not responding to any input.

  [Fix]
  b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM
  f0c472a6da51 xhci: Return if xHCI doesn't support LPM

  [Fix] 

 
  Patchset[1] for fix this issue currently landed in upstream,  

 
  so we backported them:

 


 
  [1]:  

 
  b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM   

 
  f0c472a6da51 xhci: Return if xHCI doesn't support LPM 

 


 
  [Test]

 
  With the above patch applied, run:

 
  sudo fwts --s3-sleep-delay=30 --s3-multiple=30 -p s3  

 


 
  Can passed 30 times.  

 


 
  [Regression Potential]

 
  Low, the patch is just like a safeguard,  

 
  doesn't really change any behavior.

  [Reproduce Steps]
  1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso
  2. Upgrade kernel to 4.15.0-1080-oem
  3. Boot the system with 4.15.0-1080-oem kernel
  4. Insert SD card
  5. Suspend the system to S3

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

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

[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  Computer is frozen after suspend

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems with ATA drives freeze during suspend

  [Fix]
  Avoid circular sync dependency by using async cookie.

  [Test]
  User reports positive feedback.

  [Regression Potential]
  Low. This patch makes synchronize more targeted, prevents many potential
  freeze.

  === Original Bug Report ===
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1890220] [NEW] ASoC:amd:renoir: the dmic can't record sound after suspend and resume

2020-08-03 Thread Hui Wang
Public bug reported:

This bug is for tracking purpose.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: Fix Released

** Affects: linux-oem-5.6 (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: linux (Ubuntu Focal)
 Importance: Critical
 Status: Triaged

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Critical
 Status: Triaged

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

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

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Importance: Undecided => Critical

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

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: New => 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/1890220

Title:
  ASoC:amd:renoir:  the dmic can't record sound after suspend and resume

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

Bug description:
  This bug is for tracking purpose.

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

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


[Kernel-packages] [Bug 1864669] Re: overlayfs regression - internal getxattr operations without sepolicy checking

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux-aws (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  overlayfs regression - internal getxattr operations without sepolicy
  checking

Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-4.15 source package in Xenial:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure-4.15 source package in Bionic:
  Fix Released
Status in linux-aws source package in Eoan:
  Fix Committed
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-azure-4.15 source package in Eoan:
  Invalid
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Bug description and repro:

  Run the following commands on host instances:

  Prepare the overlayfs directories:
  $ cd /tmp
  $ mkdir -p base/dir1/dir2 upper olwork merged
  $ touch base/dir1/dir2/file
  $ chown -R 10:10 base upper olwork merged

  Verify that the directory is owned by user 10:
  $ ls -al merged/ 
  total 8
  drwxr-xr-x  2 10 10 4096 Nov  1 07:08 .
  drwxrwxrwt 16 root   root   4096 Nov  1 07:08 ..

  We use lxc-usernsexec to start a new shell as user 10.
  $ lxc-usernsexec -m b:0:10:1 -- /bin/bash
  $$ ls -al merged/
  total 8
  drwxr-xr-x  2 root   root4096 Nov  1 07:08 .
  drwxrwxrwt 16 nobody nogroup 4096 Nov  1 07:08 ..

  Notice that the ownership of . and .. has changed because the new shell is 
running as the remapped user.
  Now, mount the overlayfs as an unprivileged user in the new shell. This is 
the key to trigger the bug.
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2/file 
  -rw-r--r-- 1 root root 0 Nov  1 07:09 merged/dir1/dir2/file

  We can see the file in the base layer from the mount directory. Now trigger 
the bug:
  $$ rm -rf merged/dir1/dir2/
  $$ mkdir merged/dir1/dir2
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 2 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..

  File does not show up in the newly created dir2 as expected. But it will 
reappear after we remount the filesystem (or any other means that might evict 
the cached dentry, such as attempt to delete the parent directory):
  $$ umount merged
  $$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
  $$ ls -al merged/dir1/dir2
  total 12
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 .
  drwxr-xr-x 1 root root 4096 Nov  1 07:10 ..
  -rw-r--r-- 1 root root0 Nov  1 07:09 file
  $$ exit
  $

  This is a recent kernel regression. I tried the above step on an old
  kernel (4.4.0-1072-aws) but cannot reproduce.


  I looked up linux source code and figured out where the "regression" is 
coming from. The issue lies in how overlayfs checks the "opaque" flag from the 
underlying upper-level filesystem. It checks the "trusted.overlay.opaque" 
extended attribute to decide whether to hide the directory content from the 
lower level. The logic are different in 4.4 and 4.15 kernel.
  In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
int res;
char val;
struct inode *inode = dentry->d_inode;

if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
return false;

res = inode->i_op->getxattr(dentry, OVL_XATTR_OPAQUE, , 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  In 4.15: 
https://elixir.bootlin.com/linux/v4.15/source/fs/overlayfs/util.c#L349
  static bool ovl_is_opaquedir(struct dentry *dentry)
  {
return ovl_check_dir_xattr(dentry, OVL_XATTR_OPAQUE);
  }

  bool ovl_check_dir_xattr(struct dentry *dentry, const char *name)
  {
int res;
char val;

if (!d_is_dir(dentry))
return false;

res = vfs_getxattr(dentry, name, , 1);
if (res == 1 && val == 'y')
return true;

return false;
  }

  The 4.4 version simply uses the internal i_node callback 
inode->i_op->getxattr from the host filesystem, which doesn't perform any 
permission check. While the 4.15 version calls the VFS interface vfs_getxattr 
that performs bunch of permission checks before the calling the internal 
insecure callback __vfs_getxattr:
  See 

[Kernel-packages] [Bug 1881346] Re: linux-kvm should support nftables

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux-kvm (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

Title:
  linux-kvm should support nftables

Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  LXD can't use nftables on the latest Focal/linux-kvm kernel, since
  nftables support is off (contrary to generic, where nftables is
  enabled).

  [Fix]

  Apply the attached config change

  [Regression potential]

  Low, we are enabling CONFIG_NF* options widely used in generic since a
  while.

  Boot performance wise, the config change has been tested on a isolated
  KVM instance, iterating over 100 reboots and we didn't notice any
  evident regression:

  5.4.0-1018-kvm 20.04 focal (CPUS=1):

  kernel: 2.16371, user: 7.58647, total: 9.75018
  kernel_std: .03405, user_std: .33445, total_std: .33524

  5.4.0-1018-kvm~nft 20.04 focal (CPUS=1):

  kernel: 2.15961, user: 7.63694, total: 9.79655
  kernel_std: .03420, user_std: .36585, total_std: .37049

  ---
  LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and 
groovy:

  - groovy: 5.4.0.1009.9
  - focal: 5.4.0-1011.11
  - eoan: 5.3.0.1017.19

  LXD detects that nft tools are available, and nft tables can be
  listed; however, trying to create a new table or rule fails.

  Because of this, LXD has to fall back on xtables, which is a legacy
  package.

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

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


[Kernel-packages] [Bug 1885023] Re: Focal update: v5.4.48 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.48 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.48 upstream stable release
     from git://git.kernel.org/

  ACPI: GED: use correct trigger type field in _Exx / _Lxx handling
  drm/amdgpu: fix and cleanup amdgpu_gem_object_close v4
  ath10k: Fix the race condition in firmware dump work queue
  drm: bridge: adv7511: Extend list of audio sample rates
  media: staging: imgu: do not hold spinlock during freeing mmu page table
  media: imx: imx7-mipi-csis: Cleanup and fix subdev pad format handling
  crypto: ccp -- don't "select" CONFIG_DMADEVICES
  media: vicodec: Fix error codes in probe function
  media: si2157: Better check for running tuner in init
  objtool: Ignore empty alternatives
  spi: spi-mem: Fix Dual/Quad modes on Octal-capable devices
  drm/amdgpu: Init data to avoid oops while reading pp_num_states.
  arm64/kernel: Fix range on invalidating dcache for boot page tables
  libbpf: Fix memory leak and possible double-free in hashmap__clear
  spi: pxa2xx: Apply CS clk quirk to BXT
  x86,smap: Fix smap_{save,restore}() alternatives
  sched/fair: Refill bandwidth before scaling
  net: atlantic: make hw_get_regs optional
  net: ena: fix error returning in ena_com_get_hash_function()
  efi/libstub/x86: Work around LLVM ELF quirk build regression
  ath10k: remove the max_sched_scan_reqs value
  arm64: cacheflush: Fix KGDB trap detection
  media: staging: ipu3: Fix stale list entries on parameter queue failure
  rtw88: fix an issue about leak system resources
  spi: dw: Zero DMA Tx and Rx configurations on stack
  ACPICA: Dispatcher: add status checks
  block: alloc map and request for new hardware queue
  arm64: insn: Fix two bugs in encoding 32-bit logical immediates
  block: reset mapping if failed to update hardware queue count
  drm: rcar-du: Set primary plane zpos immutably at initializing
  lockdown: Allow unprivileged users to see lockdown status
  ixgbe: Fix XDP redirect on archs with PAGE_SIZE above 4K
  platform/x86: dell-laptop: don't register micmute LED if there is no token
  MIPS: Loongson: Build ATI Radeon GPU driver as module
  Bluetooth: Add SCO fallback for invalid LMP parameters error
  kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb
  kgdb: Prevent infinite recursive entries to the debugger
  pmu/smmuv3: Clear IRQ affinity hint on device removal
  ACPI/IORT: Fix PMCG node single ID mapping handling
  mips: Fix cpu_has_mips64r1/2 activation for MIPS32 CPUs
  spi: dw: Enable interrupts in accordance with DMA xfer mode
  clocksource: dw_apb_timer: Make CPU-affiliation being optional
  clocksource: dw_apb_timer_of: Fix missing clockevent timers
  media: dvbdev: Fix tuner->demod media controller link
  btrfs: account for trans_block_rsv in may_commit_transaction
  btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums
  ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE
  batman-adv: Revert "disable ethtool link speed detection when auto 
negotiation off"
  ice: Fix memory leak
  ice: Fix for memory leaks and modify ICE_FREE_CQ_BUFS
  mmc: meson-mx-sdio: trigger a soft reset after a timeout or CRC error
  Bluetooth: btmtkuart: Improve exception handling in btmtuart_probe()
  spi: dw: Fix Rx-only DMA transfers
  x86/kvm/hyper-v: Explicitly align hcall param for kvm_hyperv_exit
  net: vmxnet3: fix possible buffer overflow caused by bad DMA value in 
vmxnet3_get_rss()
  x86: fix vmap arguments in map_irq_stack
  staging: android: ion: use vmap instead of vm_map_ram
  ath10k: fix kernel null pointer dereference
  media: staging/intel-ipu3: Implement lock for stream on/off operations
  spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource
  brcmfmac: fix wrong location to get firmware feature
  regulator: qcom-rpmh: Fix typos in pm8150 and pm8150l
  tools api fs: Make xxx__mountpoint() more scalable
  e1000: Distribute switch variables for initialization
  dt-bindings: display: mediatek: control dpi pins mode to avoid leakage
  drm/mediatek: set dpi pin mode to gpio low to avoid leakage current
  audit: fix a net reference leak in audit_send_reply()
  media: dvb: return -EREMOTEIO on i2c transfer failure.
  media: 

[Kernel-packages] [Bug 1885322] Re: Focal update: v5.4.49 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.49 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.49 upstream stable release
     from git://git.kernel.org/

  power: supply: bq24257_charger: Replace depends on REGMAP_I2C with select
  clk: sunxi: Fix incorrect usage of round_down()
  ASoC: tegra: tegra_wm8903: Support nvidia, headset property
  i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets
  ASoC: SOF: imx8: Fix randbuild error
  iio: pressure: bmp280: Tolerate IRQ before registering
  remoteproc: Fix IDR initialisation in rproc_alloc()
  clk: qcom: msm8916: Fix the address location of pll->config_reg
  ASoC: fsl_esai: Disable exception interrupt before scheduling tasklet
  backlight: lp855x: Ensure regulators are disabled on probe failure
  ARM: dts: renesas: Fix IOMMU device node names
  ASoC: davinci-mcasp: Fix dma_chan refcnt leak when getting dma type
  ARM: integrator: Add some Kconfig selections
  ARM: dts: stm32: Add missing ethernet PHY reset on AV96
  scsi: core: free sgtables in case command setup fails
  scsi: qedi: Check for buffer overflow in qedi_set_path()
  arm64: dts: meson: fixup SCP sram nodes
  ALSA: isa/wavefront: prevent out of bounds write in ioctl
  PCI: Allow pci_resize_resource() for devices on root bus
  scsi: qla2xxx: Fix issue with adapter's stopping state
  Input: edt-ft5x06 - fix get_default register write access
  powerpc/kasan: Fix stack overflow by increasing THREAD_SHIFT
  rtc: mc13xxx: fix a double-unlock issue
  iio: bmp280: fix compensation of humidity
  f2fs: report delalloc reserve as non-free in statfs for project quota
  i2c: pxa: clear all master action bits in i2c_pxa_stop_message()
  remoteproc: qcom_q6v5_mss: map/unmap mpss segments before/after use
  clk: samsung: Mark top ISP and CAM clocks on Exynos542x as critical
  usblp: poison URBs upon disconnect
  serial: 8250: Fix max baud limit in generic 8250 port
  misc: fastrpc: Fix an incomplete memory release in fastrpc_rpmsg_probe()
  misc: fastrpc: fix potential fastrpc_invoke_ctx leak
  dm mpath: switch paths in dm_blk_ioctl() code path
  arm64: dts: armada-3720-turris-mox: forbid SDR104 on SDIO for FCC purposes
  arm64: dts: armada-3720-turris-mox: fix SFP binding
  arm64: dts: juno: Fix GIC child nodes
  pinctrl: ocelot: Fix GPIO interrupt decoding on Jaguar2
  clk: renesas: cpg-mssr: Fix STBCR suspend/resume handling
  ASoC: SOF: Do nothing when DSP PM callbacks are not set
  arm64: dts: fvp: Fix GIC child nodes
  PCI: aardvark: Don't blindly enable ASPM L0s and don't write to read-only 
register
  ps3disk: use the default segment boundary
  arm64: dts: fvp/juno: Fix node address fields
  vfio/pci: fix memory leaks in alloc_perm_bits()
  coresight: tmc: Fix TMC mode read in tmc_read_prepare_etb()
  RDMA/mlx5: Add init2init as a modify command
  scsi: hisi_sas: Do not reset phy timer to wait for stray phy up
  PCI: pci-bridge-emul: Fix PCIe bit conflicts
  m68k/PCI: Fix a memory leak in an error handling path
  gpio: dwapb: Call acpi_gpiochip_free_interrupts() on GPIO chip de-registration
  usb: gadget: core: sync interrupt before unbind the udc
  powerpc/ptdump: Add _PAGE_COHERENT flag
  mfd: wm8994: Fix driver operation if loaded as modules
  scsi: cxgb3i: Fix some leaks in init_act_open()
  clk: zynqmp: fix memory leak in zynqmp_register_clocks
  scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event
  scsi: vhost: Notify TCM about the maximum sg entries supported per command
  clk: clk-flexgen: fix clock-critical handling
  IB/mlx5: Fix DEVX support for MLX5_CMD_OP_INIT2INIT_QP command
  powerpc/perf/hv-24x7: Fix inconsistent output values incase multiple hv-24x7 
events run
  nfsd: Fix svc_xprt refcnt leak when setup callback client failed
  PCI: vmd: Filter resource type bits from shadow register
  RDMA/core: Fix several reference count leaks.
  cifs: set up next DFS target before generic_ip_connect()
  ASoC: qcom: q6asm-dai: kCFI fix
  powerpc/crashkernel: Take "mem=" option into account
  pwm: img: Call pm_runtime_put() in pm_runtime_get_sync() failed case
  sparc32: mm: Don't try to free page-table pages if ctor() fails
  yam: fix possible memory leak in yam_init_driver
 

[Kernel-packages] [Bug 1885942] Re: Focal update: v5.4.50 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.50 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.50 upstream stable release
     from git://git.kernel.org/

  block/bio-integrity: don't free 'buf' if bio_integrity_add_page() failed
  enetc: Fix tx rings bitmap iteration range, irq handling
  geneve: allow changing DF behavior after creation
  ibmveth: Fix max MTU limit
  mld: fix memory leak in ipv6_mc_destroy_dev()
  mvpp2: ethtool rxtx stats fix
  net: bridge: enfore alignment for ethernet address
  net: core: reduce recursion limit value
  net: Do not clear the sock TX queue in sk_set_socket()
  net: fix memleak in register_netdevice()
  net: Fix the arp error in some cases
  net: increment xmit_recursion level in dev_direct_xmit()
  net: usb: ax88179_178a: fix packet alignment padding
  openvswitch: take into account de-fragmentation/gso_size in 
execute_check_pkt_len
  rocker: fix incorrect error handling in dma_rings_init
  rxrpc: Fix notification call on completion of discarded calls
  sctp: Don't advertise IPv4 addresses if ipv6only is set on the socket
  tcp: don't ignore ECN CWR on pure ACK
  tcp: grow window for OOO packets only for SACK flows
  tg3: driver sleeps indefinitely when EEH errors exceed eeh_max_freezes
  ip6_gre: fix use-after-free in ip6gre_tunnel_lookup()
  net: phy: Check harder for errors in get_phy_id()
  ip_tunnel: fix use-after-free in ip_tunnel_lookup()
  sch_cake: don't try to reallocate or unshare skb unconditionally
  sch_cake: don't call diffserv parsing code when it is not needed
  sch_cake: fix a few style nits
  tcp_cubic: fix spurious HYSTART_DELAY exit upon drop in min RTT
  Revert "i2c: tegra: Fix suspending in active runtime PM state"
  btrfs: fix a block group ref counter leak after failure to remove block group
  net: sched: export __netdev_watchdog_up()
  fix a braino in "sparc32: fix register window handling in genregs32_[gs]et()"
  ALSA: usb-audio: Fix potential use-after-free of streams
  binder: fix null deref of proc->context
  USB: ohci-sm501: Add missed iounmap() in remove
  usb: dwc2: Postponed gadget registration to the udc class driver
  usb: add USB_QUIRK_DELAY_INIT for Logitech C922
  USB: ehci: reopen solution for Synopsys HC bug
  usb: host: xhci-mtk: avoid runtime suspend when removing hcd
  xhci: Poll for U0 after disabling USB2 LPM
  usb: host: ehci-exynos: Fix error check in exynos_ehci_probe()
  usb: typec: tcpci_rt1711h: avoid screaming irq causing boot hangs
  ALSA: usb-audio: Add implicit feedback quirk for SSL2+.
  ALSA: usb-audio: add quirk for Denon DCD-1500RE
  ALSA: usb-audio: add quirk for Samsung USBC Headset (AKG)
  ALSA: usb-audio: Fix OOB access of mixer element list
  usb: cdns3: trace: using correct dir value
  usb: cdns3: ep0: fix the test mode set incorrectly
  usb: cdns3: ep0: add spinlock for cdns3_check_new_setup
  scsi: qla2xxx: Keep initiator ports after RSCN
  scsi: zfcp: Fix panic on ERP timeout for previously dismissed ERP action
  cifs: Fix cached_fid refcnt leak in open_shroot
  cifs/smb3: Fix data inconsistent when punch hole
  cifs/smb3: Fix data inconsistent when zero file range
  xhci: Fix incorrect EP_STATE_MASK
  xhci: Fix enumeration issue when setting max packet size for FS devices.
  xhci: Return if xHCI doesn't support LPM
  cdc-acm: Add DISABLE_ECHO quirk for Microchip/SMSC chip
  loop: replace kill_bdev with invalidate_bdev
  IB/mad: Fix use after free when destroying MAD agent
  IB/hfi1: Fix module use count flaw due to leftover module put calls
  bus: ti-sysc: Flush posted write on enable and disable
  bus: ti-sysc: Ignore clockactivity unless specified as a quirk
  ARM: OMAP2+: Fix legacy mode dss_reset
  xfrm: Fix double ESP trailer insertion in IPsec crypto offload.
  ASoC: q6asm: handle EOS correctly
  efi/tpm: Verify event log header before parsing
  efi/esrt: Fix reference count leak in esre_create_sysfs_entry.
  ASoc: q6afe: add support to get port direction
  ASoC: qcom: common: set correct directions for dailinks
  regualtor: pfuze100: correct sw1a/sw2 on pfuze3000
  RDMA/siw: Fix pointer-to-int-cast warning in siw_rx_pbl()
  ASoC: fsl_ssi: Fix bclk calculation for mono channel
  samples/bpf: 

[Kernel-packages] [Bug 1886995] Re: Focal update: v5.4.51 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.51 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.51 upstream stable release
     from git://git.kernel.org/

  io_uring: make sure async workqueue is canceled on exit
  mm: fix swap cache node allocation mask
  EDAC/amd64: Read back the scrub rate PCI register on F15h
  usbnet: smsc95xx: Fix use-after-free after removal
  sched/debug: Make sd->flags sysctl read-only
  mm/slub.c: fix corrupted freechain in deactivate_slab()
  mm/slub: fix stack overruns with SLUB_STATS
  rxrpc: Fix race between incoming ACK parser and retransmitter
  usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
  tools lib traceevent: Add append() function helper for appending strings
  tools lib traceevent: Handle __attribute__((user)) in field names
  s390/debug: avoid kernel warning on too large number of pages
  nvme-multipath: set bdi capabilities once
  nvme-multipath: fix deadlock between ana_work and scan_work
  nvme-multipath: fix deadlock due to head->lock
  nvme-multipath: fix bogus request queue reference put
  kgdb: Avoid suspicious RCU usage warning
  selftests: tpm: Use /bin/sh instead of /bin/bash
  crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
  drm/msm/dpu: fix error return code in dpu_encoder_init
  rxrpc: Fix afs large storage transmission performance drop
  RDMA/counter: Query a counter before release
  cxgb4: use unaligned conversion for fetching timestamp
  cxgb4: parse TC-U32 key values and masks natively
  cxgb4: fix endian conversions for L4 ports in filters
  cxgb4: use correct type for all-mask IP address comparison
  cxgb4: fix SGE queue dump destination buffer context
  hwmon: (max6697) Make sure the OVERT mask is set correctly
  hwmon: (acpi_power_meter) Fix potential memory leak in acpi_power_meter_add()
  thermal/drivers/mediatek: Fix bank number settings on mt8183
  thermal/drivers/rcar_gen3: Fix undefined temperature if negative
  nfsd4: fix nfsdfs reference count loop
  nfsd: fix nfsdfs inode reference count leak
  drm: sun4i: hdmi: Remove extra HPD polling
  virtio-blk: free vblk-vqs in error path of virtblk_probe()
  SMB3: Honor 'posix' flag for multiuser mounts
  nvme: fix identify error status silent ignore
  nvme: fix a crash in nvme_mpath_add_disk
  samples/vfs: avoid warning in statx override
  i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
  i2c: mlxcpld: check correct size of maximum RECV_LEN packet
  spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths
  nfsd: apply umask on fs without ACL support
  Revert "ALSA: usb-audio: Improve frames size computation"
  SMB3: Honor 'seal' flag for multiuser mounts
  SMB3: Honor persistent/resilient handle flags for multiuser mounts
  SMB3: Honor lease disabling for multiuser mounts
  SMB3: Honor 'handletimeout' flag for multiuser mounts
  cifs: Fix the target file was deleted when rename failed.
  MIPS: lantiq: xway: sysctrl: fix the GPHY clock alias names
  MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
  drm/amd/display: Only revalidate bandwidth on medium and fast updates
  drm/amdgpu: use %u rather than %d for sclk/mclk
  drm/amdgpu/atomfirmware: fix vram_info fetching for renoir
  dma-buf: Move dma_buf_release() from fops to dentry_ops
  irqchip/gic: Atomically update affinity
  mm, compaction: fully assume capture is not NULL in compact_zone_order()
  mm, compaction: make capture control handling safe wrt interrupts
  x86/resctrl: Fix memory bandwidth counter width for AMD
  dm zoned: assign max_io_len correctly
  UBUNTU: [Config] updateconfigs for EFI_CUSTOM_SSDT_OVERLAYS
  efi: Make it possible to disable efivar_ssdt entirely
  Linux 5.4.51
  UBUNTU: upstream stable to v5.4.51

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

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


[Kernel-packages] [Bug 1887853] Re: Focal update: v5.4.52 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.52 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.52 upstream stable release
     from git://git.kernel.org/

  Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race 
window"
  KVM: s390: reduce number of IO pins to 1
  spi: spi-fsl-dspi: Adding shutdown hook
  spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer
  regmap: fix alignment issue
  perf/x86/rapl: Move RAPL support to common x86 code
  perf/x86/rapl: Fix RAPL config variable bug
  UBUNTU: [Packaging] module intel-rapl-perf rename
  ARM: dts: omap4-droid4: Fix spi configuration and increase rate
  drm/ttm: Fix dma_fence refcnt leak when adding move fence
  drm/tegra: hub: Do not enable orphaned window group
  gpu: host1x: Detach driver on unregister
  drm: mcde: Fix display initialization problem
  ASoC: SOF: Intel: add PCI ID for CometLake-S
  ALSA: hda: Intel: add missing PCI IDs for ICL-H, TGL-H and EKL
  spi: spidev: fix a race between spidev_release and spidev_remove
  spi: spidev: fix a potential use-after-free in spidev_release()
  net: ethernet: mvneta: Fix Serdes configuration for SoCs without comphy
  net: ethernet: mvneta: Add 2500BaseX support for SoCs without comphy
  ixgbe: protect ring accesses with READ- and WRITE_ONCE
  i40e: protect ring accesses with READ- and WRITE_ONCE
  ibmvnic: continue to init in CRQ reset returns H_CLOSED
  powerpc/kvm/book3s64: Fix kernel crash with nested kvm & DEBUG_VIRTUAL
  iommu/vt-d: Don't apply gfx quirks to untrusted devices
  drm: panel-orientation-quirks: Add quirk for Asus T101HA panel
  drm: panel-orientation-quirks: Use generic orientation-data for Acer S1003
  s390/kasan: fix early pgm check handler execution
  cifs: update ctime and mtime during truncate
  ARM: imx6: add missing put_device() call in imx6q_suspend_init()
  scsi: mptscsih: Fix read sense data size
  usb: dwc3: pci: Fix reference count leak in dwc3_pci_resume_work
  block: release bip in a right way in error path
  nvme-rdma: assign completion vector correctly
  x86/entry: Increase entry_stack size to a full page
  sched/core: Check cpus_mask, not cpus_ptr in __set_cpus_allowed_ptr(), to fix 
mask corruption
  net: qrtr: Fix an out of bounds read qrtr_endpoint_post()
  gpio: pca953x: Override IRQ for one of the expanders on Galileo Gen 2
  gpio: pca953x: Fix GPIO resource leak on Intel Galileo Gen 2
  nl80211: don't return err unconditionally in nl80211_start_ap()
  drm/mediatek: Check plane visibility in atomic_update
  bpf, sockmap: RCU splat with redirect and strparser error or TLS
  bpf, sockmap: RCU dereferenced psock may be used outside RCU block
  netfilter: ipset: call ip_set_free() instead of kfree()
  net: mvneta: fix use of state->speed
  net: cxgb4: fix return error value in t4_prep_fw
  IB/sa: Resolv use-after-free in ib_nl_make_request()
  net: dsa: microchip: set the correct number of ports
  netfilter: conntrack: refetch conntrack after nf_conntrack_update()
  perf report TUI: Fix segmentation fault in perf_evsel__hists_browse()
  perf intel-pt: Fix recording PEBS-via-PT with registers
  perf intel-pt: Fix PEBS sample for XMM registers
  smsc95xx: check return value of smsc95xx_reset
  smsc95xx: avoid memory leak in smsc95xx_bind
  net: hns3: add a missing uninit debugfs when unload driver
  net: hns3: fix use-after-free when doing self test
  ALSA: compress: fix partial_drain completion state
  RDMA/siw: Fix reporting vendor_part_id
  arm64: kgdb: Fix single-step exception handling oops
  nbd: Fix memory leak in nbd_add_socket
  cxgb4: fix all-mask IP address comparison
  IB/mlx5: Fix 50G per lane indication
  qed: Populate nvm-file attributes while reading nvm config partition.
  net/mlx5: Fix eeprom support for SFP module
  net/mlx5e: Fix 50G per lane indication
  bnxt_en: fix NULL dereference in case SR-IOV configuration fails
  net: macb: fix wakeup test in runtime suspend/resume routines
  net: macb: mark device wake capable when "magic-packet" property present
  net: macb: fix call to pm_runtime in the suspend/resume functions
  mlxsw: spectrum_router: Remove inappropriate usage of WARN_ON()
  mlxsw: pci: Fix use-after-free in 

[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU

2020-08-03 Thread Christopher Clapp
I had a similar issue with an existing Ubuntu 16.04 LTS install on my
Dell Precision 5820 tower that has booted without issue for 2 years.
After updating the BIOS via the Ubuntu Software Center (to 1.13.0), my
computer gave only a black screen.

After clearing the BIOS, CMOS and NVRAM by removing the CMOS battery, it
would only boot to BusyBox.  BusyBox gave me a "ALERT! UUID=*** does not
exist. Dropping to a shell" error.

My OS is installed on a NVMe PCIe SSD boot drive, and I have a single SATA file 
drive.  
   
Setting the SATA Operation from to "AHCI" and Disabling the "Intel VMD 
Technology" under System Configuration in the BIOS seems to have solved the 
issue for me as well.  (@kvasko - 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/1812758

Title:
  Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell 
Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. 

  I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then
  starts throwing a bunch of error messages stating

  [33.192238] nouveau :05:00.0: DRM: base-0: timeout

  repeating over and over again. It never gets past this.

  I tried the suggestions of adding "nomodeset" in grub when I'm
  booting. It progresses a little further but hangs at "failed to start
  Ubuntu Installation Service, please run journalctl to see what
  failed". I can't see what failed as I can't get a prompt since nothing
  is installed. I don't know where to go debug from here.

  My computer boots to a black screen, what options do I have to fix it?

  Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA
  graphics

  Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes -
  Nouveau/Nvidia Driver issue 1080ti

  Ubuntu 16.04 installation blank screen

  Ubuntu 16.04 unable to boot with GTX 1080

  etc.

  However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with
  the video and was successfully able to install Ubuntu 16.04.1.
  Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM
  network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit
  the same behavior as 16.04.5 with the video.

  Just as a test, I installed 16.04.1, installed broadcom NIC (which was
  successfully detected), and upgraded from 16.04.1 --> 16.04.5 with
  apt-get and had no video issues after reboot (I didn't install the
  video drivers), in addition, after it was upgraded to 16.04.5 the
  Intel 219-LM drivers were added and would work. I have a workaround,
  but it's REALLY annoying.

  The kicker in this is that the Dell Precision 5810 worked 100%
  correctly. Put the USB boot drive in, select the drive in UEFI to boot
  and everything works out of the box.

  I'm working on gathering more logs of this issue and testing different
  kernel versions.

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

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


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

2020-08-03 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  5.8 kernel appears to break video in two groovy installs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ran apt to update/upgrade in both of my groovy distros, Lubuntu &
  U-MATE 20.10 . . . on reboot not only was my grub list broken in both
  cases but seemingly the update to the new 5.8.0-12 kernel shows splash
  logo, but "logs" to a black screen.  Display power light is "on" but
  screen is black.

  I repeated this several times in both systems . . . having to boot
  using SG2 to another distro to repair grub . . . then after I did that
  I got to grub list and went to "advanced options" and rolled back to
  the prior 5.4.0-42 kernel . . . and GUI is operational.

  I believe in TW I am running 5.7 kernel and that system has video.  I
  have an Nvidia card and I'm using "nouveau" as my driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu43
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  non-space2   1665 F pulseaudio
   /dev/snd/controlC0:  non-space2   1665 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 15:45:08 2020
  InstallationDate: Installed on 2019-06-17 (413 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: Apple Inc. MacPro5,1
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=17bcb813-d05e-4cc3-bcdf-16d283156780 ro quiet splash 
resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.189
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2019-12-13 (234 days ago)
  dmi.bios.date: 07/30/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 138.0.0.0.0
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1890211] Re: 5.8 kernel appears to break video in two groovy installs

2020-08-03 Thread Fritz Hudnut
Forgot to mention that when I'm booted in the 5.8 kernel with the black
screen, when I hit the power button the splash for both U-MATE &&
Lubuntu return to the screen before then powering down.

So we are moving from visible splash to black to visible splash to . . .
powering down.

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

Title:
  5.8 kernel appears to break video in two groovy installs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ran apt to update/upgrade in both of my groovy distros, Lubuntu &
  U-MATE 20.10 . . . on reboot not only was my grub list broken in both
  cases but seemingly the update to the new 5.8.0-12 kernel shows splash
  logo, but "logs" to a black screen.  Display power light is "on" but
  screen is black.

  I repeated this several times in both systems . . . having to boot
  using SG2 to another distro to repair grub . . . then after I did that
  I got to grub list and went to "advanced options" and rolled back to
  the prior 5.4.0-42 kernel . . . and GUI is operational.

  I believe in TW I am running 5.7 kernel and that system has video.  I
  have an Nvidia card and I'm using "nouveau" as my driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu43
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  non-space2   1665 F pulseaudio
   /dev/snd/controlC0:  non-space2   1665 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 15:45:08 2020
  InstallationDate: Installed on 2019-06-17 (413 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: Apple Inc. MacPro5,1
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=17bcb813-d05e-4cc3-bcdf-16d283156780 ro quiet splash 
resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.189
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2019-12-13 (234 days ago)
  dmi.bios.date: 07/30/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 138.0.0.0.0
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1890211] [NEW] 5.8 kernel appears to break video in two groovy installs

2020-08-03 Thread Fritz Hudnut
Public bug reported:

Ran apt to update/upgrade in both of my groovy distros, Lubuntu & U-MATE
20.10 . . . on reboot not only was my grub list broken in both cases but
seemingly the update to the new 5.8.0-12 kernel shows splash logo, but
"logs" to a black screen.  Display power light is "on" but screen is
black.

I repeated this several times in both systems . . . having to boot using
SG2 to another distro to repair grub . . . then after I did that I got
to grub list and went to "advanced options" and rolled back to the prior
5.4.0-42 kernel . . . and GUI is operational.

I believe in TW I am running 5.7 kernel and that system has video.  I
have an Nvidia card and I'm using "nouveau" as my driver.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu43
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  non-space2   1665 F pulseaudio
 /dev/snd/controlC0:  non-space2   1665 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Mon Aug  3 15:45:08 2020
InstallationDate: Installed on 2019-06-17 (413 days ago)
InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
 lono wireless extensions.
 
 enp9s0no wireless extensions.
 
 enp10s0   no wireless extensions.
MachineType: Apple Inc. MacPro5,1
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=17bcb813-d05e-4cc3-bcdf-16d283156780 ro quiet splash 
resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.189
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2019-12-13 (234 days ago)
dmi.bios.date: 07/30/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 138.0.0.0.0
dmi.board.asset.tag: 0
dmi.board.name: Mac-F221BEC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F221BEC8
dmi.modalias: 
dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
dmi.product.family: MacPro
dmi.product.name: MacPro5,1
dmi.product.sku: System SKU#
dmi.product.version: 0.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug groovy

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

Title:
  5.8 kernel appears to break video in two groovy installs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ran apt to update/upgrade in both of my groovy distros, Lubuntu &
  U-MATE 20.10 . . . on reboot not only was my grub list broken in both
  cases but seemingly the update to the new 5.8.0-12 kernel shows splash
  logo, but "logs" to a black screen.  Display power light is "on" but
  screen is black.

  I repeated this several times in both systems . . . having to boot
  using SG2 to another distro to repair grub . . . then after I did that
  I got to grub list and went to "advanced options" and rolled back to
  the prior 5.4.0-42 kernel . . . and GUI is operational.

  I believe in TW I am running 5.7 kernel and that system has video.  I
  have an Nvidia card and I'm using "nouveau" as my driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu43
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  non-space2   1665 F pulseaudio
   /dev/snd/controlC0:  non-space2   1665 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 15:45:08 2020
  InstallationDate: Installed on 2019-06-17 (413 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.
   
   enp9s0no wireless extensions.
   
   enp10s0   no wireless extensions.
  MachineType: Apple Inc. MacPro5,1
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=17bcb813-d05e-4cc3-bcdf-16d283156780 ro quiet splash 
resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.189
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to 

[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for

2020-08-03 Thread Alex B
Same messages about BAR13 and BAR15 in dmesg with Razer Blade 2016,
Ubuntu 20.04.1. Also available to 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/1426216

Title:
  pci driver messages - BAR 13: no space for

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  pci driver messages - BAR 13: no space for 

  ---uname output---
  3.18.0-12-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  Install Ubuntu 15.04 daily build running bare-metal
  After the installation following messages are seen in dmesg. 
  Not sure if these indicate a problem. Can some one look at these and confirm 
if this is problem or can be ignored ?

  Messages from dmesg log

  [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4
  [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit]
  [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit]
  [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe081ff]
  [0.714581] pci 0001:00:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0817f]
  [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 
0x3fe08180-0x3fe08183]
  [0.714595] pci 0001:01:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 
0x3b101000-0x3b101fff 64bit pref]
  [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 
0x3b102000-0x3b102fff 64bit pref]
  [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 
0x3b103000-0x3b103fff 64bit pref]
  [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0807f]
  [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 
0x3fe08080-0x3fe080ff]
  [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 
0x3fe08100-0x3fe0817f]
  [0.714611] pci 0001:02:01.0: BAR 13: no space for [io  size 0x1000]
  [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714614] pci 0001:02:08.0: BAR 13: no space for [io  size 0x1000]
  [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714618] pci 0001:02:09.0: BAR 13: no space for [io  size 0x1000]
  [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 
0x3fe08000-0x3fe08003 pref]
  [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 
0x3fe08004-0x3fe08007 pref]
  [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 
0x3fe08008-0x3fe080083fff 64bit]
  [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 
0x3fe080084000-0x3fe080087fff 64bit]
  [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 
0x3fe080088000-0x3fe080088fff 64bit]
  [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 
0x3fe080089000-0x3fe080089fff 64bit]
  [0.714685] pci 0001:03:00.0: BAR 4: no space for [io  size 0x0100]
  [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io  size 0x0100]
  [0.714688] pci 0001:03:00.1: BAR 4: no space for [io  size 0x0100]
  [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io  size 0x0100]
  [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03]

  # lspci 
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 

[Kernel-packages] [Bug 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3

2020-08-03 Thread Alexander Sack
and no i wont file the log files you asked for as my system is already
changed again etc.

i am just here after colin king asked me to file a bug ... so the ubuntu
kernel team can check and maybe fix the source of the problem.

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

Title:
  ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-
  image-gke 5.3

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

Bug description:
  Hi,

  as summary says, today I got an upgrade to gke which broke my 18.04
  oem install (dell xps 13)...

  After upgrade i had

  ii  linux-image-4.15.0-1093-oem   4.15.0-1093.103 amd64   
Signed kernel image oem
  ii  linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64   
Signed kernel image GKE

  and had to use advanced boot options to get back to a usable setup...

  
  maybe useful:

  dpkg -l linux* | grep  ^ii
  ii  linux-base   4.5ubuntu1.2  all  
Linux image base package
  ii  linux-firmware   1.173.19  all  
Firmware for Linux kernel drivers
  ii  linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-4.15.0-1091-oem4.15.0-1091.101   amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-4.15.0-1093-oem4.15.0-1093.103   amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-oem4.15.0.1093.96amd64
OEM Linux kernel headers
  ii  linux-image-4.15.0-1030-oem  4.15.0-1030.35amd64
Signed kernel image oem
  ii  linux-image-4.15.0-1091-oem  4.15.0-1091.101   amd64
Signed kernel image oem
  ii  linux-image-4.15.0-1093-oem  4.15.0-1093.103   amd64
Signed kernel image oem
  ii  linux-image-5.3.0-1030-gke   5.3.0-1030.32~18.04.1 amd64
Signed kernel image GKE
  ii  linux-image-oem  4.15.0.1093.96amd64
OEM Linux kernel image
  ii  linux-libc-dev:amd64 4.15.0-112.113amd64
Linux Kernel Headers for development
  ii  linux-libc-dev:i386  4.15.0-112.113i386 
Linux Kernel Headers for development
  ii  linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1091-oem4.15.0-1091.101   amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1093-oem4.15.0-1093.103   amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64
Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP
  ii  linux-oem4.15.0.1093.96amd64
Complete OEM Linux kernel and headers
  ii  linux-oem-headers-4.15.0-10304.15.0-1030.35all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10904.15.0-1090.100   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10914.15.0-1091.101   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10934.15.0-1093.103   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-sound-base 1.0.25+dfsg-0ubuntu5  all  
base package for ALSA and OSS sound systems

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

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


[Kernel-packages] [Bug 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3

2020-08-03 Thread Alexander Sack
well obviously it is not supposed to go for gke kernel, but what i am
reporting is that my dell xps13 with ubuntu preinstall automatically got
this kernel pushed ...  same for a coworker who got the same laptop...
so yes this bug report is about someone/something wrongfully pusing the
gke kernel to my laptop...

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

Title:
  ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-
  image-gke 5.3

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

Bug description:
  Hi,

  as summary says, today I got an upgrade to gke which broke my 18.04
  oem install (dell xps 13)...

  After upgrade i had

  ii  linux-image-4.15.0-1093-oem   4.15.0-1093.103 amd64   
Signed kernel image oem
  ii  linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64   
Signed kernel image GKE

  and had to use advanced boot options to get back to a usable setup...

  
  maybe useful:

  dpkg -l linux* | grep  ^ii
  ii  linux-base   4.5ubuntu1.2  all  
Linux image base package
  ii  linux-firmware   1.173.19  all  
Firmware for Linux kernel drivers
  ii  linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-4.15.0-1091-oem4.15.0-1091.101   amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-4.15.0-1093-oem4.15.0-1093.103   amd64
Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
  ii  linux-headers-oem4.15.0.1093.96amd64
OEM Linux kernel headers
  ii  linux-image-4.15.0-1030-oem  4.15.0-1030.35amd64
Signed kernel image oem
  ii  linux-image-4.15.0-1091-oem  4.15.0-1091.101   amd64
Signed kernel image oem
  ii  linux-image-4.15.0-1093-oem  4.15.0-1093.103   amd64
Signed kernel image oem
  ii  linux-image-5.3.0-1030-gke   5.3.0-1030.32~18.04.1 amd64
Signed kernel image GKE
  ii  linux-image-oem  4.15.0.1093.96amd64
OEM Linux kernel image
  ii  linux-libc-dev:amd64 4.15.0-112.113amd64
Linux Kernel Headers for development
  ii  linux-libc-dev:i386  4.15.0-112.113i386 
Linux Kernel Headers for development
  ii  linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1091-oem4.15.0-1091.101   amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-4.15.0-1093-oem4.15.0-1093.103   amd64
Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
  ii  linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64
Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP
  ii  linux-oem4.15.0.1093.96amd64
Complete OEM Linux kernel and headers
  ii  linux-oem-headers-4.15.0-10304.15.0-1030.35all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10904.15.0-1090.100   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10914.15.0-1091.101   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-oem-headers-4.15.0-10934.15.0-1093.103   all  
Header files related to Linux kernel version 4.15.0
  ii  linux-sound-base 1.0.25+dfsg-0ubuntu5  all  
base package for ALSA and OSS sound systems

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

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


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

2020-08-03 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  package linux-modules-5.4.0-42-generic (not installed) failed to
  install/upgrade: nie można skopiować wypakowanych danych
  "./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do
  "/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-
  new": niespodziewany koniec pliku lub strumienia

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I faced this during regular update of Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.4.0-42-generic (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  AptOrdering:
   linux-modules-5.4.0-42-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gdm1217 F pulseaudio
michal 2302 F pulseaudio
   /dev/snd/controlC0:  gdm1217 F pulseaudio
michal 2302 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Aug  3 22:02:38 2020
  DpkgHistoryLog:
   Start-Date: 2020-08-03  22:02:38
   Commandline: apt-get install -f
   Requested-By: michal (1000)
   Install: linux-modules-5.4.0-42-generic:amd64 (5.4.0-42.46, automatic)
  ErrorMessage: nie można skopiować wypakowanych danych 
"./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do 
"/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": 
niespodziewany koniec pliku lub strumienia
  InstallationDate: Installed on 2020-04-24 (101 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. H370HD3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=7235dcc7-ba5b-41ad-b76a-f18c4b11b203 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-modules-5.4.0-42-generic (not installed) failed to 
install/upgrade: nie można skopiować wypakowanych danych 
"./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do 
"/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": 
niespodziewany koniec pliku lub strumienia
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F14
  dmi.board.asset.tag: Default string
  dmi.board.name: H370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H370HD3
  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/1890194/+subscriptions

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


[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or
  available with perf

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters
  reported with lscpumf are not usable with 'perf stat -e'.

  * 'lscpumf -c' provides a list of available counters, but the
  following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC,
  DFLT_CCERROR

  * 'perf list' is also not offering these counters.

  * On the kernel side this is fixed with the following upstream
  accepted commit:

  [Fix]

  * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b
  "s390/cpum_cf: Add new extended counters for IBM z15"

  [Test Case]

  * Requires the fix/patch of the perf tool, as mentioned in the bug,
  too.

  * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in
  LPAR is needed where the counters are enabled in the activation
  profile.

  * Use 'perf list' to determine if the counters DFLT_ACCESS,
  DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed

  * Use 'perf stat -e' to enable amd make use of these counters.

  [Regression Potential]

  * The regression can be considered as low, since:

  * it's architecture specific (s390x)

  * limited to IBM z15 hardware

  * and only additional (s390x) hardware counters are defined and added.

  [Other]

  * This requires a patch to be included into the perf itself, too -
  please see bug description for more details.

  * Since this patch is upstream in kernel 5.7 it will automatically
  land in groovy.

  __

  ---Problem Description---
  ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable 
with perf stat -e

  ---uname output---
  Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = z15 8561

  ---Steps to Reproduce---
   lscpumf -c gives a list of available counters, but a few of them are not 
usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR
  perf list is also not offering these counters.

  A solution will be a backport to 20.04, and tried to made available
  for next SRU , code needed before 06-12.

  Addl Info from Dev:
  I have downloaded the following repository
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
  and checked out branch master-next.

  Both patches appended apply without warning and the compilation showed
  no error.

  For the perf tool:
  e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM 
z15

  For the s390 kernel
  d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15

  All accepted for kernel 5.7 rc1

  Please include both patches into Ubuntu 20.04

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

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


[Kernel-packages] [Bug 1884767] Re: shiftfs: fix btrfs regression

2020-08-03 Thread Kelsey Margarete Skunberg
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

Title:
  shiftfs: fix btrfs regression

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The patch
  commit cfaa482afb97e3c05d020af80b897b061109d51f
  Author: Christian Brauner 
  Date:   Tue Apr 14 22:26:53 2020 +0200

  UBUNTU: SAUCE: shiftfs: fix dentry revalidation

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

  to fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757
  regresses various btrfs + shiftfs users. Creating a btrfs subvolume,
  deleting it, and then trying to recreate it will cause EEXIST to be returned.
  It also leaves some files in a half-visible state because they are not 
revalidated
  correctly.
  Faulty behavior such as this can be reproduced via:

  btrfs subvolume create my-subvol
  btrfs subvolume delete my-subvol

  Fix: We need to revert this patch restoring the old behavior. This will 
briefly
  resurface https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757 which 
I will fix in a follow-up patch on top of this revert. We basically split the 
part that fixes https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757 
out of the revert.

  Regression Potential: Limited to shiftfs.

  Test Case: Build a kernel with fix applied and run above reproducer.

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

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


[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of bcache who manually specified a block size
     greater than the page size when creating the device
     with 'make-bcache' started to hit a kernel BUG/oops
     after kernel upgrades.  (This is not widely used.)

   * The issue has been exposed with commit ad6bf88a6c19
     ("block: fix an integer overflow in logical block size")
     because it increased the range of values accepted as
     logical block size, which used to overflow to zero,
     and thus receive a default of 512 via block layer.

   * The issue existed previously, but with fewer values
     exposed (e.g. 8k, 16k, 32k); the regression reports
     happened with larger values (512k) for RAID stripes.

  [Fix]

   * The upstream commit dcacbc1242c7 ("bcache: check and
     adjust logical block size for backing devices") checks
     the block size and adjusts it if needed, to the value
     of the underlying device's logical block size.

   * It is merged as of v5.8-rcN, and sent to v5.7 stable.

  [Test Case]

   * Run make-bcache with block size greater than page size.
     $ sudo make-bcache --bdev $DEV --block 8k

   * Expected results: bcache device registered; no BUG/oops.
   * Details steps on comment #43.

  [Regression Potential]

   * Restricted to users who specify a bcache block size
     greater than page size.

   * Regressions could theoretically manifest on bcache
     device probe/register, if the underlying device's
     logical block size for whatever triggers issues not
     seen previously with the overflow/default 512 bytes.

  [Other Info]

   * Unstable has the patch on both master/master-5.7.
   * Groovy should get it on rebase.

  [Original Bug Description]
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does 
not boot any longer. It always crashes during boot with a kernel panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf 

[Kernel-packages] [Bug 1885072] Re: [SRU][OEM-5.6/U] Fix r8117 firmware base issue

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: Invalid => Fix Committed

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

Title:
  [SRU][OEM-5.6/U] Fix r8117 firmware base issue

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

Bug description:
  [Impact]
  Realtek 8117 failed to work after loading firmware on 5.5+ kernel.

  [Fix]
  Firmware should reset ocp_base, but not on r8117. Correct the ocp_base in the 
driver.
  Then it works well.

  [Test]
  Verified on hardware, link status is OK, iperf test result is good.

  [Regression Potential]
  Low.
  Fixed issue, cherry-picked from maintainer's tree.
  Due to 5.4- kernel needs more patches, SRU the fix on 5.5+ kernel first.

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

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


[Kernel-packages] [Bug 1890194] [NEW] package linux-modules-5.4.0-42-generic (not installed) failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/modules/5.4.0-42-generic/kernel/c

2020-08-03 Thread Michal
Public bug reported:

I faced this during regular update of Ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-modules-5.4.0-42-generic (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
 linux-modules-5.4.0-42-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  gdm1217 F pulseaudio
  michal 2302 F pulseaudio
 /dev/snd/controlC0:  gdm1217 F pulseaudio
  michal 2302 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Aug  3 22:02:38 2020
DpkgHistoryLog:
 Start-Date: 2020-08-03  22:02:38
 Commandline: apt-get install -f
 Requested-By: michal (1000)
 Install: linux-modules-5.4.0-42-generic:amd64 (5.4.0-42.46, automatic)
ErrorMessage: nie można skopiować wypakowanych danych 
"./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do 
"/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": 
niespodziewany koniec pliku lub strumienia
InstallationDate: Installed on 2020-04-24 (101 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. H370HD3
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=7235dcc7-ba5b-41ad-b76a-f18c4b11b203 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-modules-5.4.0-42-generic (not installed) failed to 
install/upgrade: nie można skopiować wypakowanych danych 
"./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do 
"/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": 
niespodziewany koniec pliku lub strumienia
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F14
dmi.board.asset.tag: Default string
dmi.board.name: H370 HD3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: H370HD3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-modules-5.4.0-42-generic (not installed) failed to
  install/upgrade: nie można skopiować wypakowanych danych
  "./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do
  "/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-
  new": niespodziewany koniec pliku lub strumienia

Status in linux package in Ubuntu:
  New

Bug description:
  I faced this during regular update of Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.4.0-42-generic (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  AptOrdering:
   linux-modules-5.4.0-42-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gdm1217 F pulseaudio
michal 2302 F pulseaudio
   /dev/snd/controlC0:  gdm1217 F pulseaudio
michal 2302 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Aug  3 22:02:38 2020
  DpkgHistoryLog:
   Start-Date: 2020-08-03  22:02:38
   Commandline: apt-get install -f
   Requested-By: michal (1000)
   Install: linux-modules-5.4.0-42-generic:amd64 (5.4.0-42.46, automatic)
  ErrorMessage: nie można skopiować wypakowanych danych 
"./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do 
"/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": 
niespodziewany koniec pliku lub strumienia
  InstallationDate: Installed on 2020-04-24 

[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal
  audio devices to fail to load w/o unacceptable workaround (Lenovo
  IdeaPad 5 15IIL05)

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

Bug description:
  [Impact]
  On the machine of Lenovo IdeaPad 5 15IIL05, the audio doesn't work,
  checking the dmesg, I found the audio driver fails to initialize
  because it fails on i915 audio codec probe.

  [Fix]
  backport 3 patches from mainline kernel, move the i915 audio codec
  init earlier.

  [Test Case]
  Boot the kernel with these 3 patches, check dmesg, there is no
  i915 audio codec probe error anymore, and audio driver initializes
  successfully, and input and output audio devices all work.

  [Regression Risk]
  Low, already tested these 3 patches on a couple of LENOVO dmic
  machines (cnl and cml machines), all work as well as before.


  On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal
  speakers, headphone jack, and mic do not work at all. No audio devices
  appear in the Sound settings or in pavucontrol. By appending options
  snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can
  get audio working, but the microphone (unsuprisingly) does not work.
  Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as
  the same effect as dmic_detect=0. Attempts to fix with option
  snd_hda_intel device=generic or deveice=auto have had no effect. This
  bug does NOT manifest on 5.4.0-26-generic, the kernel version featured
  on the 20.04 live media. After installation, and updating to
  5.4.0-40-generic, the bug manifests on the next boot.

  Note that the audio hardware seems to work properly w/o workaround on
  a small (< 5%) percentage of boots, but I have been unable to
  reproduce this. With the workaround enabled, inxi -A gives

  Audio:
    Device-1: Intel Smart Sound Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.4.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jill   1374 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 13:32:58 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05:
  dmi.product.family: IdeaPad 5 15IIL05
  dmi.product.name: 81YK
  dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05
  dmi.product.version: IdeaPad 5 15IIL05
  dmi.sys.vendor: LENOVO
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YK
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [UBUNTU 20.04] smc: SMC connections hang with later-level
  implementations

Status in Ubuntu on IBM z Systems:
  In Progress
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]

  * Connections from later-level SMC (protocol) versions to an SMC-
  enabled server on Linux hang.

  * Later-level versions of SMC (although backwards-compatible) present
  a higher version number and use larger messages during the CLC
  handshake.

  * The solution to avoid such hangs is to introduce toleration for
  later version numbers, and support CLC messages of arbitrary length.

  [Fix]

  * fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 fb4f79264c0f "net/smc:
  tolerate future SMCD versions"

  [Test Case]

  * Requires two IBM z13/z13s GA2 or LinuxONE Rockhopper/Emperor systems
  with RoCE Express adapter v2(.1) for SMC-D usage.

  * One system needs to run the initial SMC-D version, the other a newer
  version.

  * Establish a connection between both system and monitor/verify if
  it's reliable or if it hangs.

  [Regression Potential]

  * The regression can be considered as medium to low:

  * Since SMC-D is a pretty special way of doing shared memory
  communications and not that wide-spread.

  * However, the code that is changed is common code.

  * But the patch is straight forward and only modifies
  /net/smc/smc_clc.c and /net/smc/smc_clc.h

  * It largely bumps limits (allows larger messages), adds a check and
  introduces toleration, rather than changing control or flow.

  [Other]

  * The above fix is currently in 'linux-next' and tagged with
  next-20200709.

  * It is still assumed that it gets accepted for 5.8.

  * However, since this is not guaranteed this SRU request is for focal
  and groovy - to make sure that no potential regressions are introduced
  in case the patch will not end up in 5.8.

  __

  Description:   smc: SMC connections hang with later-level implementations
  Symptom:   Connections from later-level SMC versions to an SMC-enabled
     server on Linux hang.
  Problem:   Later-level versions of SMC present, although backwards-
     compatible, a higher version number, and use larger messages
     during the CLC handshake.
  Solution:  Adjust for tolerating later version numbers, and support CLC
     messages of arbitrary length.
  Reproduction:  Enable a server on Linux for SMC, and connect using a later-
     level version of SMC

  Applicable for: Ubuntu 20.04

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

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


[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally

2020-08-03 Thread Andrew Cloke
** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

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

Title:
  [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the
  kernel crashes unconditionally

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * DIF and DIX support in zfcp (s390x) is broken and the kernel crashes
  unconditionally, in case one activates either zfcp DIF (data integrity
  field) or DIX (data integrity extention) and attaches any LU.

  * zfcp used to allocate/add the shost object for a HBA, before knowing
  all the HBA's capabilities. But later the shost object got patched to
  make more of the capabilities known - including the protection
  capabilities.

  * Changes that are later made to the protection capabilities don't get
  reflected in the tag-set requests and are missing.

  * Now sending I/O, scsi_mod tries to access the protection payload
  data, that isn't there, and the kernel crashes.

  [Fix]

  * The SRU request was created as pull request, so please pull starting
  at 0b38938af911 to head / 9227405ee311 from
  https://code.launchpad.net/~fheimes/+git/lp1887124

  [Test Case]

  * Have a IBM Z or LInuxONE system (ideally on LPAR) in place that is
  connected to a DS8xxx storage subsystem that supports, zfcp SCSI
  storage with DIF and DIX.

  * Have an Ubuntu Server 20.04 installed in such a LPAR system.

  * Now enable DIF (zfcp.dif=1) or DIX (zfcp.dix=1) and connect the
  system to a logical unit.

  * Monitor the system for any kernel crashes (/var/log/syslog and
  /var/log/kern.log) - look for kernel panic in scsi_queue_rq.

  [Regression Potential]

  * Even if the modifications are substantial, the regression potnetial
  can be considered as moderate.

  * This issue could be mainly tracked down to commit '737eb78e82d5'
  (made for v5.4) that made the problem more visible.

  * With the old blk queue DIF/DIX worked fine, but after scsi_mod switched to 
blk-mq (and because requests are now
  all allocated during allocation time of the blk-mq tag-set), it didn't worked 
anymore.

  * The solution is to allocate/add the shost object for a HBA after all
  of its base capabilities are known.

  * Since the situation is like this for quite a while, several places
  in the zfcp driver code (where it's assumed that the shost object was
  correctly allocated) needed to be touched.

  * This is finally the reason (as well as the fact that some parts
  depend on code that went upstream with the kernels 5.5 and 5.7) for
  this rather big patchset for fixing DIF and DIX support in zfcp.

  * On the other hand side this entire set is now upstream accepted and
  entirely included in 5.8 (and with that soon in groovy), and no
  5.4-specific (hand-crafted) backports are needed.

  * Also notice that all modifications are in the zfcp driver layer,
  hence they are s390x specific, and with that limited to
  /drivers/s390/scsi/zfcp_*

  * Finally the patches were already tested with a patched focal kernel
  with DIF/DIX/NONE, with I/O, and local/remote cable pulls - switched
  and point-to-point connected. No regressions were identified.

  [Other]

  * Alternatively the patches can also be cherry-picked from linux master with:
  git cherry-pick 92953c6e0aa7~1..e76acc519426
  git cherry-pick a3fd4bfe85fb
  git cherry-pick e05a10a05509~1..42cabdaf103b
  git cherry-pick cec9cbac5244
  git cherry-pick 978857c7e367~1..d0dff2ac98dd

  * The following lists the individual commits - just for the reason of
  completeness:

  * 92953c6e0aa77d4febcca6dd691e8192910c8a28 92953c6e0aa77 "scsi: zfcp:
  signal incomplete or error for sync exchange config/port data"

  * 7e418833e68948cb9ed15262889173b7db2960cb 7e418833e6894 "scsi: zfcp:
  diagnostics buffer caching and use for exchange port data"

  * 088210233e6fc039fd2c0bfe44b06bb94328d09e 088210233e6fc "scsi: zfcp:
  add diagnostics buffer for exchange config data"

  * a10a61e807b0a226b78e2041843cbf0521bd0c35 a10a61e807b0a "scsi: zfcp:
  support retrieval of SFP Data via Exchange Port Data"

  * 6028f7c4cd87cac13481255d7e35dd2c9207ecae 6028f7c4cd87c "scsi: zfcp:
  introduce sysfs interface for diagnostics of local SFP transceiver"

  * 8155eb0785279728b6b2e29aba2ca52d16aa526f 8155eb0785279 "scsi: zfcp:
  implicitly refresh port-data diagnostics when reading sysfs"

  * 5a2876f0d1ef26b76755749f978d46e4666013dd 5a2876f0d1ef2 "scsi: zfcp:
  introduce sysfs interface to read the local B2B-Credit"

  * 8a72db70b5ca3c3feb3ca25519e8a9516cc60cfe 8a72db70b5ca3 "scsi: zfcp:
  implicitly refresh config-data diagnostics when reading 

[Kernel-packages] [Bug 1886744] Re: Enable Quectel EG95 LTE modem [2c7c:0195]

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  Enable Quectel EG95 LTE modem [2c7c:0195]

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

Bug description:
  [Impact]
  No modems were found by `mmcli -L`

  [Fix]
  Below 2 commits are required to enable this chip.
  https://lkml.org/lkml/2020/7/7/200
  https://lkml.org/lkml/2020/7/7/199

  [Test]
  Verified on the machine with EG95 LTE modem

  [Regression Potential]
  Low, just adding IDs.

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

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


[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the
  kernel crashes unconditionally

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * DIF and DIX support in zfcp (s390x) is broken and the kernel crashes
  unconditionally, in case one activates either zfcp DIF (data integrity
  field) or DIX (data integrity extention) and attaches any LU.

  * zfcp used to allocate/add the shost object for a HBA, before knowing
  all the HBA's capabilities. But later the shost object got patched to
  make more of the capabilities known - including the protection
  capabilities.

  * Changes that are later made to the protection capabilities don't get
  reflected in the tag-set requests and are missing.

  * Now sending I/O, scsi_mod tries to access the protection payload
  data, that isn't there, and the kernel crashes.

  [Fix]

  * The SRU request was created as pull request, so please pull starting
  at 0b38938af911 to head / 9227405ee311 from
  https://code.launchpad.net/~fheimes/+git/lp1887124

  [Test Case]

  * Have a IBM Z or LInuxONE system (ideally on LPAR) in place that is
  connected to a DS8xxx storage subsystem that supports, zfcp SCSI
  storage with DIF and DIX.

  * Have an Ubuntu Server 20.04 installed in such a LPAR system.

  * Now enable DIF (zfcp.dif=1) or DIX (zfcp.dix=1) and connect the
  system to a logical unit.

  * Monitor the system for any kernel crashes (/var/log/syslog and
  /var/log/kern.log) - look for kernel panic in scsi_queue_rq.

  [Regression Potential]

  * Even if the modifications are substantial, the regression potnetial
  can be considered as moderate.

  * This issue could be mainly tracked down to commit '737eb78e82d5'
  (made for v5.4) that made the problem more visible.

  * With the old blk queue DIF/DIX worked fine, but after scsi_mod switched to 
blk-mq (and because requests are now
  all allocated during allocation time of the blk-mq tag-set), it didn't worked 
anymore.

  * The solution is to allocate/add the shost object for a HBA after all
  of its base capabilities are known.

  * Since the situation is like this for quite a while, several places
  in the zfcp driver code (where it's assumed that the shost object was
  correctly allocated) needed to be touched.

  * This is finally the reason (as well as the fact that some parts
  depend on code that went upstream with the kernels 5.5 and 5.7) for
  this rather big patchset for fixing DIF and DIX support in zfcp.

  * On the other hand side this entire set is now upstream accepted and
  entirely included in 5.8 (and with that soon in groovy), and no
  5.4-specific (hand-crafted) backports are needed.

  * Also notice that all modifications are in the zfcp driver layer,
  hence they are s390x specific, and with that limited to
  /drivers/s390/scsi/zfcp_*

  * Finally the patches were already tested with a patched focal kernel
  with DIF/DIX/NONE, with I/O, and local/remote cable pulls - switched
  and point-to-point connected. No regressions were identified.

  [Other]

  * Alternatively the patches can also be cherry-picked from linux master with:
  git cherry-pick 92953c6e0aa7~1..e76acc519426
  git cherry-pick a3fd4bfe85fb
  git cherry-pick e05a10a05509~1..42cabdaf103b
  git cherry-pick cec9cbac5244
  git cherry-pick 978857c7e367~1..d0dff2ac98dd

  * The following lists the individual commits - just for the reason of
  completeness:

  * 92953c6e0aa77d4febcca6dd691e8192910c8a28 92953c6e0aa77 "scsi: zfcp:
  signal incomplete or error for sync exchange config/port data"

  * 7e418833e68948cb9ed15262889173b7db2960cb 7e418833e6894 "scsi: zfcp:
  diagnostics buffer caching and use for exchange port data"

  * 088210233e6fc039fd2c0bfe44b06bb94328d09e 088210233e6fc "scsi: zfcp:
  add diagnostics buffer for exchange config data"

  * a10a61e807b0a226b78e2041843cbf0521bd0c35 a10a61e807b0a "scsi: zfcp:
  support retrieval of SFP Data via Exchange Port Data"

  * 6028f7c4cd87cac13481255d7e35dd2c9207ecae 6028f7c4cd87c "scsi: zfcp:
  introduce sysfs interface for diagnostics of local SFP transceiver"

  * 8155eb0785279728b6b2e29aba2ca52d16aa526f 8155eb0785279 "scsi: zfcp:
  implicitly refresh port-data diagnostics when reading sysfs"

  * 5a2876f0d1ef26b76755749f978d46e4666013dd 5a2876f0d1ef2 "scsi: zfcp:
  introduce sysfs interface to read the local B2B-Credit"

  * 8a72db70b5ca3c3feb3ca25519e8a9516cc60cfe 8a72db70b5ca3 "scsi: zfcp:
  implicitly refresh config-data diagnostics when reading sysfs"

  * 48910f8c35cfd250d806f3e03150d256f40b6d4c 48910f8c35cfd "scsi: 

[Kernel-packages] [Bug 1888560] Re: Focal update: v5.4.53 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.53 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.53 upstream stable release
     from git://git.kernel.org/

  crypto: atmel - Fix selection of CRYPTO_AUTHENC
  crypto: atmel - Fix build error of CRYPTO_AUTHENC
  net: atlantic: fix ip dst and ipv6 address filters
  net: rmnet: fix lower interface leak
  bridge: mcast: Fix MLD2 Report IPv6 payload length check
  genetlink: remove genl_bind
  ipv4: fill fl4_icmp_{type,code} in ping_v4_sendmsg
  ipv6: fib6_select_path can not use out path for nexthop objects
  ipv6: Fix use of anycast address with loopback
  l2tp: remove skb_dst_set() from l2tp_xmit_skb()
  llc: make sure applications use ARPHRD_ETHER
  net: Added pointer check for dst->ops->neigh_lookup in dst_neigh_lookup_skb
  net_sched: fix a memory leak in atm_tc_init()
  sched: consistently handle layer3 header accesses in the presence of VLANs
  tcp: fix SO_RCVLOWAT possible hangs under high mem pressure
  tcp: make sure listeners don't initialize congestion-control state
  tcp: md5: add missing memory barriers in tcp_md5_do_add()/tcp_md5_hash_key()
  tcp: md5: do not send silly options in SYNCOOKIES
  vlan: consolidate VLAN parsing code and limit max parsing depth
  tcp: md5: refine tcp_md5_do_add()/tcp_md5_hash_key() barriers
  tcp: md5: allow changing MD5 keys in all socket states
  cgroup: fix cgroup_sk_alloc() for sk_clone_lock()
  cgroup: Fix sock_cgroup_data on big-endian.
  ip: Fix SO_MARK in RST, ACK and ICMP packets
  arm64: Introduce a way to disable the 32bit vdso
  arm64: arch_timer: Allow an workaround descriptor to disable compat vdso
  arm64: arch_timer: Disable the compat vdso for cores affected by 
ARM64_WORKAROUND_1418040
  drm/msm: fix potential memleak in error branch
  drm/msm/dpu: allow initialization of encoder locks during encoder init
  drm/exynos: Properly propagate return value in drm_iommu_attach_device()
  drm/exynos: fix ref count leak in mic_pre_enable
  x86/fpu: Reset MXCSR to default in kernel_fpu_begin()
  thermal/drivers: imx: Fix missing of_node_put() at probe time
  blk-mq-debugfs: update blk_queue_flag_name[] accordingly for new flags
  m68k: nommu: register start of the memory with memblock
  m68k: mm: fix node memblock init
  dt-bindings: mailbox: zynqmp_ipi: fix unit address
  cifs: prevent truncation from long to int in wait_for_free_credits
  arm64/alternatives: use subsections for replacement sequences
  tpm_tis: extra chip->ops check on error path in tpm_tis_core_init
  gfs2: read-only mounts should grab the sd_freeze_gl glock
  i2c: eg20t: Load module automatically if ID matches
  arm64/alternatives: don't patch up internal branches
  iio:magnetometer:ak8974: Fix alignment and data leak issues
  iio:humidity:hdc100x Fix alignment and data leak issues
  iio: magnetometer: ak8974: Fix runtime PM imbalance on error
  iio: core: add missing IIO_MOD_H2/ETHANOL string identifiers
  iio: mma8452: Add missed iio_device_unregister() call in mma8452_probe()
  iio: pressure: zpa2326: handle pm_runtime_get_sync failure
  iio:humidity:hts221 Fix alignment and data leak issues
  iio:pressure:ms5611 Fix buffer element alignment
  iio:health:afe4403 Fix timestamp alignment and prevent data leak.
  spi: spi-fsl-dspi: Fix lockup if device is shutdown during SPI transfer
  net: dsa: bcm_sf2: Fix node reference count
  of: of_mdio: Correct loop scanning logic
  net: macb: call pm_runtime_put_sync on failure path
  net: ethernet: mvneta: Do not error out in non serdes modes
  net: ethernet: mvneta: Add back interface mode validation
  Revert "usb/ohci-platform: Fix a warning when hibernating"
  Revert "usb/ehci-platform: Set PM runtime as active on resume"
  Revert "usb/xhci-plat: Set PM runtime as active on resume"
  net: sfp: add support for module quirks
  net: sfp: add some quirks for GPON modules
  ARM: OMAP4+: remove pdata quirks for omap4+ iommus
  ARM: OMAP2+: Add workaround for DRA7 DSP MStandby errata i879
  ARM: OMAP2+: use separate IOMMU pdata to fix DRA7 IPU1 boot
  mmc: mmci: Support any block sizes for ux500v2 and qcom variant
  HID: quirks: Remove ITE 8595 entry from hid_have_special_driver
  ARM: at91: pm: add quirk for 

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

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

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


[Kernel-packages] [Bug 1889669] Re: Focal update: v5.4.54 upstream stable release

2020-08-03 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.54 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.54 upstream stable release
     from git://git.kernel.org/

  soc: qcom: rpmh: Dirt can only make you dirtier, not cleaner
  gpio: arizona: handle pm_runtime_get_sync failure case
  gpio: arizona: put pm_runtime in case of failure
  pinctrl: amd: fix npins for uart0 in kerncz_groups
  mac80211: allow rx of mesh eapol frames with default rx key
  scsi: scsi_transport_spi: Fix function pointer check
  xtensa: fix __sync_fetch_and_{and,or}_4 declarations
  xtensa: update *pos in cpuinfo_op.next
  scsi: mpt3sas: Fix unlock imbalance
  drivers/net/wan/lapbether: Fixed the value of hard_header_len
  ALSA: hda/hdmi: fix failures at PCM open on Intel ICL and later
  net: sky2: initialize return of gm_phy_read
  drm/nouveau/i2c/g94-: increase NV_PMGR_DP_AUXCTL_TRANSACTREQ timeout
  scsi: mpt3sas: Fix error returns in BRM_status_show
  scsi: dh: Add Fujitsu device to devinfo and dh lists
  dm: use bio_uninit instead of bio_disassociate_blkg
  drivers/firmware/psci: Fix memory leakage in alloc_init_cpu_groups()
  fuse: fix weird page warning
  irqdomain/treewide: Keep firmware node unconditionally allocated
  ARM: dts: imx6qdl-gw551x: Do not use 'simple-audio-card,dai-link'
  ARM: dts: imx6qdl-gw551x: fix audio SSI
  dmabuf: use spinlock to access dmabuf->name
  drm/amd/display: Check DMCU Exists Before Loading
  SUNRPC reverting d03727b248d0 ("NFSv4 fix CLOSE not waiting for direct IO 
compeletion")
  btrfs: reloc: fix reloc root leak and NULL pointer dereference
  btrfs: reloc: clear DEAD_RELOC_TREE bit for orphan roots to prevent runaway 
balance
  uprobes: Change handle_swbp() to send SIGTRAP with si_code=SI_KERNEL, to fix 
GDB regression
  ALSA: hda/realtek: Fixed ALC298 sound bug by adding quirk for Samsung 
Notebook Pen S
  ALSA: info: Drop WARN_ON() from buffer NULL sanity check
  ASoC: rt5670: Correct RT5670_LDO_SEL_MASK
  btrfs: fix double free on ulist after backref resolution failure
  btrfs: fix mount failure caused by race with umount
  btrfs: fix page leaks after failure to lock page for delalloc
  bnxt_en: Fix race when modifying pause settings.
  bnxt_en: Fix completion ring sizing with TPA enabled.
  fpga: dfl: pci: reduce the scope of variable 'ret'
  fpga: dfl: fix bug in port reset handshake
  hippi: Fix a size used in a 'pci_free_consistent()' in an error handling path
  vsock/virtio: annotate 'the_virtio_vsock' RCU pointer
  ax88172a: fix ax88172a_unbind() failures
  RDMA/mlx5: Use xa_lock_irq when access to SRQ table
  ASoC: Intel: bytcht_es8316: Add missed put_device()
  net: dp83640: fix SIOCSHWTSTAMP to update the struct with actual configuration
  ieee802154: fix one possible memleak in adf7242_probe
  drm: sun4i: hdmi: Fix inverted HPD result
  net: smc91x: Fix possible memory leak in smc_drv_probe()
  bonding: check error value of register_netdevice() immediately
  mlxsw: destroy workqueue when trap_register in mlxsw_emad_init
  ionic: use offset for ethtool regs data
  ionic: fix up filter locks and debug msgs
  net: ag71xx: add missed clk_disable_unprepare in error path of probe
  net: hns3: fix error handling for desc filling
  net: dsa: microchip: call phy_remove_link_mode during probe
  netdevsim: fix unbalaced locking in nsim_create()
  qed: suppress "don't support RoCE & iWARP" flooding on HW init
  qed: suppress false-positives interrupt error messages on HW init
  ipvs: fix the connection sync failed in some cases
  net: ethernet: ave: Fix error returns in ave_init
  Revert "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"
  nfsd4: fix NULL dereference in nfsd/clients display code
  enetc: Remove the mdio bus on PF probe bailout
  i2c: rcar: always clear ICSAR to avoid side effects
  i2c: i2c-qcom-geni: Fix DMA transfer race
  bonding: check return value of register_netdevice() in bond_newlink()
  geneve: fix an uninitialized value in geneve_changelink()
  serial: exar: Fix GPIO configuration for Sealevel cards based on XR17V35X
  scripts/decode_stacktrace: strip basepath from all paths
  scripts/gdb: fix lx-symbols 'gdb.error' while loading modules
  HID: i2c-hid: add 

[Kernel-packages] [Bug 1887294] Re: [nvidia] Display freeze

2020-08-03 Thread fa2k
Done. There's been no more crash on 440, and I'll post here if I get a
crash on 450.

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

Title:
  [nvidia] Display freeze

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  The display is completely frozen, and no signal is output to the
  monitors. There is also no signal when switching to a console (Ctr-
  Alt-F1). I have normal access via SSH.

  It happens about once in 14 days. Only happens when turning the
  display off or on (about once in 15 screen power cycles).

  nvidia-smi still works (via SSH; without any options)

  DISPLAY=:1 xset dpms force on

  hangs indefinitely.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul 12 17:47:58 2020
  DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] 
https://repo.skype.com/deb stable main # disabled on upgrade to focal' was 
disabled (unknown mirror)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae]
  InstallationDate: Installed on 2016-07-27 (1445 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago)
  dmi.bios.date: 04/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8C WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Jul  7 22:02:38 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+subscriptions

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


[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value

2020-08-03 Thread Frank Heimes
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]

  Impact: The tc command does not show the correct values for tcp_flags
  (and ip_tos) on filter rules. This might break other scripts parsing
  that output but at least confuses users.

  Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output"
  from upstream iproute2.

  Testcase:
  tc qdisc add dev lo ingress
  tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
  tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \
   tcp_flags 0x909/f00

  tc filter show dev lo parent :

  filter protocol ip pref 3 flower chain 0
  filter protocol ip pref 3 flower chain 0 handle 0x1
    eth_type ipv4
    ip_tos a9606c10 <-- bad, should be 0x8/32
    not_in_hw
  filter protocol ip pref 5 flower chain 0
  filter protocol ip pref 5 flower chain 0 handle 0x1
    eth_type ipv4
    ip_proto tcp
    tcp_flags 909909 <-- bad, should be 0x909/f00
    not_in_hw

  Note that the ip_tos value in the -j[son] output is correct, while the 
tcp_flags value is
  is incorrect in both cases.

  Risk of Regression:
  Low: Usually scripts would use the json output and that has at least the ip 
output correct. And the values shown in the bad case seem to be little useful. 
So it seems unlikely anybody relied on them. But cannot completely be ruled out.

  === Original description ===

  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r

  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 22   /* <--- Wrong */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r

  After that, using "tc filter show dev p0v2_r root" to verify, we still
  see the same output (tcp_flags 22) as shown in 2) above, which is
  wrong.

  Userspace tool common name: tc

  The userspace tool has the following bit modes: 64-bit

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */

  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.

  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 0x2/7   /* <--- Correct */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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

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

2020-08-03 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad doesn't work at all (No response from the Touchpad), I have
  an acer aspire E5-523-91TL. I did a fresh install (first time
  installing Ubuntu on this pc). Immediately after i moved from Windows
  to Ubuntu, the touchpad stopped working. i followed the steps as
  described in https://wiki.ubuntu.com/DebuggingTouchpadDetection.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brentdevent   1648 F pulseaudio
   /dev/snd/controlC0:  brentdevent   1648 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  3 19:46:11 2020
  InstallationDate: Installed on 2020-08-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire E5-523
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=31ca8f5a-d3c0-4886-bae4-5c1d6d4f0f36 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Wasp_SR
  dmi.board.vendor: Acer
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd06/28/2017:svnAcer:pnAspireE5-523:pvrV1.18:rvnAcer:rnWasp_SR:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SR
  dmi.product.name: Aspire E5-523
  dmi.product.sku: Aspire E5-523_1099_1.18
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1857938] Re: Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening from suspended state

2020-08-03 Thread daljit97
I have the dmesg for the kernel.

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

Title:
  Extreme touchpad lag on HP Envy X360 13-ag0xxx on startup/awakening
  from suspended state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 20.04 with kernel 5.4.4 on my HP Envy X360 13-ag0xxx. The 
touchpad works fine under most conditions, however whenever the system wakes up 
from a suspended state (on startup) in the first 15-20 seconds the touchpad is 
quite laggy (everything else is smooth) and very hard to use. I am using 
Libinput 1.14.1.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2340 F pulseaudio
   /dev/snd/controlC0:  user   2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (83 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ENVY x360 Convertible 13-ag0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=5cd8ac1d-85c5-4ed5-84c6-fb958f99ee4c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  Tags:  focal
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8496
  dmi.board.vendor: HP
  dmi.board.version: 92.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.42:bd05/13/2019:svnHP:pnHPENVYx360Convertible13-ag0xxx:pvr:rvnHP:rn8496:rvr92.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ag0xxx
  dmi.product.sku: 4JV79EA#ABU
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1890181] [NEW] Touchpad doesn't work

2020-08-03 Thread Brent van Lieshout
Public bug reported:

Touchpad doesn't work at all (No response from the Touchpad), I have an
acer aspire E5-523-91TL. I did a fresh install (first time installing
Ubuntu on this pc). Immediately after i moved from Windows to Ubuntu,
the touchpad stopped working. i followed the steps as described in
https://wiki.ubuntu.com/DebuggingTouchpadDetection.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  brentdevent   1648 F pulseaudio
 /dev/snd/controlC0:  brentdevent   1648 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  3 19:46:11 2020
InstallationDate: Installed on 2020-08-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Aspire E5-523
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=31ca8f5a-d3c0-4886-bae4-5c1d6d4f0f36 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/28/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Wasp_SR
dmi.board.vendor: Acer
dmi.board.version: V1.18
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd06/28/2017:svnAcer:pnAspireE5-523:pvrV1.18:rvnAcer:rnWasp_SR:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SR
dmi.product.name: Aspire E5-523
dmi.product.sku: Aspire E5-523_1099_1.18
dmi.product.version: V1.18
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal

** Attachment added: ""cat /proc/bus/input/devices > ~/devices""
   https://bugs.launchpad.net/bugs/1890181/+attachment/5398379/+files/devices

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad doesn't work at all (No response from the Touchpad), I have
  an acer aspire E5-523-91TL. I did a fresh install (first time
  installing Ubuntu on this pc). Immediately after i moved from Windows
  to Ubuntu, the touchpad stopped working. i followed the steps as
  described in https://wiki.ubuntu.com/DebuggingTouchpadDetection.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brentdevent   1648 F pulseaudio
   /dev/snd/controlC0:  brentdevent   1648 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  3 19:46:11 2020
  InstallationDate: Installed on 2020-08-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire E5-523
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=31ca8f5a-d3c0-4886-bae4-5c1d6d4f0f36 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Wasp_SR
  dmi.board.vendor: Acer
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.18:bd06/28/2017:svnAcer:pnAspireE5-523:pvrV1.18:rvnAcer:rnWasp_SR:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SR
  dmi.product.name: Aspire E5-523
  dmi.product.sku: Aspire E5-523_1099_1.18
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer

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

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

2020-08-03 Thread Md Ayquassar
I recall that on one of my machines I had exactly the same situation as
reported in #20 and #21 up to the timings (5.3.0-26-generic in Ubuntu
19.10 with EFI Secure Boot and dual boot with Windows 10,
fastboot/hibernation disabled, LZ4 image by default, booting failed
often, booting succeeded upon reinstall with EFI secure boot).
Unfortunately, I don't have this machine any longer. @mario-gleirscher
would probably be of help if they provide us with some debugging when
asked by the Ubuntu maintainers.

On another machine, I still have this annoying printf in dmesg (and
journalctl -b):

[0.215092] NET: Registered protocol family 1
[0.215096] NET: Registered protocol family 44
[0.215105] pci :00:02.0: Video device with shadowed ROM at [mem 
0x000c-0x000d]
[0.215670] PCI: CLS 64 bytes, default 64
[0.215696] Trying to unpack rootfs image as initramfs...
[0.303126] Initramfs unpacking failed: Decoding failed
[0.306614] Freeing initrd memory: 48364K

I run 5.4.0-42-generic in Ubuntu 20.04.1 LTS focal.

As for me, this issue seems to simply uselessly burn processor cycles
(and, as every such issue, indirectly generate superfluous carbon
dioxide); there is a potential for optimization here.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1873961] Comment bridged from LTC Bugzilla

2020-08-03 Thread bugproxy
--- Comment From z...@us.ibm.com 2020-08-03 13:45 EDT---
Follow the link Waiki Wright provided today:
"https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961see comment 17"

Get the binary from:
https://launchpad.net/ubuntu/bionic/ppc64el/iproute2/4.15.0-2ubuntu1.2
iproute2_4.15.0-2ubuntu1.2_ppc64el.deb (783.3 KiB)

After installation:
root@ltcgen4:~# ls -al /sbin/tc
-rwxr-xr-x 1 root root 746392 Jul 15 10:16 /sbin/tc

root@ltcgen4:~# sum /sbin/tc
45845   729

root@ltcgen4:~# dpkg -l |grep iproute
ii  iproute2 4.15.0-2ubuntu1.2  
  ppc64el  networking and traffic control tools

It works with this iproute2 package.

# /sbin/tc qdisc add dev lo ingress
# /sbin/tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
# /sbin/tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp 
tcp_flags 0x909/f00

# /sbin/tc filter show dev lo parent :
filter protocol ip pref 3 flower chain 0
filter protocol ip pref 3 flower chain 0 handle 0x1
eth_type ipv4
ip_tos 0x8/32
not_in_hw
filter protocol ip pref 5 flower chain 0
filter protocol ip pref 5 flower chain 0 handle 0x1
eth_type ipv4
ip_proto tcp
tcp_flags 0x909/f00   /* <--- */
not_in_hw

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]

  Impact: The tc command does not show the correct values for tcp_flags
  (and ip_tos) on filter rules. This might break other scripts parsing
  that output but at least confuses users.

  Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output"
  from upstream iproute2.

  Testcase:
  tc qdisc add dev lo ingress
  tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
  tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \
   tcp_flags 0x909/f00

  tc filter show dev lo parent :

  filter protocol ip pref 3 flower chain 0
  filter protocol ip pref 3 flower chain 0 handle 0x1
    eth_type ipv4
    ip_tos a9606c10 <-- bad, should be 0x8/32
    not_in_hw
  filter protocol ip pref 5 flower chain 0
  filter protocol ip pref 5 flower chain 0 handle 0x1
    eth_type ipv4
    ip_proto tcp
    tcp_flags 909909 <-- bad, should be 0x909/f00
    not_in_hw

  Note that the ip_tos value in the -j[son] output is correct, while the 
tcp_flags value is
  is incorrect in both cases.

  Risk of Regression:
  Low: Usually scripts would use the json output and that has at least the ip 
output correct. And the values shown in the bad case seem to be little useful. 
So it seems unlikely anybody relied on them. But cannot completely be ruled out.

  === Original description ===

  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r

  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 22   /* <--- Wrong */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r

  After that, using "tc filter show dev p0v2_r root" to verify, we still
  see the same output (tcp_flags 22) as shown in 2) above, which is
  wrong.

  Userspace tool common name: tc

  The userspace tool has the following bit modes: 64-bit

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = 

[Kernel-packages] [Bug 1889780] Re: Unable to change screen resolution after upgrade to 5.4.0-42-generic

2020-08-03 Thread Dave Dave
I was able to run apport-collect 1889780 . Changed status to
"Confirmed".

 Dave

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-08-03 Thread dann frazier
@Milan: I don't doubt that there maybe also be a driver issue, but that
wasn't the root cause of this issue.

@All: It might be helpful to know, for each of these cases, if what you are 
seeing is also correlated with the patch we reverted (and are planning to 
reintroduce) in older releases. To do so, you could try reverting:
commit 0b6a70743beacb ("usb: handle warm-reset port requests on hub resume").

Alternatively, if you're not comfortable w/ building your own kernel and
the bionic kernel supports your hardware, you could try comparing the
results of 4.15.0-70.79 and 4.15.0-72.81.

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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


[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-08-03 Thread Balint Reczey
I've added the OEM Solutions Group team for awareness. I'm not sure what
the final fix will be since servers' and desktops'/laptops' ideal
default seem to be different, but most likely the certification tests
should be adjusted if we don't end up restoring the previous behaviour
of the ondemand.service unconditionally.

The latest LTS release, 20.04 is not affected so the certification test
changes are probably not very urgent.

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Invalid

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

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

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


[Kernel-packages] [Bug 1742089] Re: Third unkown screen

2020-08-03 Thread Sebastien Bacher
** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-440
(Ubuntu)

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

Title:
  Third unkown screen

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  After updating a third unknown screen appeared, apparently connected
  to the vga port according to xrandr

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan  9 09:35:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-104-generic, x86_64: installed
   nvidia-384, 384.90, 4.4.0-104-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
  InstallationDate: Installed on 2017-01-03 (370 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=21e3988f-d702-4bae-b6e3-54620f292e02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0T3YTY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1742089/+subscriptions

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


[Kernel-packages] [Bug 1742089] [NEW] Third unkown screen

2020-08-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After updating a third unknown screen appeared, apparently connected to
the vga port according to xrandr

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Jan  9 09:35:25 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-104-generic, x86_64: installed
 nvidia-384, 384.90, 4.4.0-104-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
 NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
InstallationDate: Installed on 2017-01-03 (370 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Precision M4800
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=21e3988f-d702-4bae-b6e3-54620f292e02 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0T3YTY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
Third unkown screen
https://bugs.launchpad.net/bugs/1742089
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-440 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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-08-03 Thread Milan Bulat
I can also confirm that upgrading to kernel 5.8.0 didn't fix the
problem.

@dannf: I have tried three different USB cables with exactly the same
results. I'm pretty sure the problem is in the USB kernel drivers.

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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


[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-08-03 Thread Balint Reczey
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Invalid

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

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

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


[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-08-03 Thread dann frazier
fyi, the system for which I originally filed this bug was conclusively
determined to have an out-of-spec USB cable, for which the manufacturer
is providing replacements.

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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


[Kernel-packages] [Bug 1884767] Re: shiftfs: fix btrfs regression

2020-08-03 Thread Stéphane Graber
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  shiftfs: fix btrfs regression

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

Bug description:
  SRU Justification

  Impact: The patch
  commit cfaa482afb97e3c05d020af80b897b061109d51f
  Author: Christian Brauner 
  Date:   Tue Apr 14 22:26:53 2020 +0200

  UBUNTU: SAUCE: shiftfs: fix dentry revalidation

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

  to fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757
  regresses various btrfs + shiftfs users. Creating a btrfs subvolume,
  deleting it, and then trying to recreate it will cause EEXIST to be returned.
  It also leaves some files in a half-visible state because they are not 
revalidated
  correctly.
  Faulty behavior such as this can be reproduced via:

  btrfs subvolume create my-subvol
  btrfs subvolume delete my-subvol

  Fix: We need to revert this patch restoring the old behavior. This will 
briefly
  resurface https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757 which 
I will fix in a follow-up patch on top of this revert. We basically split the 
part that fixes https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757 
out of the revert.

  Regression Potential: Limited to shiftfs.

  Test Case: Build a kernel with fix applied and run above reproducer.

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

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5398340/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


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

2020-08-03 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions

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


[Kernel-packages] [Bug 1889780] Re: Unable to change screen resolution after upgrade to 5.4.0-42-generic

2020-08-03 Thread Dave Dave
apport information

** Tags added: apport-collected

** Description changed:

   When booting using 5.4.0-42-generic kernel, screen resolution is fixed
  at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.
  
  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.
  
  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4
  
  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?
  
   Thanks,
Dave
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dave   2495 F pulseaudio
+  /dev/snd/controlC1:  dave   2495 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-02-27 (158 days ago)
+ InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-62-generic N/A
+  linux-backports-modules-5.3.0-62-generic  N/A
+  linux-firmware1.173.19
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 5.3.0-62-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/18/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 2801
+ dmi.board.asset.tag: Default string
+ dmi.board.name: ROG STRIX B450-F GAMING
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

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

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-08-03 Thread Milan Bulat
I can also confirm that the bug is not fixed, and I can also confirm two
Bamoqi's posts - I'm testing it on various mobile phones and it's
messing up my development workflow as phones sometimes do not connect
when attached to USB cable.

I have tried three different USB-A -> USB-C cables from various
manufacturers, and they are all reported as bad by the kernel.

Very annoying bug.

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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


[Kernel-packages] [Bug 1843742] Re: irda-utils ftbfs in eoan

2020-08-03 Thread Stefan Bader
Exact status in Debian:
irda-utils | 0.9.18-12 | oldoldstable | source, amd64, armel, armhf, i386
irda-utils | 0.9.18-15 | oldstable| source, amd64, arm64, armel, armhf, 
i386, mips, mips64el, mipsel, ppc64el, s390x

ircp-tray  | 0.7.6-1.1 | oldoldstable   | source, amd64, armel, armhf, i386
ircp-tray  | 0.7.6-1.2 | oldstable  | source
ircp-tray  | 0.7.6-1.2 | unstable   | source
ircp-tray  | 0.7.6-1.2 | unstable-debug | source
ircp-tray  | 0.7.6-1.2+b1  | oldstable  | amd64, arm64, armel, armhf, i386, 
mips, mips64el, mipsel, ppc64el, s390x
ircp-tray  | 0.7.6-1.2+b1  | unstable   | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

For Ubuntu the proposal would be to remove both source and binaries of
irda-utils and ircp-tray from Groovy.

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

Title:
  irda-utils ftbfs in eoan

Status in irda-utils package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
  .irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz

  gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline 
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c 
irdadump.c
  irdadump.c: In function ‘print_time’:
  irdadump.c:82:13: warning: g_string_append_printf
 82 |  g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
  irdadump.c: In function ‘print_diff_time’:
  irdadump.c:108:13: warning: g_string_append_printf
108 |  g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
  irdadump.c: In function ‘parse_irda_frame’:
  irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
  irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
  irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
  irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
  irdadump.c: In function ‘irdadump_loop’:
  irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this 
function); did you mean ‘SIOCGARP’?
286 |  if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
  irdadump.c:286:16: note: each undeclared identifier is reported only once for 
each function it appears in
  make[1]: *** [Makefile:48: irdadump.o] Error 1
  make[1]: Leaving directory '/<>/irdadump'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/1843742/+subscriptions

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


[Kernel-packages] [Bug 1843742] Re: irda-utils ftbfs in eoan

2020-08-03 Thread Stefan Bader
There seems to be one package which depends on irda-utils (ircp-tray in
universe/misc). It was removed from testing in Debian due to the removal
of irda-utils there. Seems to make no sense to keep any tray icon around
which shows irda activity without userspace tools and kernel support
around.

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

Title:
  irda-utils ftbfs in eoan

Status in irda-utils package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
  .irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz

  gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline 
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c 
irdadump.c
  irdadump.c: In function ‘print_time’:
  irdadump.c:82:13: warning: g_string_append_printf
 82 |  g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
  irdadump.c: In function ‘print_diff_time’:
  irdadump.c:108:13: warning: g_string_append_printf
108 |  g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
  irdadump.c: In function ‘parse_irda_frame’:
  irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
  irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
  irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
  irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
  irdadump.c: In function ‘irdadump_loop’:
  irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this 
function); did you mean ‘SIOCGARP’?
286 |  if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
  irdadump.c:286:16: note: each undeclared identifier is reported only once for 
each function it appears in
  make[1]: *** [Makefile:48: irdadump.o] Error 1
  make[1]: Leaving directory '/<>/irdadump'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/1843742/+subscriptions

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


[Kernel-packages] [Bug 1843742] Re: irda-utils ftbfs in eoan

2020-08-03 Thread Stefan Bader
The irda-utils package was removed in Debian (https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=907453) mentioning the lack of kernel
support. Checking the upstream kernel repo, the following commit was
part of v4.17:

commit d64c2a76123f0300b08d0557ad56e9d599872a36
Author: Greg Kroah-Hartman 
Date:   Wed Mar 14 13:12:26 2018 +0100

staging: irda: remove the irda network stack and drivers

No one has publicly stepped up to maintain this broken codebase for
devices that no one uses anymore, so let's just drop the whole thing.

If someone really wants/needs it, we can revert this and they can fix
the code up to work properly.

Cc: David S. Miller 
Signed-off-by: Greg Kroah-Hartman 

This would mean that no Ubuntu kernel after 18.04/Bionic has kernel
support. Proposing to remove this package from Groovy onward.

** Changed in: irda-utils (Ubuntu)
 Assignee: (unassigned) => Stefan Bader (smb)

** Bug watch added: Debian Bug tracker #907453
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907453

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

Title:
  irda-utils ftbfs in eoan

Status in irda-utils package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
  .irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz

  gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline 
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c 
irdadump.c
  irdadump.c: In function ‘print_time’:
  irdadump.c:82:13: warning: g_string_append_printf
 82 |  g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
  irdadump.c: In function ‘print_diff_time’:
  irdadump.c:108:13: warning: g_string_append_printf
108 |  g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
  irdadump.c: In function ‘parse_irda_frame’:
  irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
  irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
  irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
  irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
  irdadump.c: In function ‘irdadump_loop’:
  irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this 
function); did you mean ‘SIOCGARP’?
286 |  if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
  irdadump.c:286:16: note: each undeclared identifier is reported only once for 
each function it appears in
  make[1]: *** [Makefile:48: irdadump.o] Error 1
  make[1]: Leaving directory '/<>/irdadump'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/1843742/+subscriptions

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


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

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

apport-collect 1890136

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

Title:
  Return value in rtnetlink.sh from kselftests/net will be override in
  the last test

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In this test, it uses ret to store the return value of each test.

  However, this value will be reset to 0 in the beginning of each test.

  In the end of this test, it will judge PASS/FAIL base on this value.

  Thus this will cause false-negative in some cases.
  Below is an example for the test on Bionic OEM-OSP1, test "ip6erspan", 
"erspan", "ip6gretap" failed with return value 255, but the return value will 
soon be overridden with 0 if following test passed without any issue (I made 
the test to print === RET $ret === line for debugging purpose):

  PASS: policy routing
  === RET 0 ===
  PASS: route get
  === RET 0 ===
  PASS: preferred_lft addresses have expired
  === RET 0 ===
  PASS: tc htb hierarchy
  === RET 0 ===
  PASS: gre tunnel endpoint
  === RET 0 ===
  PASS: gretap
  === RET 0 ===
  Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ hoplimit TTL ]
[ encaplimit ELIM ]
[ tclass TCLASS ]
[ flowlabel FLOWLABEL ]
[ dscp inherit ]
[ fwmark MARK ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ erspan IDX ]

  Where: ADDR  := IPV6_ADDRESS
 TTL   := { 0..255 } (default=64)
 KEY   := { DOTTED_QUAD | NUMBER }
 ELIM  := { none | 0..255 }(default=4)
 TCLASS:= { 0x0..0xff | inherit }
 FLOWLABEL := { 0x0..0xf | inherit }
 MARK  := { 0x0..0x | inherit }
  Cannot find device "ip6gretap00"
  FAIL: ip6gretap
  === RET 255 ===
  Usage: ... { gre | gretap | erspan } [ remote ADDR ]
  [ local ADDR ]
  [ [i|o]seq ]
  [ [i|o]key KEY ]
  [ [i|o]csum ]
  [ ttl TTL ]
  [ tos TOS ]
  [ [no]pmtudisc ]
  [ [no]ignore-df ]
  [ dev PHYS_DEV ]
  [ noencap ]
  [ encap { fou | gue | none } ]
  [ encap-sport PORT ]
  [ encap-dport PORT ]
  [ [no]encap-csum ]
  [ [no]encap-csum6 ]
  [ [no]encap-remcsum ]
  [ external ]
  [ fwmark MARK ]
  [ erspan IDX ]

  Where: ADDR := { IP_ADDRESS | any }
 TOS  := { NUMBER | inherit }
 TTL  := { 1..255 | inherit }
 KEY  := { DOTTED_QUAD | NUMBER }
 MARK := { 0x0..0x }
  Cannot find device "erspan00"
  Cannot find device "erspan00"
  Cannot find device "erspan00"
  Usage: ... { gre | gretap | erspan } [ remote ADDR ]
  [ local ADDR ]
  [ [i|o]seq ]
  [ [i|o]key KEY ]
  [ [i|o]csum ]
  [ ttl TTL ]
  [ tos TOS ]
  [ [no]pmtudisc ]
  [ [no]ignore-df ]
  [ dev PHYS_DEV ]
   

[Kernel-packages] [Bug 1890136] [NEW] Return value in rtnetlink.sh from kselftests/net will be override in the last test

2020-08-03 Thread Po-Hsu Lin
Public bug reported:

In this test, it uses ret to store the return value of each test.

However, this value will be reset to 0 in the beginning of each test.

In the end of this test, it will judge PASS/FAIL base on this value.

Thus this will cause false-negative in some cases.
Below is an example for the test on Bionic OEM-OSP1, test "ip6erspan", 
"erspan", "ip6gretap" failed with return value 255, but the return value will 
soon be overridden with 0 if following test passed without any issue (I made 
the test to print === RET $ret === line for debugging purpose):

PASS: policy routing
=== RET 0 ===
PASS: route get
=== RET 0 ===
PASS: preferred_lft addresses have expired
=== RET 0 ===
PASS: tc htb hierarchy
=== RET 0 ===
PASS: gre tunnel endpoint
=== RET 0 ===
PASS: gretap
=== RET 0 ===
Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
  [ local ADDR ]
  [ [i|o]seq ]
  [ [i|o]key KEY ]
  [ [i|o]csum ]
  [ hoplimit TTL ]
  [ encaplimit ELIM ]
  [ tclass TCLASS ]
  [ flowlabel FLOWLABEL ]
  [ dscp inherit ]
  [ fwmark MARK ]
  [ dev PHYS_DEV ]
  [ noencap ]
  [ encap { fou | gue | none } ]
  [ encap-sport PORT ]
  [ encap-dport PORT ]
  [ [no]encap-csum ]
  [ [no]encap-csum6 ]
  [ [no]encap-remcsum ]
  [ erspan IDX ]

Where: ADDR  := IPV6_ADDRESS
   TTL   := { 0..255 } (default=64)
   KEY   := { DOTTED_QUAD | NUMBER }
   ELIM  := { none | 0..255 }(default=4)
   TCLASS:= { 0x0..0xff | inherit }
   FLOWLABEL := { 0x0..0xf | inherit }
   MARK  := { 0x0..0x | inherit }
Cannot find device "ip6gretap00"
FAIL: ip6gretap
=== RET 255 ===
Usage: ... { gre | gretap | erspan } [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ ttl TTL ]
[ tos TOS ]
[ [no]pmtudisc ]
[ [no]ignore-df ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ external ]
[ fwmark MARK ]
[ erspan IDX ]

Where: ADDR := { IP_ADDRESS | any }
   TOS  := { NUMBER | inherit }
   TTL  := { 1..255 | inherit }
   KEY  := { DOTTED_QUAD | NUMBER }
   MARK := { 0x0..0x }
Cannot find device "erspan00"
Cannot find device "erspan00"
Cannot find device "erspan00"
Usage: ... { gre | gretap | erspan } [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ ttl TTL ]
[ tos TOS ]
[ [no]pmtudisc ]
[ [no]ignore-df ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ external ]
[ fwmark MARK ]
[ erspan IDX ]

Where: ADDR := { IP_ADDRESS | any }
   TOS  := { NUMBER | inherit }
   TTL  := { 1..255 | inherit }
   KEY  := { DOTTED_QUAD | NUMBER }
   MARK := { 0x0..0x }
Cannot find device "erspan00"
Cannot find device "erspan00"
Cannot find device "erspan00"
FAIL: erspan
=== RET 255 ===
Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
  [ local ADDR ]
  [ [i|o]seq ]
  [ [i|o]key KEY ]
  [ [i|o]csum ]
  [ hoplimit TTL ]
  [ encaplimit ELIM ]
  

  1   2   >