[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[axt]

Vicky, your current issue has nothing to do with the UEFI issue in this
thread.

> I then select windows 8 and use windows 8.

Technically you only had to do an in-place upgrade to Win10.
This reliably ;-) overwrites Grub.

Officially, this has been possible free of charge for up to 1 year after
the release of Win10. With several time extensions.

Then you can install an up-to-date Linux distribution in dualboot.

But if you can boot normally from a USB stick, you don't have the
problem in this thread anyway and can install Linux as the only OS.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  If you have applied updates, and find that you can not boot the above
  fixed kernel because of Secure Boot and that the kernel is unsigned,
  but can still boot another kernel for your system; here's what you can
  do:

  1) Download 
http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed:
  $ wget 
http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed

  2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
  $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

  3) Reboot; you should now be able to load the new unsigned kernel that
  allows fixing firmware / SPI.

  4) Once you're satisfied that things work; boot to Ubuntu with a
  standard, signed kernel, and re-install the right GRUB version for
  your system:

  $ sudo grub-install

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116

[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade

[Günter Neiß]

OK, Result for #30: BAD

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

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the problem 
will show up again.
  So I block these versions too.

  BTW: Due to the stuck I am able to see some other error messages that are not 
reported in the journal. The very last 3-5 lines show:
  shutdown [1]: Failed to wait for process: Protocol error
  These lines are present although in the working kernels, but hard to see, 
because the system powers down some ms after these lines are displayed!
  This problem seams to be solved more than one year ago in the upstream kernel!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gneiss 1929 F pulseaudio
   /dev/snd/controlC0:  gneiss 1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-02 (448 days ago)
  InstallationMedia:
   
  MachineType: Acer Aspire E5-771G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic 
root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth 
resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-61-generic N/A
   linux-backports-modules-5.3.0-61-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-771G
  dmi.product.sku: Aspire E5-771G_0884_1_23
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1889223] Re: vc4-kms-v3d boot failure focal armhf preinstalled server

[Juerg Haefliger]

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

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

** Changed in: linux-raspi (Ubuntu Focal)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  vc4-kms-v3d boot failure focal armhf preinstalled server

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Focal:
  New

Bug description:
  Booting 20.04 armhf preinstalled-server on Pi3b+ with vc4-kms-v3d
  selected [1] causes boot failure with [2] output on UART. Further
  system info in [3]

  Side note: Booting with the same usercfg.txt but with the 18.04 vc4
  -kms-v3d.dtbo file "works": the boot is normal without the errors
  shown in [2].

  [1]

  ubuntu@ubuntu:~$ cat /boot/firmware/usercfg.txt 
  # Place "config.txt" changes (dtparam, dtoverlay, disable_overscan, etc.) in
  # this file. Please refer to the README file for a description of the various
  # configuration files on the boot partition.
  dtoverlay=vc4-kms-v3d

  [2]

Starting kernel ...

  [0.039873] cma: CMA area linux,cma could not be activated
  [0.043189] DMA: failed to allocate 1024 KiB pool for atomic coherent
  allocation
  [0.308022] kobject_add_internal failed for 3e513000.framebuffer with
  -EEXIST, don't try to register things with the s.
  [1.141370] kvm [1]: Error, CPU 0 not supported!
  [1.235565] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 0 config (-12 80)
  [1.236723] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 1 config (-12 81)
  [1.237882] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 2 config (-12 82)
  [1.239014] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 3 config (-12 83)
  [1.240139] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 4 config (-12 84)
  [1.241263] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 5 config (-12 85)
  [1.242412] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 6 config (-12 86)
  [1.243526] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 7 config (-12 87)
  [1.831440] spi-bcm2835 3f204000.spi: could not get clk: -517
  [1.849256] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 2 config (-12 82)
  [1.850523] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get
  GPIO 2 config (-12 82)
  [1.852205] bcm2835_vchiq 3f00b840.mailbox: could not allocate DMA memory
  [2.369653] spi-bcm2835 3f204000.spi: cannot prepare fill_tx_desc -
  not using DMA mode
  [2.412710] sdhost: failed to allocate log buf
  ext4

  [3]

  ubuntu@ubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal

  ubuntu@ubuntu:~$ uname -a
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020 
armv7l armv7l armv7l GNU/Linux

  Initial part of lshw:
  ubuntu  
  description: ARMv7 Processor rev 4 (v7l)
  product: Raspberry Pi 3 Model B Plus Rev 1.3
  serial: 92021ecd
  width: 32 bits
  capabilities: smp

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

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

[Kernel-packages] [Bug 1889468] Re: 20.04.1 selecting audio output device does not work on rpi

[Juerg Haefliger]

** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)

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

** Changed in: linux-raspi (Ubuntu Focal)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

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

Title:
  20.04.1 selecting audio output device does not work on rpi

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Focal:
  New

Bug description:
  Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing 
that I can no longer select the audio output device with amixer. This used to 
be possible by using:
  amixer cset numid=3 2 for HDMI0
  amixer cset numid=3 3 for HDMI1
  amixer cset numid=3 1 for 3.5mm headphone jack

  However, now trying to set this gets the following error:
  amixer: Cannot find the given element from control default

  It seems that by default, it will now use the hdmi output for
  whichever one is connected, and will only output through the
  headphones if no hdmi device is connected.

  Kernel is:
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

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

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

[Kernel-packages] [Bug 1888691] Re: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps

[Juerg Haefliger]

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

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

Title:
  [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps

Status in snapd:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Focal:
  New

Bug description:
  The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots 
fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system 
does not boot. After it gets to "Starting kernel..." it just stops.  Attempting 
to power off/on the device after the failed boot fails in the uboot script:
  Hit any key to stop autoboot:  0
  switch to partitions #0, OK
  mmc0 is current device
  Scanning mmc 0:1...
  Found U-Boot script /boot.scr
  4638 bytes read in 28 ms (161.1 KiB/s)
  ## Executing script at 0240
  4096 bytes read in 39 ms (102.5 KiB/s)
  131072 bytes read in 45 ms (2.8 MiB/s)
  131072 bytes written in 89 ms (1.4 MiB/s)
  SCRIPT FAILED: continuing...
  45618 bytes read in 41 ms (1.1 MiB/s)
  Card did not respond to voltage select!
  starting USB...
  ...

  This does not seem to happen with the arm64 kernel, and booting the
  armhf kernel seems to work fine on pi3 devices - it just seems to be
  the combination of armhf and rpi4 that breaks right now.

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

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

[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade

[Alex Hung]

@gneisss,

I forgot to remove to *tool*.deb. They aren't needed.

next one: https://people.canonical.com/~alexhung/LP1888570/115f51d0fa11/

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

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the problem 
will show up again.
  So I block these versions too.

  BTW: Due to the stuck I am able to see some other error messages that are not 
reported in the journal. The very last 3-5 lines show:
  shutdown [1]: Failed to wait for process: Protocol error
  These lines are present although in the working kernels, but hard to see, 
because the system powers down some ms after these lines are displayed!
  This problem seams to be solved more than one year ago in the upstream kernel!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gneiss 1929 F pulseaudio
   /dev/snd/controlC0:  gneiss 1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-02 (448 days ago)
  InstallationMedia:
   
  MachineType: Acer Aspire E5-771G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic 
root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth 
resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-61-generic N/A
   linux-backports-modules-5.3.0-61-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-771G
  dmi.product.sku: Aspire E5-771G_0884_1_23
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install

[Daniel van Vugt]

Maybe try selecting 'Ubuntu on Wayland' from the login screen (icon in
the bottom right corner after you select the user). That will use a
different render path and might avoid the problem.

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

Title:
  [Ice Lake] Screen flickering and glitching after install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel integrated driver causes screen flickering with Ubuntu install.
  Windows did not have this issue

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 15:41:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a]
  InstallationDate: Installed on 2020-07-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ENVY Laptop 13-ba0xxx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 875A
  dmi.board.vendor: HP
  dmi.board.version: 07.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ba0xxx
  dmi.product.sku: 8KD13AV
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[Hui Wang]

Recently we found the CONFIG_PREEMPT is not enabled in the ubuntu
kernel, but it is enabled in the Pi OS's kernel. We plan to enable the
CONFIG_PREEMPT in the ubuntu kernel too. So please wait for that kernel
and then test a kernel with PREEMPT enabled.

Or you could test Pi OS's kernel first. Looks like there is 5.4 Pi OS's
kernel.

thx.

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

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

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

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

  
  kern.log message that appears after a while:

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

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

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

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

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

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  

[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop

[Hui Wang]

** Description changed:

  [Impact]
  On the LENOVO AMD renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.
  
  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.
  
  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305
  
  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41
  
  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  ucm-simplify-get_by_card-in-parser.c.patch
  ucm-implement-AlwaysTrue-Condition.Type.patch
  ucm-Allow-empty-strings-in-var-.-substitutions.patch
  ucm-substitution-remove-duplicate-allow_empty-assign.patch
  ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch
  ucm-substitute-the-merged-tree-completely.patch
- 
+ add Depends alsa-ucm-conf (>= 1.2.2-1ubuntu0.1.1) in the d/control
+ add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols
  
  [Test Case]
  On the AMD renoir machines:
  Boot the system with these updated packages (already backported kernel
  drivers to focal and oem-5.6 kernels), open the gnome-control-center,
  we could see the digital mic in the input device tab, and only one
  input 

[Kernel-packages] [Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  debian/rules editconfigs does not work on s390x to change s390x only
  configs

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

Bug description:
  On s390x

  pull-lp-source linux-5.4
  cd linux-*
  fakeroot ./debian/rules clean
  ./debian/rules editconfig
  dh_testdir;
  /bin/bash -e debian/scripts/misc/kernelconfig editconfigs
  Do you want to edit config: amd64/config.flavour.generic? [Y/n] n
  ...
  scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found
  make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1
  make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2
  make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build'
  make[1]: *** [Makefile:179: sub-make] Error 2
  make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0'
  make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2

  And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available
  to build on s390x for amd64, and also I don't want to touch amd64
  configs. Only s390x ones.

  As a user, I should be able to rebuild ports architecture kernel with
  tweaked config for testing, self-hosted without cross-compilers.

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

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

[Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Stefano Forli]

Very similar behavior and error message on Xeon E5-1620 and NVIDIA card (Quadro 
M2000).
Kernel 4.19.0-9-amd (Debian)

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

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

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

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

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

[mlx]

** Attachment added: "kernel_5.4.0-1015.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397093/+files/kernel_5.4.0-1015.log

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

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

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

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

  
  kern.log message that appears after a while:

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

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

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

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

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

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

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

[mlx]

I got myself the Ruideng TC66 USB tester and played a bit with it - it
appears that after the network dies on Raspberry, the system's stable
power consumption ends up higher than when it's functional and idling.
Some stray endless loop, perhaps?

** Attachment added: "RPi3B+ power consumption during bug"
   
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397091/+files/Screenshot%202020-07-30%20at%2001.16.47.png

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

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

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

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

  
  kern.log message that appears after a while:

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

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

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

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

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

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  

[Kernel-packages] [Bug 1889474] Re: Bionic update: upstream stable patchset 2020-07-29

[Kamal Mostafa]

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2020-07-29
  
-upstream stable patchset 2020-07-29
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.190, v4.19.135
+ 
+    from git://git.kernel.org/
+ 
+ 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
+ drivers/net/wan/lapbether: Fixed the value of hard_header_len
+ net: sky2: initialize return of gm_phy_read
+ drm/nouveau/i2c/g94-: increase NV_PMGR_DP_AUXCTL_TRANSACTREQ timeout
+ irqdomain/treewide: Keep firmware node unconditionally allocated
+ SUNRPC reverting d03727b248d0 ("NFSv4 fix CLOSE not waiting for direct IO 
compeletion")
+ spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours
+ IB/umem: fix reference count leak in ib_umem_odp_get()
+ uprobes: Change handle_swbp() to send SIGTRAP with si_code=SI_KERNEL, to fix 
GDB regression
+ 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.
+ hippi: Fix a size used in a 'pci_free_consistent()' in an error handling path
+ ax88172a: fix ax88172a_unbind() failures
+ net: dp83640: fix SIOCSHWTSTAMP to update the struct with actual configuration
+ 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
+ ipvs: fix the connection sync failed in some cases
+ i2c: rcar: always clear ICSAR to avoid side effects
+ bonding: check return value of register_netdevice() in bond_newlink()
+ serial: exar: Fix GPIO configuration for Sealevel cards based on XR17V35X
+ scripts/decode_stacktrace: strip basepath from all paths
+ HID: i2c-hid: add Mediacom FlexBook edge13 to descriptor override
+ HID: apple: Disable Fn-key key-re-mapping on clone keyboards
+ dmaengine: tegra210-adma: Fix runtime PM imbalance on error
+ Input: add `SW_MACHINE_COVER`
+ spi: mediatek: use correct SPI_CFG2_REG MACRO
+ regmap: dev_get_regmap_match(): fix string comparison
+ hwmon: (aspeed-pwm-tacho) Avoid possible buffer overflow
+ dmaengine: ioat setting ioat timeout as module parameter
+ Input: synaptics - enable InterTouch for ThinkPad X1E 1st gen
+ usb: gadget: udc: gr_udc: fix memleak on error handling path in gr_ep_init()
+ arm64: Use test_tsk_thread_flag() for checking TIF_SINGLESTEP
+ x86: math-emu: Fix up 'cmp' insn for clang ias
+ binder: Don't use mmput() from shrinker function.
+ usb: xhci-mtk: fix the failure of bandwidth allocation
+ usb: xhci: Fix ASM2142/ASM3142 DMA addressing
+ Revert "cifs: Fix the target file was deleted when rename failed."
+ staging: wlan-ng: properly check endpoint types
+ staging: comedi: addi_apci_1032: check INSN_CONFIG_DIGITAL_TRIG shift
+ staging: comedi: ni_6527: fix INSN_CONFIG_DIGITAL_TRIG support
+ staging: comedi: addi_apci_1500: check INSN_CONFIG_DIGITAL_TRIG shift
+ staging: comedi: addi_apci_1564: check INSN_CONFIG_DIGITAL_TRIG shift
+ serial: 8250: fix null-ptr-deref in serial8250_start_tx()
+ serial: 8250_mtk: Fix high-speed baud rates clamping
+ fbdev: Detect integer underflow at "struct fbcon_ops"->clear_margins.
+ vt: Reject zero-sized screen buffer size.
+ Makefile: Fix GCC_TOOLCHAIN_DIR prefix for Clang cross compilation
+ mm/memcg: fix refcount error while moving and swapping
+ io-mapping: indicate mapping failure
+ parisc: Add atomic64_set_release() define to avoid CPU soft lockups
+ 

[Kernel-packages] [Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs

[Andy Whitcroft]

Fundamentally you have to have a compiler to update the configuration on
an architecture.  We can however limit update/edit operations to the
architectures for which appropriate compilers are available.

Attached is a patch implementing this exclusion.  Could those affected
try applying this to their tree and retry the operation.  Please report
any testing back here.

** Patch added: 
"0001-UBUNTU-Packaging-kernelconfig-only-update-edit-confi.patch"
   
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+attachment/5397080/+files/0001-UBUNTU-Packaging-kernelconfig-only-update-edit-confi.patch

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

Title:
  debian/rules editconfigs does not work on s390x to change s390x only
  configs

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

Bug description:
  On s390x

  pull-lp-source linux-5.4
  cd linux-*
  fakeroot ./debian/rules clean
  ./debian/rules editconfig
  dh_testdir;
  /bin/bash -e debian/scripts/misc/kernelconfig editconfigs
  Do you want to edit config: amd64/config.flavour.generic? [Y/n] n
  ...
  scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found
  make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1
  make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2
  make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build'
  make[1]: *** [Makefile:179: sub-make] Error 2
  make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0'
  make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2

  And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available
  to build on s390x for amd64, and also I don't want to touch amd64
  configs. Only s390x ones.

  As a user, I should be able to rebuild ports architecture kernel with
  tweaked config for testing, self-hosted without cross-compilers.

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

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

[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog

[Dave Chiluk]

This is seems to be wider than simply Lenovo machines as my Dell
Precision 5540 is hitting this as well.

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

Title:
  Frequently getting thermal warnings and cpu throttling messages in
  syslog

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Nov  6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature 
above threshold, cpu clock throttled (total events = 50300) 


 
  Nov  6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature 
above threshold, cpu clock throttled (total events = 50300) 


 
  Nov  6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature 
above threshold, cpu clock throttled (total events = 58637) 


  
  Nov  6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core 
temperature/speed normal


 
  Nov  6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core 
temperature/speed normal


 
  Nov  6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package 
temperature/speed normal


  
  Nov  6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package 
temperature/speed normal


  
  Nov  6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package 
temperature/speed normal


  
  Nov  6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package 
temperature/speed normal


  
  Nov  6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature 
above threshold, cpu clock throttled (total events = 50316) 


 
  Nov  6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature 
above threshold, cpu clock throttled (total events = 50316) 


 
  Nov  6 11:40:35 fog 

[Kernel-packages] [Bug 1889137] Re: HWE kernel is missing firmwares

[Thomas Mayer]

For older kernels, there are no such warnings:
update-initramfs: Generating /boot/initrd.img-5.3.0-62-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
cryptsetup: WARNING: could not determine root device from /etc/fstab
update-initramfs: Generating /boot/initrd.img-4.15.0-112-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
cryptsetup: WARNING: could not determine root device from /etc/fstab
update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
cryptsetup: WARNING: could not determine root device from /etc/fstab
python3-distupgrade (1:18.04.38) wird eingerichtet ...
libglx-mesa0:amd64 (20.0.8-0ubuntu1~18.04.1) wird eingerichtet ...

Note that I'm still on 18.04.x, with hwe kernel installed

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

Title:
  HWE kernel is missing firmwares

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  After install linux-generic-hwe-18.04:

  update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
  W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module 
r8169
  W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module 
i915
  cd /lib/firmware/rtl_nicroot@h2:~# cd /lib/firmware/rtl_nic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-generic-hwe-18.04 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-7634.38~1595345317~20.04~a8480ad-generic 
5.4.41
  Uname: Linux 5.4.0-7634-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue Jul 28 10:43:18 2020
  HibernationDevice:
   #RESUME=UUID=9926e754-5beb-4353-ab1b-8e22f798efc6
   RESUME=UUID=aa434b5f-9af6-4b25-986e-216eb0e20a2e
  InstallationDate: Installed on 2018-06-28 (760 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. N551JK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-7634-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-7634-generic N/A
   linux-backports-modules-5.4.0-7634-generic  N/A
   linux-firmware  1.187.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-30 (58 days ago)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N551JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1889137] Re: HWE kernel is missing firmwares

[Thomas Mayer]

uname -a
Linux lat61 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux


sudo apt-get upgrade
reports:

update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
cryptsetup: WARNING: could not determine root device from /etc/fstab
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module 
i915
update-initramfs: Generating /boot/initrd.img-5.3.0-62-generic

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

Title:
  HWE kernel is missing firmwares

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  After install linux-generic-hwe-18.04:

  update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
  W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module 
r8169
  W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module 
i915
  cd /lib/firmware/rtl_nicroot@h2:~# cd /lib/firmware/rtl_nic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-generic-hwe-18.04 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-7634.38~1595345317~20.04~a8480ad-generic 
5.4.41
  Uname: Linux 5.4.0-7634-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue Jul 28 10:43:18 2020
  HibernationDevice:
   #RESUME=UUID=9926e754-5beb-4353-ab1b-8e22f798efc6
   RESUME=UUID=aa434b5f-9af6-4b25-986e-216eb0e20a2e
  InstallationDate: Installed on 2018-06-28 (760 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. N551JK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-7634-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-7634-generic N/A
   linux-backports-modules-5.4.0-7634-generic  N/A
   linux-firmware  1.187.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-30 (58 days ago)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JK.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N551JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1889474] [NEW] Bionic update: upstream stable patchset 2020-07-29

[Kamal Mostafa]

Public bug reported:


SRU Justification

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

   upstream stable patchset 2020-07-29
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Bionic update: upstream stable patchset 2020-07-29

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  In Progress

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:

 upstream stable patchset 2020-07-29
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support

[Jeff Lane]

Per Amir at Mellanox:
The kernel has been tested and It is good to go

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

Title:
  Devlink -  add RoCE disable kernel support

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]

  RoCE disable feature was added to the kernel v5.5.
  This feature was requested by Mellanox customers that use Ubuntu 20.04,
  and it's a very high important to deliver this feature to the customers
  in one of ubuntu 20.04 SRU.

  [SHORT DESCRIPTION]

  RoCE enablement state controls driver support for RoCE traffic.
  When RoCE is disabled, there is no gid table, only raw ethernet QPs are 
supported and traffic on the well known UDP RoCE port is handled as raw 
ethernet traffic.

  [Test Case]

  To change RoCE enablement state a user must change the driverinit
  cmode value and run devlink reload.

  User command examples:

  - Disable RoCE::

  $ devlink dev param set pci/:06:00.0 name enable_roce value false 
cmode driverinit
  $ devlink dev reload pci/:06:00.0

  - Read RoCE enablement state::

  $ devlink dev param show pci/:06:00.0 name enable_roce
    pci/:06:00.0:
    name enable_roce type generic
    values:
   cmode driverinit value true

  [Regression Potential]

  This feature shouldn't affect the regression because it's only adding support 
for
  RoCE enable/disable.
  Also,
  This feature was tested internally by Mellanox QA teams
  those tests logs/results are private unfortunately i can't share it here

  [Other Info]

  Feature patchset:

  4383cfcc65e7 net/mlx5: Add devlink reload
  32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
  94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
  b5a498baf929 IB/mlx5: Rename profile and init methods
  cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
  e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
  6c7295e13ffd devlink: Add new "enable_roce" generic device param

  All are in upstream in 5.5, so no pick into Groovy necessary

  Patches picked into this branch:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1877270-pull-roce-disable-from-5.5

  userspace:

  No userspace dependency on this. the feature  uses the devlink
  param functionality which already exists in UB20.04.

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

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

[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work

[Pierre rahbi]

Thats works !!! Thank you so much, I will pray for you tonight for a
long and happy life.

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

Title:
  DELL LATITUDE 5491 touchscreen doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I will really appreciate any help like said in summary my touchscreen
  doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

  Any idea ?

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ying   1977 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:45:20 2020
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5491
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0VK7YF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889468] Re: 20.04.1 selecting audio output device does not work on rpi

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1889468

** Tags added: iso-testing

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

Title:
  20.04.1 selecting audio output device does not work on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing 
that I can no longer select the audio output device with amixer. This used to 
be possible by using:
  amixer cset numid=3 2 for HDMI0
  amixer cset numid=3 3 for HDMI1
  amixer cset numid=3 1 for 3.5mm headphone jack

  However, now trying to set this gets the following error:
  amixer: Cannot find the given element from control default

  It seems that by default, it will now use the hdmi output for
  whichever one is connected, and will only output through the
  headphones if no hdmi device is connected.

  Kernel is:
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

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

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

[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work

[Kai-Heng Feng]

https://wiki.ubuntu.com/Kernel/KernelBootParameters#Permanently_Add_a_Kernel_Boot_Parameter

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

Title:
  DELL LATITUDE 5491 touchscreen doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I will really appreciate any help like said in summary my touchscreen
  doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

  Any idea ?

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ying   1977 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:45:20 2020
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5491
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0VK7YF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889468] [NEW] 20.04.1 selecting audio output device does not work on rpi

[Paul Larson]

Public bug reported:

Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing 
that I can no longer select the audio output device with amixer. This used to 
be possible by using:
amixer cset numid=3 2 for HDMI0
amixer cset numid=3 3 for HDMI1
amixer cset numid=3 1 for 3.5mm headphone jack

However, now trying to set this gets the following error:
amixer: Cannot find the given element from control default

It seems that by default, it will now use the hdmi output for whichever
one is connected, and will only output through the headphones if no hdmi
device is connected.

Kernel is:
Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

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

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

Title:
  20.04.1 selecting audio output device does not work on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing 
that I can no longer select the audio output device with amixer. This used to 
be possible by using:
  amixer cset numid=3 2 for HDMI0
  amixer cset numid=3 3 for HDMI1
  amixer cset numid=3 1 for 3.5mm headphone jack

  However, now trying to set this gets the following error:
  amixer: Cannot find the given element from control default

  It seems that by default, it will now use the hdmi output for
  whichever one is connected, and will only output through the
  headphones if no hdmi device is connected.

  Kernel is:
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Vicky Jadhav]

As per my previous comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/626

I have Lenovo z50 70

I had dual os installed on it.

1) Ubuntu 17x

2) Windows 8

As soon as I boot the laptop. It takes me to the GUNU GRUB Version
2.02~beta2-36Ubuntu3.22 black screen where I see Grub> prompt.

I usually type exit and it shows me boot screen, I then select windows 8
and use windows 8.

Earlier I have errased ubuntu partiations and now stuck with this Grub
screen only.

I am not sure how can I boot into Linux and fix this grub :(

Please help.

Regards,

Vicky Jadhav

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  If you have applied updates, and find that you can not boot the above
  fixed kernel because of Secure Boot and that the kernel is unsigned,
  but can still boot another kernel for your system; here's what you can
  do:

  1) Download 
http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed:
  $ wget 
http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed

  2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
  $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

  3) Reboot; you should now be able to load the new unsigned kernel that
  allows fixing firmware / SPI.

  4) Once you're satisfied that things work; boot to Ubuntu with a
  standard, signed kernel, and re-install the right GRUB version for
  your system:

  $ sudo grub-install

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     

[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work

[Pierre rahbi]

How I do that sir ? I'm still in my Linux learning period aha

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

Title:
  DELL LATITUDE 5491 touchscreen doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I will really appreciate any help like said in summary my touchscreen
  doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

  Any idea ?

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ying   1977 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:45:20 2020
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5491
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0VK7YF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1889114

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

Title:
  Ubuntu 18.04 Update Breaks KVM Wireless Mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 18.04 updates on July 21st.  This was a relatively
  small update with kernel related files from what I remember when
  installing the update.  Since the update, my KVM connected Logitech
  G305 wireless mouse functionality is broken.  The KVM keyboard and
  display still function correctly.

  I have 2 computers (desktop and laptop) connected to a KVM switch.
  The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro.  This
  KVM setup has worked since 2015 with versions of Linux Mint 17.x,
  Ubuntu 18.04, and Windows 7 Pro.

  The KVM (ConnectPro 14+)

  • Has a video cable from each computer to the KVM
  • Has a USB control cable from each computer to the KVM
  • Has a video cable from the KVM to the display
  • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the 
PS/2 keyboard
  • Has a KVM USB extension cable with the Logitech G305 wireless mouse 
receiver plugged into the USB connector.

  The extension cable is used to locate the receiver in proximity to the
  wireless mouse.

  I updated Ubuntu on the desktop on July 21st.  Since the update, I
  have lost wireless mouse functionality to the desktop.  But, I still
  have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop
  that was not updated.

  KVM Wireless Mouse function matrix (see attached image)

  I replaced the mouse battery, so that is not the problem.

  I verified that a wired mouse and the wireless Logitech G305 mouse
  both work properly when plugged directly into a USB port on the M83
  desktop.

  I replaced the wireless mouse with a wired mouse on the KVM mouse
  input, and the 4 configurations above worked OK (including the desktop
  with the July updates).

  So, I think that the July 21st update broke some function(s) in the
  handling of the wireless mouse USB controls signals between the
  desktop computer and the KVM switch.

  1. Can I provide any additional configuration information, and, if so, 
what terminal commands should I run?
  2. How do I recover from this problem?
  3. Can I back-out the update?  If so, how will this impact future updates?
  4. What else can I try to restore the wireless mouse functionality?

  
  Thank you in advance for your assistance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.37
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 27 14:29:36 2020
  InstallationDate: Installed on 2020-03-18 (130 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1889114] Re: Ubuntu 18.04 Update Breaks KVM Wireless Mouse

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu 18.04 Update Breaks KVM Wireless Mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 18.04 updates on July 21st.  This was a relatively
  small update with kernel related files from what I remember when
  installing the update.  Since the update, my KVM connected Logitech
  G305 wireless mouse functionality is broken.  The KVM keyboard and
  display still function correctly.

  I have 2 computers (desktop and laptop) connected to a KVM switch.
  The 2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro.  This
  KVM setup has worked since 2015 with versions of Linux Mint 17.x,
  Ubuntu 18.04, and Windows 7 Pro.

  The KVM (ConnectPro 14+)

  • Has a video cable from each computer to the KVM
  • Has a USB control cable from each computer to the KVM
  • Has a video cable from the KVM to the display
  • Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the 
PS/2 keyboard
  • Has a KVM USB extension cable with the Logitech G305 wireless mouse 
receiver plugged into the USB connector.

  The extension cable is used to locate the receiver in proximity to the
  wireless mouse.

  I updated Ubuntu on the desktop on July 21st.  Since the update, I
  have lost wireless mouse functionality to the desktop.  But, I still
  have functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop
  that was not updated.

  KVM Wireless Mouse function matrix (see attached image)

  I replaced the mouse battery, so that is not the problem.

  I verified that a wired mouse and the wireless Logitech G305 mouse
  both work properly when plugged directly into a USB port on the M83
  desktop.

  I replaced the wireless mouse with a wired mouse on the KVM mouse
  input, and the 4 configurations above worked OK (including the desktop
  with the July updates).

  So, I think that the July 21st update broke some function(s) in the
  handling of the wireless mouse USB controls signals between the
  desktop computer and the KVM switch.

  1. Can I provide any additional configuration information, and, if so, 
what terminal commands should I run?
  2. How do I recover from this problem?
  3. Can I back-out the update?  If so, how will this impact future updates?
  4. What else can I try to restore the wireless mouse functionality?

  
  Thank you in advance for your assistance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.37
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 27 14:29:36 2020
  InstallationDate: Installed on 2020-03-18 (130 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1889114] [NEW] Ubuntu 18.04 Update Breaks KVM Wireless Mouse

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed Ubuntu 18.04 updates on July 21st.  This was a relatively
small update with kernel related files from what I remember when
installing the update.  Since the update, my KVM connected Logitech G305
wireless mouse functionality is broken.  The KVM keyboard and display
still function correctly.

I have 2 computers (desktop and laptop) connected to a KVM switch.  The
2 computers are dual boot Ubuntu 18.04 and Windows 7 Pro.  This KVM
setup has worked since 2015 with versions of Linux Mint 17.x, Ubuntu
18.04, and Windows 7 Pro.

The KVM (ConnectPro 14+)

• Has a video cable from each computer to the KVM
• Has a USB control cable from each computer to the KVM
• Has a video cable from the KVM to the display
• Has a USB-to-PS/2 adapter connecting the KVM keyboard output to the PS/2 
keyboard
• Has a KVM USB extension cable with the Logitech G305 wireless mouse 
receiver plugged into the USB connector.

The extension cable is used to locate the receiver in proximity to the
wireless mouse.

I updated Ubuntu on the desktop on July 21st.  Since the update, I have
lost wireless mouse functionality to the desktop.  But, I still have
functionality with Win 7 Pro, and with the Ubuntu 18.04 laptop that was
not updated.

KVM Wireless Mouse function matrix (see attached image)

I replaced the mouse battery, so that is not the problem.

I verified that a wired mouse and the wireless Logitech G305 mouse both
work properly when plugged directly into a USB port on the M83 desktop.

I replaced the wireless mouse with a wired mouse on the KVM mouse input,
and the 4 configurations above worked OK (including the desktop with the
July updates).

So, I think that the July 21st update broke some function(s) in the
handling of the wireless mouse USB controls signals between the desktop
computer and the KVM switch.

1. Can I provide any additional configuration information, and, if so, what 
terminal commands should I run?
2. How do I recover from this problem?
3. Can I back-out the update?  If so, how will this impact future updates?
4. What else can I try to restore the wireless mouse functionality?


Thank you in advance for your assistance.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 27 14:29:36 2020
InstallationDate: Installed on 2020-03-18 (130 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic dist-upg kvm mouserade
-- 
Ubuntu 18.04 Update Breaks KVM Wireless Mouse
https://bugs.launchpad.net/bugs/1889114
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1815844] Change abandoned on os-brick (master)

[OpenStack Infra]

Change abandoned by Sean McGinnis (sean.mcgin...@gmail.com) on branch: master
Review: https://review.opendev.org/638639
Reason: After reading the bug report, I'm going to abandon this. Feel free to 
restore and update if there is anything else to be done.

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

Title:
  iscsi multipath dm-N device only used on first volume attachment

Status in OpenStack nova-compute charm:
  Invalid
Status in OpenStack Compute (nova):
  Invalid
Status in os-brick:
  Invalid
Status in linux package in Ubuntu:
  Expired

Bug description:
  With nova-compute from cloud:xenial-queens and use-multipath=true
  iscsi multipath is configured and the dm-N devices used on the first
  attachment but subsequent attachments only use a single path.

  The back-end storage is a Purestorage array.
  The multipath.conf is attached
  The issue is easily reproduced as shown below:

  jog@pnjostkinfr01:~⟫ openstack volume create pure2 --size 10 --type pure
  +-+--+
  | Field   | Value|
  +-+--+
  | attachments | []   |
  | availability_zone   | nova |
  | bootable| false|
  | consistencygroup_id | None |
  | created_at  | 2019-02-13T23:07:40.00   |
  | description | None |
  | encrypted   | False|
  | id  | e286161b-e8e8-47b0-abe3-4df411993265 |
  | migration_status| None |
  | multiattach | False|
  | name| pure2|
  | properties  |  |
  | replication_status  | None |
  | size| 10   |
  | snapshot_id | None |
  | source_volid| None |
  | status  | creating |
  | type| pure |
  | updated_at  | None |
  | user_id | c1fa4ae9a0b446f2ba64eebf92705d53 |
  +-+--+

  jog@pnjostkinfr01:~⟫ openstack volume show pure2
  ++--+
  | Field  | Value|
  ++--+
  | attachments| []   |
  | availability_zone  | nova |
  | bootable   | false|
  | consistencygroup_id| None |
  | created_at | 2019-02-13T23:07:40.00   |
  | description| None |
  | encrypted  | False|
  | id | e286161b-e8e8-47b0-abe3-4df411993265 |
  | migration_status   | None |
  | multiattach| False|
  | name   | pure2|
  | os-vol-host-attr:host  | cinder@cinder-pure#cinder-pure   |
  | os-vol-mig-status-attr:migstat | None |
  | os-vol-mig-status-attr:name_id | None |
  | os-vol-tenant-attr:tenant_id   | 9be499fd1eee48dfb4dc6faf3cc0a1d7 |
  | properties |  |
  | replication_status | None |
  | size   | 10   |
  | snapshot_id| None |
  | source_volid   | None |
  | status | available|
  | type   | pure |
  | updated_at | 2019-02-13T23:07:41.00   |
  | user_id| c1fa4ae9a0b446f2ba64eebf92705d53 |
  ++--+

  Add the volume to an instance:
  jog@pnjostkinfr01:~⟫ openstack server add volume T1 pure2
  jog@pnjostkinfr01:~⟫ openstack server show T1   

[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work

[Kai-Heng Feng]

Try boot with kernel parameter "usbcore.quirks=2386:350e:k"

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

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

Title:
  DELL LATITUDE 5491 touchscreen doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I will really appreciate any help like said in summary my touchscreen
  doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

  Any idea ?

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ying   1977 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:45:20 2020
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5491
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0VK7YF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889445] Re: Problem with touchscreen who doesn't work

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1889446
   DELL LATITUDE 5491 touchscreen doesn't work

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

Title:
  Problem with touchscreen who doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bus 001 Device 002: ID 2386:350e Raydium Corporation Raydium Touch System
  Dont work on DELL LATITUDE 5491 with I5-8400H as CPU
  I can strangely see him by ruuning "lsusb"

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

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

[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade

[Günter Neiß]

OK, I hope I do it now right.
Instead of using apt, I use
sudo dpkg -i ./*.deb
inside the folder where I have downloaded Your files.
uname -a
Then shows me a date that is close to Your message date (so it feels OK).

The problem with the 2 extra DEBs from Msg 25 are the same, so I can't
install them.

The results regarding the power off problem are (for all 3 versions):
BAD

Sorry for long messages, but I will give as mutch information as
possible.

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

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the problem 
will show up again.
  So I block these versions too.

  BTW: Due to the stuck I am able to see some other error messages that are not 
reported in the journal. The very last 3-5 lines show:
  shutdown [1]: Failed to wait for process: Protocol error
  These lines are present although in the working kernels, but hard to see, 
because the system powers down some ms after these lines are displayed!
  This problem seams to be solved more than one year ago in the upstream kernel!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gneiss 1929 F pulseaudio
   /dev/snd/controlC0:  gneiss 1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-02 (448 days ago)
  InstallationMedia:
   
  MachineType: Acer Aspire E5-771G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic 
root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth 
resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-61-generic N/A
   linux-backports-modules-5.3.0-61-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-771G
  dmi.product.sku: Aspire E5-771G_0884_1_23
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Zak B]

Still not working for me. @janitor can you please explain how to apply
the fix. In your text I dont see the bug number rnding in 610.

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

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

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

Bug description:
  [SRU Justification]

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

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

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

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1889445

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

Title:
  Problem with touchscreen who doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bus 001 Device 002: ID 2386:350e Raydium Corporation Raydium Touch System
  Dont work on DELL LATITUDE 5491 with I5-8400H as CPU
  I can strangely see him by ruuning "lsusb"

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  DELL LATITUDE 5491 touchscreen doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I will really appreciate any help like said in summary my touchscreen
  doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

  Any idea ?

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ying   1977 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:45:20 2020
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5491
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0VK7YF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889446] [NEW] DELL LATITUDE 5491 touchscreen doesn't work

[Pierre rahbi]

Public bug reported:

I will really appreciate any help like said in summary my touchscreen
doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

Any idea ?

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ying   1977 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 29 18:45:20 2020
InstallationDate: Installed on 2020-07-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Latitude 5491
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 0VK7YF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5491
dmi.product.sku: 0818
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  DELL LATITUDE 5491 touchscreen doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I will really appreciate any help like said in summary my touchscreen
  doesnt work on my dell lattitude 5491 with a I5-8400H cpu.

  Any idea ?

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ying   1977 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:45:20 2020
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5491
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: 02/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0VK7YF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889445] [NEW] Problem with touchscreen who doesn't work

[Pierre rahbi]

Public bug reported:

Bus 001 Device 002: ID 2386:350e Raydium Corporation Raydium Touch System
Dont work on DELL LATITUDE 5491 with I5-8400H as CPU
I can strangely see him by ruuning "lsusb"

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

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

Title:
  Problem with touchscreen who doesn't work

Status in linux package in Ubuntu:
  New

Bug description:
  Bus 001 Device 002: ID 2386:350e Raydium Corporation Raydium Touch System
  Dont work on DELL LATITUDE 5491 with I5-8400H as CPU
  I can strangely see him by ruuning "lsusb"

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

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

[Mauricio Faria de Oliveira]

Verification done on xenial-proposed.

The kernel in -proposed logs the block size change.
The kernel in -updates fails.

xenial-proposed:
---

$ uname -rv
4.4.0-187-generic #217-Ubuntu SMP Tue Jul 21 04:18:15 UTC 2020

$ apt-cache madison linux-image-4.4.0-187-generic 
linux-image-4.4.0-187-generic | 4.4.0-187.217 | 
http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages

$ sudo make-bcache --bdev $DEV --block 8k
...
[   88.514012] bcache: bcache_device_init() bcache0: sb/logical block 
size (8192) greater than page size (4096) falling back to device logical block 
size (512)
[   88.516852] bcache: register_bdev() registered backing device loop0

xenial-updates:
---

$ uname -rv
4.4.0-186-generic #216-Ubuntu SMP Wed Jul 1 05:34:05 UTC 2020

$ apt-cache madison linux-image-4.4.0-186-generic | grep updates
linux-image-4.4.0-186-generic | 4.4.0-186.216 | 
http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages

$ sudo make-bcache --bdev $DEV --block 8k
...
[   56.341127] bcache: register_bdev() registered backing device loop0
[   56.344996] BUG: unable to handle kernel NULL pointer dereference at 
0098
[   56.346996] IP: [] bdev_read_page+0x10/0xb0
...
[   56.379801] Call Trace:
[   56.380315]  [] do_mpage_readpage+0x52e/0x7a0
[   56.381452]  [] ? I_BDEV+0x20/0x20
[   56.382550]  [] ? lru_cache_add+0xe/0x10
[   56.383544]  [] mpage_readpages+0x112/0x190
[   56.384508]  [] ? I_BDEV+0x20/0x20
[   56.385369]  [] ? I_BDEV+0x20/0x20
[   56.386196]  [] ? alloc_pages_current+0x8c/0x110
[   56.387279]  [] blkdev_readpages+0x1d/0x20
[   56.388316]  [] 
__do_page_cache_readahead+0x199/0x240
[   56.389394]  [] 
force_page_cache_readahead+0xaa/0x100
[   56.390445]  [] page_cache_sync_readahead+0x3f/0x50
[   56.391600]  [] generic_file_read_iter+0x54a/0x6b0
[   56.392734]  [] blkdev_read_iter+0x35/0x40
[   56.393658]  [] new_sync_read+0x9e/0xe0
[   56.394620]  [] __vfs_read+0x29/0x40
[   56.395540]  [] vfs_read+0x86/0x130
[   56.396373]  [] SyS_read+0x5c/0xe0
[   56.397192]  [] entry_SYSCALL_64_fastpath+0x22/0xd0
...



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

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

[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade

[Günter Neiß]

Hm, the output of
sudo apt install ./*.deb
still states:
Hinweis: »linux-buildinfo-5.3.0-62-generic« wird an Stelle von 
»./linux-buildinfo-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
which means (I assume) that I did not install the packages You provided, 
instead I install the "normal" packages.
I don't know why this happens and how to prevent this.
It seams that apt simply ignores the given local DEB-files and althought ignore 
the apt-pinning I had made for this packages.
So maybe my former tests are done against the normal 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/1888570

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the problem 
will show up again.
  So I block these versions too.

  BTW: Due to the stuck I am able to see some other error messages that are not 
reported in the journal. The very last 3-5 lines show:
  shutdown [1]: Failed to wait for process: Protocol error
  These lines are present although in the working kernels, but hard to see, 
because the system powers down some ms after these lines are displayed!
  This problem seams to be solved more than one year ago in the upstream kernel!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gneiss 1929 F pulseaudio
   /dev/snd/controlC0:  gneiss 1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-02 (448 days ago)
  InstallationMedia:
   
  MachineType: Acer Aspire E5-771G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic 
root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth 
resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-61-generic N/A
   linux-backports-modules-5.3.0-61-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-771G
  dmi.product.sku: Aspire E5-771G_0884_1_23
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications 

[Kernel-packages] [Bug 1888405] Re: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols

[Robie Basak]

Hello James, or anyone else affected,

Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zfs-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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888405

Title:
  zfsutils-linux: zfs-volume-wait.service fails with locked encrypted
  zvols

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Groovy:
  Fix Released

Bug description:
  == SRU Justification Focal ==

  When an encrypted zvol is locked the zfs-volume-wait service does not
  start.  The /sbin/zvol_wait should not wait for links when the volume
  has property keystatus=unavailable.

  == Fix ==

  The attached patch in comment #1.

  == Test ==

  lock an encrypted zvol. without the fix the volume wait will block the
  boot. with the fix it is not blocked.

  == Regression Potential ==

  Limited to zvol wait - this change affects just the encrypted vols
  checking.

  -

  I was doing some experimentation with encrypted zvols and observed
  that the zfs-volume-wait.service systemd unit does not start if the
  encrypted zvol is locked.  The /sbin/zvol_wait should not wait for
  links when the volume has property keystatus=unavailable.  The
  attached patch seems to resolve the issue for me.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  # apt-cache policy zfsutils-linux
  zfsutils-linux:
    Installed: 0.8.3-1ubuntu12.1
    Candidate: 0.8.3-1ubuntu12.2
    Version table:
   0.8.3-1ubuntu12.2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 0.8.3-1ubuntu12.1 100
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade

[Günter Neiß]

After moving the DEBs 
linux-cloud-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb
and
linux-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb
away.
The installation works.
I assume this is OK, because formerly You suply only 6 files, but now 8, so I 
use only the same files as before.
I have to reboot now to tell the result

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

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the problem 
will show up again.
  So I block these versions too.

  BTW: Due to the stuck I am able to see some other error messages that are not 
reported in the journal. The very last 3-5 lines show:
  shutdown [1]: Failed to wait for process: Protocol error
  These lines are present although in the working kernels, but hard to see, 
because the system powers down some ms after these lines are displayed!
  This problem seams to be solved more than one year ago in the upstream kernel!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gneiss 1929 F pulseaudio
   /dev/snd/controlC0:  gneiss 1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-02 (448 days ago)
  InstallationMedia:
   
  MachineType: Acer Aspire E5-771G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic 
root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth 
resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-61-generic N/A
   linux-backports-modules-5.3.0-61-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-771G
  dmi.product.sku: Aspire E5-771G_0884_1_23
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1807974] Re: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370

[Weiguang Cui]

And sometimes it can be recovered, but not always...
[28023.806953] ath10k_pci :02:00.0: firmware crashed! (guid 
e4f47d81-ff1a-4173-9847-bbc2770ee439)
[28023.806968] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1a56:143a
[28023.806973] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[28023.808665] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
[28023.810003] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
4ac0889b
[28023.810009] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[28023.820139] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
[28023.820140] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[28023.820142] ath10k_pci :02:00.0: Copy Engine register dump:
[28023.820151] ath10k_pci :02:00.0: [00]: 0x00034400  11  11   3   3
[28023.820158] ath10k_pci :02:00.0: [01]: 0x00034800  23  23 356 357
[28023.820166] ath10k_pci :02:00.0: [02]: 0x00034c00  60  59  58  59
[28023.820173] ath10k_pci :02:00.0: [03]: 0x00035000  14  14  16  14
[28023.820181] ath10k_pci :02:00.0: [04]: 0x00035400 4335 4331 182 118
[28023.820188] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
[28023.820196] ath10k_pci :02:00.0: [06]: 0x00035c00   8   8   4   4
[28023.820203] ath10k_pci :02:00.0: [07]: 0x00036000   1   1   1   0
[28023.844105] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
[28023.926083] ieee80211 phy0: Hardware restart was requested
[28024.133190] ath10k_pci :02:00.0: unsupported HTC service id: 1536
[28024.236270] ath10k_pci :02:00.0: device successfully recovered
[28117.136734] wlp2s0: deauthenticating from 18:35:d1:ba:ad:67 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[28119.676844] ath10k_pci :02:00.0: unsupported HTC service id: 1536

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

Title:
  Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless
  regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
  on Dell XPS 13 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
  Cosmic. A handful of times per day, my wireless stops working ("?"
  appears in the icon in Network Manager). Turning wireless off and then
  on again, or suspending and waking the machine up, makes the wireless
  work again.

  dmesg output is as follows:

  $ dmesg | grep ath10k

  [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 
6317c652-4817-4fdd-b6d7-c7b8336e493f)
  [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [ 6646.270369] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
  [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800  29  29 106 107
  [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00  20  19  18  19
  [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000   8   8  10   8
  [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
  [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0   6   6
  [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
  [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
  [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered

  
  [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 
03393f2f-0ce1-4017-b711-40dd14f2ec11)
  [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [17641.848065] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [17641.848585] 

[Kernel-packages] [Bug 1807974] Re: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370

[Weiguang Cui]

Hi 
I have the same problem with XPS 13 9380, Ubuntu 20.04.1 LTS, 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/1807974

Title:
  Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless
  regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
  on Dell XPS 13 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
  Cosmic. A handful of times per day, my wireless stops working ("?"
  appears in the icon in Network Manager). Turning wireless off and then
  on again, or suspending and waking the machine up, makes the wireless
  work again.

  dmesg output is as follows:

  $ dmesg | grep ath10k

  [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 
6317c652-4817-4fdd-b6d7-c7b8336e493f)
  [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [ 6646.270369] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
  [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800  29  29 106 107
  [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00  20  19  18  19
  [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000   8   8  10   8
  [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
  [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0   6   6
  [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
  [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
  [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered

  
  [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 
03393f2f-0ce1-4017-b711-40dd14f2ec11)
  [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [17641.848065] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
  [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800   6   6 243 244
  [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00  53  52  51  52
  [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000   5   5   7   5
  [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
  [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0  30  30
  [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
  [17642.835601] ath10k_pci :02:00.0: device successfully recovered
  [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118

  I do not recall having any wireless issues before I upgraded (when
  this machine was running Bionic).

  Bug #1730331 - ath10k_pci: firmware crashed!
  Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
  could be related, but appear to be related to earlier releases, whereas my 
issue has appeared/become much worse on Cosmic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 

[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade

[Günter Neiß]

Sorry this one can't be installed.
Here is the output, in german, but I think You see what happens.

root@GNAspire:~/Schreibtisch/Temp/debs# sudo apt install ./*.deb
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
Hinweis: »linux-buildinfo-5.3.0-62-generic« wird an Stelle von 
»./linux-buildinfo-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Hinweis: »linux-cloud-tools-5.3.0-62-generic« wird an Stelle von 
»./linux-cloud-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Hinweis: »linux-headers-5.3.0-62« wird an Stelle von 
»./linux-headers-5.3.0-62_5.3.0-62.56_all.deb« gewählt.
Hinweis: »linux-headers-5.3.0-62-generic« wird an Stelle von 
»./linux-headers-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Hinweis: »linux-image-unsigned-5.3.0-62-generic« wird an Stelle von 
»./linux-image-unsigned-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Hinweis: »linux-modules-5.3.0-62-generic« wird an Stelle von 
»./linux-modules-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Hinweis: »linux-modules-extra-5.3.0-62-generic« wird an Stelle von 
»./linux-modules-extra-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Hinweis: »linux-tools-5.3.0-62-generic« wird an Stelle von 
»./linux-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb« gewählt.
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 linux-cloud-tools-5.3.0-62-generic : Hängt ab von: linux-cloud-tools-5.3.0-62 
ist aber nicht installierbar
 linux-tools-5.3.0-62-generic : Hängt ab von: linux-tools-5.3.0-62 ist aber 
nicht installierbar
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte 
Pakete.
root@GNAspire:~/Schreibtisch/Temp/debs# ll
insgesamt 72848
drwxr-xr-x 2 gneiss gneiss 4096 Jul 29 17:12 ./
drwxrwxr-x 4 gneiss gneiss 4096 Jul 25 17:23 ../
-rw-rw-r-- 1 gneiss gneiss   506060 Jul 29 17:11 
linux-buildinfo-5.3.0-62-generic_5.3.0-62.56_amd64.deb
-rw-rw-r-- 1 gneiss gneiss   289952 Jul 29 17:11 
linux-cloud-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb
-rw-rw-r-- 1 gneiss gneiss 11237476 Jul 29 17:12 
linux-headers-5.3.0-62_5.3.0-62.56_all.deb
-rw-rw-r-- 1 gneiss gneiss  1465188 Jul 29 17:11 
linux-headers-5.3.0-62-generic_5.3.0-62.56_amd64.deb
-rw-rw-r-- 1 gneiss gneiss  8953196 Jul 29 17:12 
linux-image-unsigned-5.3.0-62-generic_5.3.0-62.56_amd64.deb
-rw-rw-r-- 1 gneiss gneiss 13593492 Jul 29 17:12 
linux-modules-5.3.0-62-generic_5.3.0-62.56_amd64.deb
-rw-rw-r-- 1 gneiss gneiss 38240616 Jul 29 17:12 
linux-modules-extra-5.3.0-62-generic_5.3.0-62.56_amd64.deb
-rw-rw-r-- 1 gneiss gneiss   290080 Jul 29 17:12 
linux-tools-5.3.0-62-generic_5.3.0-62.56_amd64.deb

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

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the 

[Kernel-packages] [Bug 1871143] Re: Kernel crash during USB device enumeration or mounting

[Dan Halbert]

I brought this up on the linux-usb email list and was told it was more
likely to be an issue in the filesystem code. In addition, that code
(and the USB code) don't expect an MSC USB device to behave badly, and
there's no guarantee that if it does, Linux will not crash. In this
case, the filesystem changes abruptly out from under the filesystem
code.

linux-usb thread:
https://marc.info/?l=linux-usb=159387610928589=2

I suppose you can close this now. I wish Linux were more robust about
this, but it appears to be a "won't fix" from their point of view.

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

Title:
  Kernel crash during USB device enumeration or mounting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Device is an Adafruit microcontroller board running
  https://github.com/adafruit/circuitpython, using the TinyUSB USB
  stack: https://github.com/hathach/tinyusb.

  Device presents a composite USB device that includes MSC, CDC, HID, and MIDI
  Device was commanded to forcibly reformat its MSC FAT12 filesystem and then 
reset, which causes a USB reset and re-enumeration.

  This causes some USB kernel code to crash, much of the time, though
  not quite all the time.

  I work for Adafruit and the maintainer of TinyUSB also works for
  Adafruit, so we can provide further help to track this down.

  Attached is the dmesg file for the crash. I tried uploading the dump file 
from kdump, but launchpad is timing out. The dump file is available at:
  https://drive.google.com/open?id=1ka3ySSccEMRSmnYgI9X16IndPDmIKTD6

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  halbert1857 F pulseaudio
   /dev/snd/controlC2:  halbert1857 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  6 11:09:43 2020
  HibernationDevice: RESUME=UUID=55694d39-bafe-45f8-ba05-ea5d54a93a85
  InstallationDate: Installed on 2017-09-19 (929 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 7010
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=b3868153-c620-4efe-9dfc-8059dc6288a8 ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-03-08 (28 days ago)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A29
  dmi.board.name: 0WR7PY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA29:bd06/28/2018:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.sku: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

[Stéphane Gourichon]

Hi.

## Problem, check symptoms

We have a laptop here affected by the problem.

Following comment #172
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/172

> and please do not forget to also let us know what model laptop you
have.

* lshw says "ZenBook UX534FAC_UX533FAC" or simply "UX534FAC".
* Vendor identified it as UX534FA-A8094T.

> If possible please check all 4 of:
> 
> 1. Speakers
> 2. Headphones output
> 3. Internal mic.
> 4. Headset mic. (using a phone headset with builtin mic with a single T-R-R-S 
> connector)

Symptoms:

1. Speakers: no sound
2. Headphones output: no sound
3. Internal mic: works
4. Headset mic (no tested)

## Check workaround: success

> After testing please report back here what works (and what does not
work) after issueing the 4 above commands;

> hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
> hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774

Issuing the first two above allowed to get sound output.

> hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45
> hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289

Issuing the last two (right above) did not seem to have any effect.

Full test after the four commands:

1. Speakers: "perfect" sound
2. Headphones output: "perfect" sound
3. Internal mic: works
4. Headset mic: works

## Sound quality: as good as you can get

No artifacts like reported in #133.

"Perfect" means as good as can be given the physical speakers (e.g. not
much bass but this is normal).

## Next step: have a permanent fix

Some copy-paste instructions as to how to make this fix permanent would
be appreciated.  Else I can figure out some and share, e.g. from
https://askubuntu.com/questions/919054/how-do-i-run-a-single-command-at-
startup-using-systemd

## Thanks

Thanks everyone, including @j-w-r-degoede who shows that kernel
developers are taking care.

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1615209] Re: ip crashes after a few times adding and removing network namespaces

[Lucas Kanashiro]

I also tried to reproduce the mentioned failure in a clean Xenial
container with no success. Since this is an old bug and no one replied
to it for years I am removing the server-next tag.

** Tags removed: server-next

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

Title:
  ip crashes after a few times adding and removing network namespaces

Status in iproute2 package in Ubuntu:
  Expired

Bug description:
  # which ip
  /sbin/ip
  # valgrind ip netns add black2
  ==22804== Memcheck, a memory error detector
  ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==22804== Command: ip netns add black2
  ==22804== 
  ==22804== Invalid write of size 1
  ==22804==at 0x4031F43: memcpy (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C83: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804==  Address 0x4227094 is 0 bytes after a block of size 28 alloc'd
  ==22804==at 0x402D17C: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C5E: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804== 
  Cannot create namespace file "/var/run/netns/black2": File exists
  ==22804== 
  ==22804== HEAP SUMMARY:
  ==22804== in use at exit: 28 bytes in 1 blocks
  ==22804==   total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated
  ==22804== 
  ==22804== LEAK SUMMARY:
  ==22804==definitely lost: 0 bytes in 0 blocks
  ==22804==indirectly lost: 0 bytes in 0 blocks
  ==22804==  possibly lost: 0 bytes in 0 blocks
  ==22804==still reachable: 28 bytes in 1 blocks
  ==22804== suppressed: 0 bytes in 0 blocks
  ==22804== Rerun with --leak-check=full to see details of leaked memory
  ==22804== 
  ==22804== For counts of detected and suppressed errors, rerun with: -v
  ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

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

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

Re: [Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install

[Drew Erikson]

I've tried 5.7 and the problem seems to persist - weird, since I thought
that Kernel supported through TIger Lake and this machine runs an Ice Lake.

Drew Erikson
University of Minnesota - Twin Cities
Computer Science & Mathematics | 2020
eriks...@umn.edu


On Tue, Jul 28, 2020 at 9:20 PM Daniel van Vugt <1888...@bugs.launchpad.net>
wrote:

> It's *probably* a kernel bug and probably already fixed in a newer
> kernel. So you might want to try one of those:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1888571
>
> Title:
>   [Ice Lake] Screen flickering and glitching after install
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Intel integrated driver causes screen flickering with Ubuntu install.
>   Windows did not have this issue
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   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
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Jul 22 15:41:42 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if
> 00 [VGA controller])
>  Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a]
>   InstallationDate: Installed on 2020-07-22 (0 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: HP HP ENVY Laptop 13-ba0xxx
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic
> root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/04/2020
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.10
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 875A
>   dmi.board.vendor: HP
>   dmi.board.version: 07.34
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Envy
>   dmi.product.name: HP ENVY Laptop 13-ba0xxx
>   dmi.product.sku: 8KD13AV
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>   version.compiz: compiz N/A
>   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 N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+subscriptions
>

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

Title:
  [Ice Lake] Screen flickering and glitching after install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel integrated driver causes screen flickering with Ubuntu install.
  Windows did not have this issue

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 15:41:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a]
  InstallationDate: Installed on 2020-07-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ENVY Laptop 13-ba0xxx
  ProcEnviron:
   

[Kernel-packages] [Bug 1889410] Re: Integrated Webcam always stops working after updates

[Mijail Febres Soria]

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[PowerKiKi]

I just installed a fresh Xubuntu 20.04 (Linux 5.4.0-42-generic) on my
brand new Samsung Galaxy Book Ion NT950XCJ-X716A. And of course I do
experience the issues described here: very low volume on headphones and
no sound on speakers.

In pavucontrol, under "Output devices", I see 3 HDMI outputs, and the
last one is "Speaker + Headphones". I would have expected to see
something like "Built-in Audio Analog Stereo", but it's not there. Under
"Configuration", I would also expect something related to built-in, but
the only profiles available are "Play HiFi quality Music" and "Off".

>From reading this thread it seems that a (partial?) fix is on the way.
Is there a way for me try that patch already ?

And is there anything else I can do to help fix the remaining issues ? I
am not sure what log are useful and how to get them ?

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: 

[Kernel-packages] [Bug 1886390] Re: Fix an issue that HID devices are not scanned by Realtek 8822C

[Anthony Wong]

Already in groovy linux-firmware (1.188) according to the changelog.

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

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

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

Title:
  Fix an issue that HID devices are not scanned by Realtek 8822C

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

Bug description:
  [Impact]
  HID devices are not scanned by Realtek 8822C Bluetooth, so keyboard or mouse 
cannot connect to the host.

  [Fix]
  New firmware release for 8822C.

  [Test]
  HID devices can be scanned now. Pairing and connecting also work.

  [Regression Potential]
  Low. It's an upstream firmware release.

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1889410/+attachment/5396979/+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/1889410

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1889410/+attachment/5396965/+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/1889410

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

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

[Mijail Febres Soria]

apport information

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  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
  _MarkForUpload: True
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite S55-A
  dmi.product.sku: PSKK6U
  dmi.product.version: PSKK6U-00X00C
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1889410] Re: Integrated Webcam always stops working after updates

[Mijail Febres Soria]

apport information

** Tags added: apport-collected focal

** Description changed:

  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.
  
  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.
  
  As soon as an update is installed (this happens to me now in 20.04) the
  webcam stops working. At the begining, this problem could be solved by
  simply uninstalling cheese and restarting:
  
  sudo apt-get --purge remove cheese
  sudo apt-get install cheese
  
  But another update on the system and now the webcam is again dead. This
  happened also in 16.04 and 18.04. No solution on internet seems to work.
  For now I use Droidcam along my cellphone.
  
  I can provide further details.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  mijail 1834 F pulseaudio
+  /dev/snd/controlC0:  mijail 1834 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-07-08 (21 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ MachineType: TOSHIBA Satellite S55-A
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
+ 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
+ _MarkForUpload: True
+ dmi.bios.date: 09/19/2014
+ dmi.bios.vendor: TOSHIBA
+ dmi.bios.version: 1.90
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: VG10S
+ dmi.board.vendor: TOSHIBA
+ dmi.board.version: To be filled by O.E.M.
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: TOSHIBA
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00X00C:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
+ dmi.product.family: PEGA Family
+ dmi.product.name: Satellite S55-A
+ dmi.product.sku: PSKK6U
+ dmi.product.version: PSKK6U-00X00C
+ dmi.sys.vendor: TOSHIBA

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mijail 1834 F pulseaudio
   /dev/snd/controlC0:  mijail 1834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite S55-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=69ac813f-1c74-4767-ae9a-a6c7445b37f3 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
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1888924] Re: Battery drain during sleep. System suspended before kernel suspends all tasks

[Dr. Dennis]

I know if I understand. After I suspend, I can see that the system
thinks it's going into deep sleep, based typing this:

sudo journalctl | grep "PM: suspend" | tail -2

which returns:

Jul 29 14:58:15 SheRa kernel: PM: suspend entry (deep)
Jul 29 14:58:15 SheRa kernel: PM: suspend exit


As I understand it s2idle would be a less battery efficient state for it to 
report here.

However, the battery is still draining, and the cpus are still return
this "should not be sleeping"...

Also, I unfortunately cannot upgrade to 18.04 or 20.04, as a good number
of my bioinformatics pipelines are not compatible.

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

Title:
   Battery drain during sleep. System suspended before kernel suspends
  all tasks

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description: Ubuntu 16.04.6 LTS
  Release: 16.04

  I think this is similar to: Bug #1825636
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636

  Machine: Lenovo ThinkPad L390, fresh install

  Suspend drains the battery in approx 1 day.

  journalctl -b | grep -i "should not be sleeping" returns:
  "cache: parent cpu1 should not be sleeping" 

  for all cpus

  This is a real problem, as I rely on suspending frequently!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alice  2262 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd
  InstallationDate: Installed on 2019-11-22 (245 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2113 Acer, Inc 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20NR001LGE
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-112-generic N/A
   linux-backports-modules-4.15.0-112-generic  N/A
   linux-firmware  1.157.23
  Tags:  xenial
  Uname: Linux 4.15.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R10ET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NR001LGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L390
  dmi.product.name: 20NR001LGE
  dmi.product.version: ThinkPad L390
  dmi.sys.vendor: LENOVO

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1889410

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.

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

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

[Kernel-packages] [Bug 1889410] [NEW] Integrated Webcam always stops working after updates

[Mijail Febres Soria]

Public bug reported:

I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
since version 16.04.

Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
on this laptop, the integrated webcam and mic works perfectly as
intended.

As soon as an update is installed (this happens to me now in 20.04) the
webcam stops working. At the begining, this problem could be solved by
simply uninstalling cheese and restarting:

sudo apt-get --purge remove cheese
sudo apt-get install cheese

But another update on the system and now the webcam is again dead. This
happened also in 16.04 and 18.04. No solution on internet seems to work.
For now I use Droidcam along my cellphone.

I can provide further details.

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

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

Title:
  Integrated Webcam always stops working after updates

Status in linux package in Ubuntu:
  New

Bug description:
  I have a laptop Toshiba Satellite S55-A5279. I have been using Ubuntu
  since version 16.04.

  Everytime I do a clean installation of Ubuntu (16.04, 18.04 and 20.04)
  on this laptop, the integrated webcam and mic works perfectly as
  intended.

  As soon as an update is installed (this happens to me now in 20.04)
  the webcam stops working. At the begining, this problem could be
  solved by simply uninstalling cheese and restarting:

  sudo apt-get --purge remove cheese
  sudo apt-get install cheese

  But another update on the system and now the webcam is again dead.
  This happened also in 16.04 and 18.04. No solution on internet seems
  to work. For now I use Droidcam along my cellphone.

  I can provide further details.

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

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

[Kernel-packages] [Bug 1889375] Re: Fix right speaker of HP laptop

[Timo Aaltonen]

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

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

Title:
  Fix right speaker of HP laptop

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

Bug description:
  [Impact]
  Right speaker on an HP laptop doesn't work. 

  [Fix]
  Correctly enable the AMP to drive the right speaker.

  [Test]
  Open Gnome Control Center to test the right channel.
  I can hear the "front right" voice from the right speaker.
   
  [Regression Potential]
  Low. It's only affect a platform which is not on the market yet.

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

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

[Kernel-packages] [Bug 1886908] Re: Add support for Atlantic NIC firmware v4

[Timo Aaltonen]

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

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

Title:
  Add support for Atlantic NIC firmware v4

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

Bug description:
  [Impact]
  Atlantic NIC doesn't work.

  [Fix]
  Add firmware v4 support.

  [Test]
  With the patch applied, the driver probe success.
  Using iperf as a smoketest shows positive result.

  [Regression Potential]
  None. We were contacted by Marvell after I sent the patch to upstream,
  and they told us firmware v4 is created specifically for this upcoming
  platform. There are none firmware v4 in production.

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

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

[Kernel-packages] [Bug 1887909] Re: [SRU][F/OEM-5.6] add a new OLED panel support for brightness control

[Timo Aaltonen]

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

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

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

Title:
  [SRU][F/OEM-5.6] add a new OLED panel support for brightness control

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

Bug description:
  [Impact]
  Lenovo reported that a new OLED panel needs dpcd support to
  change screen brightness.

  [Fix]
  Add the panel ID in quirk list to support dpcd control.

  [Test]
  Verified on hardware by Lenovo.

  [Regression Potential]
  Low
  Upstream fix, clean cherry-picked.
  Add an ID only affected on specific hw.
  Unstable branch already got this patch.

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

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

[Kernel-packages] [Bug 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled

[Timo Aaltonen]

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

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

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

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

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

Title:
  cgroup refcount is bogus when cgroup_sk_alloc is disabled

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

Bug description:
  [Impact]
  When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as it's 
not incremented anymore, but decremented when sockets are closed.

  This might lead to crashes possibly because of use-after-free when
  packets are received as shown in LP #1886668.

  [Test case]
  Ran reproducer from comment #2.

  [Regression potential]
  We could break the use of cgroup bpf. The use of cgroup bpf looks to still be 
working from the reproducer.

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

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

[Kernel-packages] [Bug 1886785] Re: [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue.

[Timo Aaltonen]

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

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

** Changed in: linux-oem-5.6 (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/1886785

Title:
  [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue.

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

Bug description:
  [Impact]
  On AMD RENOIR gpu, after S3 backlight brightness can not be changed.

  [Fix]
  Pevious patch prevent loading iram, then dmcu can not work.
  Remove unused check to load iram right. Then backlight works well.

  [Test]
  Verified on hardware, after 10 times of S3, backlight can be changed by
  hotkey.

  [Regression Potential]
  Low
  Upstream fix, backports is minimal.
  RENOIR is only supported on oem-5.6, no focal patch.

  Harry Wentland (1):
Revert "drm/amd/display: disable dcn20 abm feature for bring up"

   drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 11 ---
   1 file changed, 4 insertions(+), 7 deletions(-)

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

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

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

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (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:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress
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 1888166] Re: soc/amd/renoir: change the module name to make it work with ucm3

[Timo Aaltonen]

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

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

Title:
  soc/amd/renoir: change the module name to make it work with ucm3

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

Bug description:
  [Impact]
  the alsa upstream worte the ucm3 files for amd renoir audio, but to
  load the ucm3, it depends on the kernel module name, and the upstream
  ucm3 needs the name snd-xxx, so we need to backport the patch
  from mainline kernel to change the kernel module name to meet ucm3
  requirement.

  [Fix]
  Backport 1 patch from upstream.

  [Test Case]
  boot the kernel with the patch on amd renoir machines (lenovo
  machines), the audio driver works well (via command line like
  aplay or areord), then upgrade the alsa-lib and alsa-ucm-conf to
  1.2.3.2, now we could see the audio devices from gnome, and they work
  well.

  [Regression Risk]
  Low, this SRU are only specific to soc/amd/renoir, and we already
  tested on 2 lenovo machines, their audio worked as before.

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

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

[Kernel-packages] [Bug 1852119] Re: Please add zfs modules to linux-raspi2

[Andreas Hasenack]

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

This is fixed already:

linux-meta-raspi (5.4.0.1014.15) focal; urgency=medium

  * linux-image-raspi provides zfs modules only for arm64 (LP: #1886682)
- [Packaging] Only provide zfs for arm64

 -- Juerg Haefliger   Thu, 09 Jul 2020 12:43:48
+0200

linux-meta-raspi (5.4.0.1014.14) focal; urgency=medium

  * Bump ABI 5.4.0-1014

  * Packaging resync (LP: #1786013)
- [Packaging] resync debian/dkms-versions from main package

  * Enable ZFS for Raspberry Pi arm64 (LP: #1884110)
- [Config] raspi: Enable zfs modules for arm64

 -- Kleber Sacilotto de Souza   Fri, 03 Jul
2020 17:52:25 +0200


I'm marking this as a duplicate.

** This bug has been marked a duplicate of bug 1884110
   Enable ZFS for Raspberry Pi arm64

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

Title:
  Please add zfs modules to linux-raspi2

Status in linux-raspi2 package in Ubuntu:
  Won't Fix

Bug description:
  The 4gb RPI4 is more than capable of handling zfs.
  ( Even zfs root can be enabled manually with arm64 eoan builds using a 
variant of the steps at 
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS . )

  Currently one has to install zfs-dkms for zfs support, but ideally one
  would have zfs modules come with the standard arm64 kernel so that one
  does not have to recompile zfs on the pi.

  Example:

  uname -a
  Linux rpi4 5.3.0-1011-raspi2 #12-Ubuntu SMP Fri Nov 1 09:07:06 UTC 2019 
aarch64 aarch64 aarch64 GNU/Linux
  @rpi4:~$ zpool status
pool: bpool
   state: ONLINE
  status: Some supported features are not enabled on the pool. The pool can
  still be used, but some features are unavailable.
  action: Enable all features using 'zpool upgrade'. Once this is done,
  the pool may no longer be accessible by software that does not support
  the features. See zpool-features(5) for details.
scan: scrub repaired 0B in 0 days 00:00:00 with 0 errors on Mon Nov 11 
13:50:14 2019
  config:

  NAME  STATE 
READ WRITE CKSUM
  bpool ONLINE  
 0 0 0
usb-Samsung_Flash_Drive_FIT_0309318110004882-0:0-part3  ONLINE  
 0 0 0

  errors: No known data errors

pool: rpool
   state: ONLINE
scan: scrub repaired 0B in 0 days 00:01:21 with 0 errors on Mon Nov 11 
13:51:39 2019
  config:

  NAMESTATE READ WRITE CKSUM
  rpool   ONLINE   0 0 0
sda4  ONLINE   0 0 0

  errors: No known data errors

  dkms status
  zfs, 0.8.1, 5.3.0-1011-raspi2, aarch64: installed

  @rpi4:~$ cat /proc/cpuinfo 
  processor   : 0
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  processor   : 1
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  processor   : 2
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  processor   : 3
  BogoMIPS: 108.00
  Features: fp asimd evtstrm crc32 cpuid
  CPU implementer : 0x41
  CPU architecture: 8
  CPU variant : 0x0
  CPU part: 0xd08
  CPU revision: 3

  Hardware: BCM2835
  Revision: c03111
  Serial  : ---
  Model   : Raspberry Pi 4 Model B Rev 1.1
  @rpi4:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:   3791 8832612  18 295
2836
  Swap:  4095   04095

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

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

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

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (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/1872383

Title:
  blk_update_request error when mount nvme partition

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Got below error message after upgraded Focal kernel(v5.4)
 [ 576.793852] blk_update_request: operation not supported error, dev 
nvme1n1, sector 4218887 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0

  This issue was introduced by below commit which added write zeros command
 6e02318eaea5 nvme: add support for the Write Zeroes command
  SK hynix firmware has a bug that it treats NLB as max value instead
  of a range, so the NLB passed isn't a valid value to the firmware.

  [Fix]
  Add a quirk to disable write zeros support

  [Test]
  Verified on the machine with SK hynix PC400 nvme machine.

  [Regression Potential]
  Low, it's a quirk to a specific PCI ID.

  ==

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

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

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

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

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board

[Launchpad Bug Tracker]

This bug was fixed in the package linux-raspi2-5.3 -
5.3.0-1030.32~18.04.2

---
linux-raspi2-5.3 (5.3.0-1030.32~18.04.2) bionic; urgency=medium

  * bionic/linux-raspi2-5.3: 5.3.0-1030.32~18.04.2 -proposed tracker
(LP: #109)

  * USB ports not working on the Pi 4 rev 1.4 board (LP: #1887156)
- usb: xhci: Raspberry Pi FW loader for VIA VL805

linux-raspi2-5.3 (5.3.0-1030.32~18.04.1) bionic; urgency=medium

  * bionic/linux-raspi2-5.3: 5.3.0-1030.32~18.04.1 -proposed tracker
(LP: #1887071)

  [ Ubuntu: 5.3.0-1030.32 ]

  * eoan/linux-raspi2: 5.3.0-1030.32 -proposed tracker (LP: #1887072)
  * eoan/linux: 5.3.0-64.58 -proposed tracker (LP: #1887088)
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux-raspi2-5.3 (5.3.0-1029.31~18.04.1) bionic; urgency=medium

  * bionic/linux-raspi2-5.3: 5.3.0-1029.31~18.04.1 -proposed tracker
(LP: #1885477)

  [ Ubuntu: 5.3.0-1029.31 ]

  * eoan/linux-raspi2: 5.3.0-1029.31 -proposed tracker (LP: #1885478)
  * CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan (LP: #1850876)
- media: bcm2835-unicam: Add support for raw14 formats
- media: bcm2835-unicam: Rework to not cache the list of active fmts
- media: bcm2835-unicam: Support unpacking CSI format to 16bpp
- media: bcm2835-unicam: Add support for luma/greyscale formats
- drm/vc4: Add support for YUV color encodings and ranges
- drm/vc4: Add support for H & V flips
- drm/vc4: Correct handling of rotation parameter in fkms
- configs: Add CONFIG_WIZNET_W5100=m and _SPI=m
- overlays: Add w5500 overlay
- bcm2711: Retain support for old dtbs
- media: bcm2835-unicam: Replace hard coded loop limit with a define
- media: bcm2835-unicam: Fix one-to-many mapping for YUYV formats
- dt-bindings: Add binding for the Infineon IRS1125 sensor
- media: i2c: Add a driver for the Infineon IRS1125 depth sensor
- configs: Add CONFIG_VIDEO_IRS1125 to the defconfigs
- dtoverlays: Add an overlay for the Infineon IRS1125
- rpi-wm8804-soundcard: Fixed MCLKDIV for Allo Digione
- dts: bcm2838: Disable DWC OTG block by default
- staging:bcm2835-codec: Add support for ENUM_FRAMESIZES
- staging: bcm2835-codec: Correct buffer type check on G_PARM
- staging: bcm2835-codec: Set default and error check timeperframe
- staging: bcm2835-codec: Fix imbalance in dma_buf_get/dma_buf_put
- drm:vc4 Added calls for firmware display blank/unblank
- configs: Add CGROUP_BPF and BPF_SYSCALL
- drm/v3d: Don't clear MMU control bits on exception
- v3d_drv: Handle missing clock more gracefully
- v3d_drv: Allow clock retrieval by name
- v3d_gem: Kick the clock so firmware knows we are using firmware clock
  interface
- clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks
- clk-raspberrypi: Also support v3d clock
- clk-bcm2835: Disable v3d clock
- config: Switch to upstream cpufreq driver
- raspberrypi-cpufreq: Only report integer pll divisor frequencies
- drm/v3d: drop use of drmP.h
- drm/v3d: Suppress all but the first MMU error
- drm/v3d: Plug dma_fence leak
- drm/v3d: Set dma_mask as well as coherent_dma_mask
- drm/v3d: Replace wait_for macros to remove use of msleep (#3510)
- Revert "UBUNTU: [config] raspi2: Revert "UBUNTU: [config] raspi2:
  CONFIG_DRM_V3D=m""
- [Config]: CLK_RASPBERRYPI=y
- [Config]: CONFIG_ARM_RASPBERRYPI_CPUFREQ=m
- [Config]: CONFIG_VIDEO_IRS1125=n
  * eoan/linux: 5.3.0-63.57 -proposed tracker (LP: #1885495)
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * The thread level parallelism would be a bottleneck when searching for the
shared pmd by using hugetlbfs (LP: #1882039)
- hugetlbfs: take read_lock on i_mmap for PMD sharing
  * Eoan update: upstream stable patchset 2020-06-30 (LP: #1885775)
- ipv6: fix IPV6_ADDRFORM operation logic
- net_failover: fixed rollback in net_failover_open()
- bridge: Avoid infinite loop when suppressing NS messages with invalid
  options
- vxlan: Avoid infinite loop when suppressing NS messages with invalid 
options
- tun: correct header offsets in napi frags mode
- Input: mms114 - fix handling of mms345l
- ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
- sched/fair: Don't NUMA balance for kthreads
- Input: synaptics - add a second working PNP_ID for Lenovo T470s
- drivers/net/ibmvnic: Update VNIC protocol version reporting
- powerpc/xive: Clear the page tables for the ESB IO mapping
- ath9k_htc: Silence undersized packet warnings
- RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
- x86/cpu/amd: Make erratum #1054 a legacy erratum
- perf probe: Accept the instance number of kretprobe event
- mm: add kvfree_sensitive() for freeing 

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

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (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/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:
  In Progress
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:
  In Progress
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@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1887734] Re: soc/amd/renoir: detect dmic from acpi table

[Timo Aaltonen]

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

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

Title:
  soc/amd/renoir: detect dmic from acpi table

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

Bug description:
  Groovy kernel already merged the patchset

  [Impact]
  On the amd renoir machines, there is possibility that they have no dmic
  from the hardware desgin, but the driver register a dmic unconditionally,
  to avoid it, add the dmic detection code in the driver.

  [Fix]
  Backport 3 patches from upstream.

  [Test Case]
  On the 3 Lenovo ADM renoir machines, boot the kernel with this patchset,
  all dmic could be detected and registered as before. Disable the dmic
  in the BIOS, the driver can't detect the dmic and the dmic is not
  registered in the driver.

  [Regression Risk]
  Low, this SRU are only specific to soc/amd/renoir, and we already
  tested on 3 lenovo machines, they worked as expected.

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

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

[Kernel-packages] [Bug 1888331] Re: Wakeup the system by touching the touchpad

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (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/1888331

Title:
  Wakeup the system by touching the touchpad

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

Bug description:
  [Impact]
  Can't wake up by touching the touchpad.

  [Fix]
  1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
    gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If 
irq_disable
    callback is implemented then genirq takes unlazy path to disable irq. 
Underlying irqchip
    may not want to implement irq_disable callback to lazy disable irq
    when client drivers invokes disable_irq(). By overriding irq_disable 
callback,
    gpiolib ends up always unlazy disabling IRQ.
    Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
    if irqchip implemented irq_disable. In cases where irq_disable is not
    implemented irq_mask is overridden. Similarly override irq_enable callback
    only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
  2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
     also the default behavior on other OSes.
     However, if touchpad and touchscreen contact to each other when lid is
     closed, wakeup events can be triggered inadventertly.
     So let's disable the wakeup by default, but enable the wakeup capability
     so users can enable it at their own discretion.

  [test]
  With the patch and manually enable HID's power/wakeup, the system can wake up 
by touching the touchpad.

  [Regression Potential]
  Low. The two patches are already landed in the upstream.

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

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

[Kernel-packages] [Bug 1888375] Re: Restart the machine successfully after suspend

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (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/1888375

Title:
  Restart the machine successfully after suspend

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

Bug description:
  [Impact]
  After suspend then restart, the System would hang during shutdown.

  [Fix]
  The commit has pushed to upstream but still wait for the maintainer of IOMMU 
to apply.
  
https://lore.kernel.org/linux-iommu/20200721001713.24282-1-baolu...@linux.intel.com/

  Skip the TE disabling for the quirky gfx dedicated iommu and
  the system would not hang during shutdown.

  [test]
  With the patch, the machine restart successfully.

  [Regression Potential]
  low, the patch just skip the TE disabling and wouldn't affect the normal 
usage.

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

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

[Kernel-packages] [Bug 1889306] Re: Resuming from deep suspend on Thinkpad T14 crashes system (readonly filesystem)

[AaronMa]

Set Invalid, Thanks for your shared info.

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

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

Title:
  Resuming from deep suspend on Thinkpad T14 crashes system (readonly
  filesystem)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Make sure that "deep" suspend is used instead of `s2idle` suspend (`echo 
deep | sudo tee /sys/power/mem_sleep`). This is always the case when the 
"Power->Suspend State" is set to "Linux" instead of "Windows 10" in the BIOS.
  2. Trigger suspend, e.g. with GUI or `systemctl suspend -i`
  3. System suspends successfully. Power light starts fading in and out, as it 
should. 
  4. Wake up the system. This is only possible with the power button instead of 
keys, which is a difference from `s2idle` suspends.
  5. Unlock lock screen
  6. Notice that the system will behave buggy/abnormal as the filesystem is 
remounted as read-only. Shortly after resuming, applications will start to 
crash or show nonsensical output.

  Expected behavior:
  (From step 4) System wakes up and can be used normally. The main filesystem 
should of course be writable.

  Ubuntu version: 20.04, latest updates as of 2020-07-28
  Kernel: Linux nicolai-t14 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  Computer: Thinkpad T14 (Intel), M2 NVMe SSD
  `dmesg | grep ACPI | grep supports`: [0.511722] ACPI: (supports S0 S3 S4 
S5)
  tlp: tlp was running during some tests but deactivated during others. The 
problem still appeared in both cases.

  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:  nicolai1472 F pulseaudio
   /dev/snd/controlC0:  nicolai1472 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 28 21:55:33 2020
  HibernationDevice:
   RESUME=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816
   # Resume from /swapfile
  InstallationDate: Installed on 2020-06-12 (46 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20S1S06C00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c ro 
resume=UUID=d4f9a6e6-e186-4b67-92fc-fb3bdf13921c resume_offset=34816 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: 04/27/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2XET15W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20S1S06C00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2XET15W(1.05):bd04/27/2020:svnLENOVO:pn20S1S06C00:pvrThinkPadT14Gen1:rvnLENOVO:rn20S1S06C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20S1S06C00
  dmi.product.sku: LENOVO_MT_20S1_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable

[Paul Menzel]

It looks like microcode update revision 0xd6 is still the officially
shipped version.

The often occurring hangs without the power cable plugged in, are still
happening.

Booting with `maxcpus=1` and adding

earlyprintk=efi earlycon=efifb debug

to the Linux command, the last messages are:

[…]
random: crng done (trusting CPU's manufacturer)
Console: colour dummy device 80x25
printk: console [tty0] enabled
printk: bootconsole [efifb0] disabled

So, it might indeed be related to bug 1862751.

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

Title:
  Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without
  plugged in power cable

Status in intel-microcode package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Already present reported in project *dell-sputnik*. (Note, it happened
  here also without suspend/resume.):

  1.  https://bugs.launchpad.net/dell-sputnik/+bug/1661741
  2.  Quote from 
https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26:

  > A similar bug affects several Dell laptop models:
  > - Dell 5480/5488 :
  >  https://bugs.launchpad.net/dell-sputnik/+bug/1866343
  > - Dell E5470 :
  > https://bugs.launchpad.net/dell-sputnik/+bug/1661741
  > (Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 
is not fixed; it has been changed, by error, to fixed. Please, it will be nice 
if somebody can change the status to "confirmed")
  > - Dell 7740 :
  > https://bugs.launchpad.net/dell-sputnik/+bug/1871491
  >
  > I suppose that the bug can also affect Dell precision 7730

  After experiencing this already on the Dell Latitude 5480/5488
  (https://bugs.launchpad.net/dell-sputnik/+bug/1866343), we have seen
  this now too with the Dell Precision 3540 (with dedicated AMD graphics
  card).

  Without the power cord plugged in, the system started fine, then
  updating packages, including the Linux kernel, turning the system off,
  and right back on, it went to GRUB, and GRUB was able to load Linux
  and initrd, and starting Linux it hung.

  Num lock key didn’t respond (but also didn’t blink – no idea if this
  should work), and Ctrl + Alt + Del didn’t work either. So, the system
  had to be powered off by pressing the power button for some (ten(?))
  seconds.

  Subsequent tries didn’t help, until we remembered the issues with the
  other device, and plugging in the power cord fixed it.

  With the power cable unplugged, it didn’t boot.

  The state of the connected power cable only mattered, when starting
  the Linux kernel. That means, plugging it in, when GRUB was active,
  the system booted. Removing the cable, when GRUB was running, Linux
  hung.

  I tried to get Linux messages, but `debug nomodeset earlyprintk=efi`
  didn’t get Linux to output any messages.

  ### Workarounds ###

  I was able to get Linux booting by adding either one of the following
  Linux kernel parameters.

  1.  `maxcpus=1` (once it started with `maxcpus=2`)
  2.  `nosmp`
  2.  `acpi=off`
  3.  `nolapic`

  In this state, there was only one CPU online. Trying to bring one more
  online, the system always froze instantly.

  echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online

  (Nothing in pstore either.) (Where maxcpus=2` worked, we were able to
  bring a third CPU online, but the system froze when trying the
  fourth.)

  ### Reproducibilty ###

  Letting the system sit over night, and trying again in the morning,
  unfortunately, we did *not* test without a power cable plugged in, as
  we had an idea to test the non-USB-Type-C power cable. With that the
  system started.

  Powering the system off, and unplugging the cable, the system booted
  without issues. So something changed.

  We weren’t able to get it into a state, where it doesn’t boot in the
  last hour, but we would like this investigated, as we are giving these
  systems to our users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1883065/+subscriptions

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889384] Re: ASPM not enabled on child devices behind VMD controller

[You-Sheng Yang]

** Attachment added: "lspci-vvn"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384/+attachment/5396930/+files/lspci-vvn

** Description changed:

- TBD.
- --- 
+ ASPM of VMD devices is not automatically enabled even it's said capable
+ in its Link Capabilities Register.
+ 
+ $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
+ 1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
+   LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
+ 1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
+   LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  u  1831 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.6.0-1020-oem N/A
-  linux-backports-modules-5.6.0-1020-oem  N/A
-  linux-firmware  1.187.2
+  linux-restricted-modules-5.6.0-1020-oem N/A
+  linux-backports-modules-5.6.0-1020-oem  N/A
+  linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session 

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1889384] Re: ASPM not enabled on child devices behind VMD controller

[You-Sheng Yang]

Patch originated from khfeng, RFCing in linux-pci:
https://lore.kernel.org/linux-
pci/20200728161321.38229-1-jonathan.derr...@intel.com/

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1889384/+attachment/5396920/+files/Lsusb-t.txt

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

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

[You-Sheng Yang]

apport information

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

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

Title:
  ASPM not enabled on child devices behind VMD controller

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

Bug description:
  ASPM of VMD devices is not automatically enabled even it's said
  capable in its Link Capabilities Register.

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express])
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1831 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.5.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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