[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Blastoff]

** Tags added: regression-update

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu

  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

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

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

[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD

[You-Sheng Yang]

It takes 50+ patches to back port to 5.3 eoan kernel, so it will
definitely take more for 5.0 oem-osp1. This is a risk we cannot take.
Suggest to upgrade to 5.6-oem instead.

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

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

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

Title:
  [ICL] TC port in legacy/static mode can't be detected due TCCOLD

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

Bug description:
  When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port
  can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected"

  The issue doesn't happen when SoC is not in PC10.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.6.0-050600rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1485 F pulseaudio
u  2075 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Vostro 14 5401
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 
root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M
  ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1043-oem-osp1 N/A
   linux-backports-modules-5.0.0-1043-oem-osp1  N/A
   linux-firmware   1.173.16
  Tags:  bionic
  Uname: Linux 5.0.0-1043-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 89.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14 5401
  dmi.product.sku: 09EA
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Blastoff]

Seems like this was supposed to be fixed by
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1850654

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu

  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

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

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

[Kernel-packages] [Bug 1874230] Re: Intel Wireless 7265 [8086:095a] subsystem [8086:5110] WiFi is extremely slow

[You-Sheng Yang]

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

Title:
  Intel Wireless 7265 [8086:095a] subsystem [8086:5110] WiFi is
  extremely slow

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a fresh install of Ubuntu 20.04, WiFi connection is extremely slow.

  For example loading https://ubuntu.com takes 200 seconds on WiFi and 2 
seconds over ethernet.
  On the same computer, Windows 10 has no such problems with WiFi.

  The chipset of the laptop is an Intel Corporation Wireless 7265 [8086:095a] 
(rev 59)
   using the iwlwifi driver.

  This issue was not present on my previous Ubuntu 18.04 install.

  The issue is present on the latest 5.4.0-26-generic kernel and is also
  present on the -25 -24 kernels.

  
  Here is a dmesg log during boot: https://paste.ubuntu.com/p/9ccMnSDcc7/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonathan   1423 F pulseaudio
   /dev/snd/pcmC0D0p:   jonathan   1423 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 12:17:45 2020
  IwConfig:
   lono wireless extensions.
   
   enp3s0f1  no wireless extensions.
   
   wlp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0fcf:1008 Dynastream Innovations, Inc. ANTUSB2 Stick
   Bus 001 Device 002: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N551VW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=dc56ad9d-b29d-48bd-804d-44e027bccd24 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551VW.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551VW.205:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnN551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N551VW
  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/backport-iwlwifi-dkms/+bug/1874230/+subscriptions

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

[Kernel-packages] [Bug 1874230] Re: WiFi is extremely slow

[You-Sheng Yang]

Hi, please try removing backport-iwlwifi-dkms package:

  $ sudo apt purge backport-iwlwifi-dkms

** Also affects: backport-iwlwifi-dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: hwe-networking-wifi

** Summary changed:

-  WiFi is extremely slow
+ Intel Wireless 7265 [8086:095a] subsystem [8086:5110] WiFi is extremely slow

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

Title:
  Intel Wireless 7265 [8086:095a] subsystem [8086:5110] WiFi is
  extremely slow

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Ubuntu 20.04, WiFi connection is extremely slow.

  For example loading https://ubuntu.com takes 200 seconds on WiFi and 2 
seconds over ethernet.
  On the same computer, Windows 10 has no such problems with WiFi.

  The chipset of the laptop is an Intel Corporation Wireless 7265 [8086:095a] 
(rev 59)
   using the iwlwifi driver.

  This issue was not present on my previous Ubuntu 18.04 install.

  The issue is present on the latest 5.4.0-26-generic kernel and is also
  present on the -25 -24 kernels.

  
  Here is a dmesg log during boot: https://paste.ubuntu.com/p/9ccMnSDcc7/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonathan   1423 F pulseaudio
   /dev/snd/pcmC0D0p:   jonathan   1423 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 12:17:45 2020
  IwConfig:
   lono wireless extensions.
   
   enp3s0f1  no wireless extensions.
   
   wlp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0fcf:1008 Dynastream Innovations, Inc. ANTUSB2 Stick
   Bus 001 Device 002: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N551VW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=dc56ad9d-b29d-48bd-804d-44e027bccd24 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551VW.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551VW.205:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnN551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N551VW
  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/backport-iwlwifi-dkms/+bug/1874230/+subscriptions

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

[Kernel-packages] [Bug 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh

[You-Sheng Yang]

** Tags added: hwe-networking-wifi

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

Title:
  iwlwifi intel ax201 crashing on intel nuc10i7fnh

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The intel iwlwifi firmware will crash when you insert a device into
  the thunderbolt3 port, and this will be trigger probabilistically.

  wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354
  Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
  Linux-firmware version: 1.187
  thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 2C 2018] (rev 06)

  dmesg output:
  [  103.777908] pcieport :00:1c.0: PME: Spurious native interrupt!
  [  103.777918] pcieport :00:1c.0: PME: Spurious native interrupt!
  [  104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using 
xhci_hcd
  [  104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, 
bcdDevice=15.32
  [  104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, 
SerialNumber=2
  [  104.147194] usb 4-1: Product: USB3.0 Card Reader
  [  104.147197] usb 4-1: Manufacturer: Generic
  [  104.147199] usb 4-1: SerialNumber: 1532
  [  104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected
  [  104.183952] scsi host3: usb-storage 4-1:1.0
  [  104.184172] usbcore: registered new interface driver usb-storage
  [  104.187897] usbcore: registered new interface driver uas
  [  105.217035] scsi 3:0:0:0: Direct-Access Generic  STORAGE DEVICE   1532 
PQ: 0 ANSI: 6
  [  105.217792] sd 3:0:0:0: Attached scsi generic sg1 type 0
  [  105.233978] sd 3:0:0:0: [sdb] Attached SCSI removable disk
  [  109.998995] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [  109.999102] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [  109.999111] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [  109.999119] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [  109.999128] iwlwifi :00:14.3: 0x4435 | ADVANCED_SYSASSERT  
  [  109.999135] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0
  [  109.999142] iwlwifi :00:14.3: 0x | trm_hw_status1
  [  109.999148] iwlwifi :00:14.3: 0x004CA228 | branchlink2
  [  109.999154] iwlwifi :00:14.3: 0x0E26 | interruptlink1
  [  109.999161] iwlwifi :00:14.3: 0x0E26 | interruptlink2
  [  109.999168] iwlwifi :00:14.3: 0x000161A0 | data1
  [  109.999174] iwlwifi :00:14.3: 0xDEADBEEF | data2
  [  109.999180] iwlwifi :00:14.3: 0xDEADBEEF | data3
  [  109.999186] iwlwifi :00:14.3: 0xF90167B5 | beacon time
  [  109.999192] iwlwifi :00:14.3: 0x51938809 | tsf low
  [  109.999199] iwlwifi :00:14.3: 0x0010 | tsf hi
  [  109.999205] iwlwifi :00:14.3: 0x | time gp1
  [  109.999211] iwlwifi :00:14.3: 0x064A1430 | time gp2
  [  109.999217] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [  109.999224] iwlwifi :00:14.3: 0x0030 | uCode version major
  [  109.999231] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
  [  109.999239] iwlwifi :00:14.3: 0x0351 | hw version
  [  109.999245] iwlwifi :00:14.3: 0x00C89004 | board version
  [  109.999252] iwlwifi :00:14.3: 0x069E001C | hcmd
  [  109.999259] iwlwifi :00:14.3: 0x8002 | isr0
  [  109.999265] iwlwifi :00:14.3: 0x0100 | isr1
  [  109.999271] iwlwifi :00:14.3: 0x08F2 | isr2
  [  109.999278] iwlwifi :00:14.3: 0x04C1FFCC | isr3
  [  109.999284] iwlwifi :00:14.3: 0x | isr4
  [  109.999290] iwlwifi :00:14.3: 0x069D001C | last cmd Id
  [  109.999297] iwlwifi :00:14.3: 0x8B70 | wait_event
  [  109.999304] iwlwifi :00:14.3: 0x4208 | l2p_control
  [  109.999310] iwlwifi :00:14.3: 0x2020 | l2p_duration
  [  109.999317] iwlwifi :00:14.3: 0x033F | l2p_mhvalid
  [  109.999324] iwlwifi :00:14.3: 0x00E6 | l2p_addr_match
  [  109.999331] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel
  [  109.999337] iwlwifi :00:14.3: 0x | timestamp
  [  109.999344] iwlwifi :00:14.3: 0xB8DC | flow_handler
  [  109.999391] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [  109.999398] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [  109.999406] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [  109.999413] iwlwifi :00:14.3: 0x | umac branchlink1
  [  109.999420] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
  [  109.999427] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink1
  [  109.999434] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink2
  [  109.999441] iwlwifi :00:14.3: 0x0400 | umac data1
  [  109.999447] iwlwifi :00:14.3: 0x8048DBD2 | umac data2
  [  109.999454] iwlwifi :00:14.3: 0x | umac data3
  [  109.999461] iwlwifi :00:14.3: 0x0030 | umac major
  [  109.

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Dexuan Cui]

I also tried xrdp mode and the VM booted up to the xrdp login window in
14 seconds, which is faster than the "native Xorg GUI mode" (which needs
30s)

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1874305] Re: Wifi goes down when change bluetooth configuration

[You-Sheng Yang]

** Tags added: hwe-bluetooth hwe-networking-wifi

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

Title:
  Wifi goes down when change bluetooth configuration

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  WiFi connection goes down when having a Bluetooth headset connected and 
change from A2DP to HSP. 
  The connection goes down instantly. If you change back to A2DP connection 
works again, but in some cases it goes down forever till you disconnect from 
the current WiFi and connect again.

  [How to reproduce]
   1. connect a Bluetooth headset and change from A2DP to HSP.

  [System Info]
   Ubuntu 5.4.0-24.28-generic 5.4.30
   03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
   
   No LSB modules are available.
   Distributor ID:  Ubuntu
   Description: Ubuntu 20.04 LTS
   Release: 20.04
   Codename:focal

  [DMESG info]
  348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072
  [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48
  [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0

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

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

[Kernel-packages] [Bug 1813878] Re: lxc test failed on Azure T-4.15

[Po-Hsu Lin]

** Tags added: sru-20200406

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

Title:
  lxc test failed on Azure T-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  There are multiple failures in the lxc test for Azure T-4.15

   FAIL: lxc-tests: /usr/bin/lxc-test-autostart
   FAIL: lxc-tests: /usr/bin/lxc-test-cgpath
   FAIL: lxc-tests: /usr/bin/lxc-test-concurrent
   FAIL: lxc-tests: /usr/bin/lxc-test-createtest
   FAIL: lxc-tests: /usr/bin/lxc-test-destroytest
   FAIL: lxc-tests: /usr/bin/lxc-test-device-add-remove
   FAIL: lxc-tests: /usr/bin/lxc-test-ubuntu
   FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
   FAIL: lxc-tests: /usr/bin/lxc-test-usernic
   FAIL: python3: API

  * lxc-test-autostart
   ---
   Setting up the GPG keyring
   Downloading the image index
   Downloading the rootfs
   Downloading the metadata
   The image cache is now ready
   Unpacking the rootfs
   
   ---
   You just created an Ubuntu trusty amd64 (20190129_07:43) container.
   
   To enable SSH, run: apt install openssh-server
   No default root or user password are set by LXC.
   Error starting container: lxc-test-auto
   Container didn't start
   FAIL

  * lxc-test-cgpath
   setting root password to "root"
   Password for 'root' changed
   cgpath.c:69 lxc_cmd_get_cgroup_path returned NULL
   lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container 
"lxctest1": Operation not permitted.

  
  * lxc-test-concurrent
   Iteration 1/1 maxfd:18
   Executing (create) for 5 containers...
   Executing (start) for 5 containers...
   lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container 
"lxc-test-concurrent-3": Operation not permitted.
   Stopping the container (lxc-test-concurrent-3) failed...
   lxc_container: lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop 
container "lxc-test-concurrent-1": Operation not permitted.
   Stopping the container (lxc-test-concurrent-1) failed...
   lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container 
"lxc-test-concurrent-0": Operation not permitted.
   Stopping the container (lxc-test-concurrent-0) failed...
   thread returned error 1

  * /lxc-test-destroytest
  75: lxctest1 thought it was defined

  * lxc-test-device-add-remove
   lxc_container: lxccontainer.c: add_remove_device_node: 3260 set_cgroup_item 
failed while adding the device node
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  * lxc-test-ubuntu
   lxc-start: lxc_start.c: main: 341 The container failed to start.
   lxc-start: lxc_start.c: main: 343 To get more details, run the container in 
foreground mode.
   lxc-start: lxc_start.c: main: 345 Additional information can be obtained by 
setting the --logfile and --logpriority options.
   Failed starting ubuntu container

  * lxc-test-unpriv
  see bug 1803686

  * lxc-test-usernic
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   /usr/sbin/deluser: The user `usernic-user' does not exist.
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   Failed to open connection to "unix:path=/sys/fs/cgroup/cgmanager/sock" 
message bus: Failed to connect to socket /sys/fs/cgroup/cgmanager/sock: 
Connection refused
   FAIL

  * python3: API
   Using image from local cache
   Unpacking the rootfs
   
   ---
   You just created an Ubuntu trusty amd64 (20190129_07:43) container.
   
   To enable SSH, run: apt install openssh-server
   No default root or user password are set by LXC.
   Getting instance for 'f13fde32-245e-11e9-8017-000d3a942bc7'
   Creating rootfs using 'download', arch=amd64
   Testing the configuration
   Testing the networking
   Starting the container
   Traceback (most recent call last):
 File "/tmp/tmp.Y8MLapGtid", line 102, in 
   assert(container.init_pid > 1)
   AssertionError

  Please see the attachment for the complete test log

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.15.0-1036-azure 4.15.0-1036.38~14.04.2
  ProcVersionSignature: User Name 4.15.0-1036.38~14.04.2-username 4.15.18
  Uname: Linux 4.15.0-1036-azure x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Jan 30 07:04:25 2019
  SourcePackage: linux-signed-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Seth Arnold]

Hello Colin, yes, this is still an open issue:

Linux wopr 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux


Apr 22 19:10:03 wopr zed[12576]: eid=8352 class=history_event 
pool_guid=0xB3B099B638F02EEF
Apr 22 19:10:03 wopr kernel: VERIFY(size != 0) failed
Apr 22 19:10:03 wopr kernel: PANIC at range_tree.c:304:range_tree_find_impl()
Apr 22 19:10:03 wopr kernel: Showing stack for process 12577
Apr 22 19:10:03 wopr kernel: CPU: 8 PID: 12577 Comm: receive_writer Tainted: P  
 O 4.15.0-91-generic #92-Ubuntu
Apr 22 19:10:03 wopr kernel: Hardware name: Supermicro 
SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015
Apr 22 19:10:03 wopr kernel: Call Trace:
Apr 22 19:10:03 wopr kernel:  dump_stack+0x6d/0x8e
Apr 22 19:10:03 wopr kernel:  spl_dumpstack+0x42/0x50 [spl]
Apr 22 19:10:03 wopr kernel:  spl_panic+0xc8/0x110 [spl]
Apr 22 19:10:03 wopr kernel:  ? __switch_to_asm+0x41/0x70
Apr 22 19:10:03 wopr kernel:  ? abd_iter_map+0xa/0x90 [zfs]
Apr 22 19:10:03 wopr kernel:  ? dbuf_dirty+0x43d/0x850 [zfs]
Apr 22 19:10:03 wopr kernel:  ? getrawmonotonic64+0x43/0xd0
Apr 22 19:10:03 wopr kernel:  ? getrawmonotonic64+0x43/0xd0
Apr 22 19:10:03 wopr kernel:  ? dmu_zfetch+0x49a/0x500 [zfs]
Apr 22 19:10:03 wopr kernel:  ? getrawmonotonic64+0x43/0xd0
Apr 22 19:10:03 wopr kernel:  ? dmu_zfetch+0x49a/0x500 [zfs]
Apr 22 19:10:03 wopr kernel:  ? mutex_lock+0x12/0x40
Apr 22 19:10:03 wopr kernel:  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
Apr 22 19:10:03 wopr kernel:  range_tree_find_impl+0x88/0x90 [zfs]
Apr 22 19:10:03 wopr kernel:  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
Apr 22 19:10:03 wopr kernel:  range_tree_clear+0x4f/0x60 [zfs]
Apr 22 19:10:03 wopr kernel:  dnode_free_range+0x11f/0x5a0 [zfs]
Apr 22 19:10:03 wopr kernel:  dmu_object_free+0x53/0x90 [zfs]
Apr 22 19:10:03 wopr kernel:  dmu_free_long_object+0x9f/0xc0 [zfs]
Apr 22 19:10:03 wopr kernel:  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
Apr 22 19:10:03 wopr kernel:  receive_writer_thread+0x6d2/0xa60 [zfs]
Apr 22 19:10:03 wopr kernel:  ? set_curr_task_fair+0x2b/0x60
Apr 22 19:10:03 wopr kernel:  ? spl_kmem_free+0x33/0x40 [spl]
Apr 22 19:10:03 wopr kernel:  ? kfree+0x165/0x180
Apr 22 19:10:03 wopr kernel:  ? receive_free.isra.13+0xc0/0xc0 [zfs]
Apr 22 19:10:03 wopr kernel:  thread_generic_wrapper+0x74/0x90 [spl]
Apr 22 19:10:03 wopr kernel:  kthread+0x121/0x140
Apr 22 19:10:03 wopr kernel:  ? __thread_exit+0x20/0x20 [spl]
Apr 22 19:10:03 wopr kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Apr 22 19:10:03 wopr kernel:  ret_from_fork+0x35/0x40
Apr 22 19:12:56 wopr kernel: INFO: task txg_quiesce:2265 blocked for more than 
120 seconds.
Apr 22 19:12:56 wopr kernel:   Tainted: P   O 4.15.0-91-generic 
#92-Ubuntu
Apr 22 19:12:56 wopr kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
Apr 22 19:12:56 wopr kernel: txg_quiesce D0  2265  2 0x8000
Apr 22 19:12:56 wopr kernel: Call Trace:
Apr 22 19:12:56 wopr kernel:  __schedule+0x24e/0x880
Apr 22 19:12:56 wopr kernel:  schedule+0x2c/0x80
Apr 22 19:12:56 wopr kernel:  cv_wait_common+0x11e/0x140 [spl]
Apr 22 19:12:56 wopr kernel:  ? wait_woken+0x80/0x80
Apr 22 19:12:56 wopr kernel:  __cv_wait+0x15/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
Apr 22 19:12:56 wopr kernel:  ? txg_delay+0x1b0/0x1b0 [zfs]
Apr 22 19:12:56 wopr kernel:  thread_generic_wrapper+0x74/0x90 [spl]
Apr 22 19:12:56 wopr kernel:  kthread+0x121/0x140
Apr 22 19:12:56 wopr kernel:  ? __thread_exit+0x20/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Apr 22 19:12:56 wopr kernel:  ret_from_fork+0x35/0x40
Apr 22 19:12:56 wopr kernel: INFO: task zfs:12482 blocked for more than 120 
seconds.
Apr 22 19:12:56 wopr kernel:   Tainted: P   O 4.15.0-91-generic 
#92-Ubuntu
Apr 22 19:12:56 wopr kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
Apr 22 19:12:56 wopr kernel: zfs D0 12482  12479 0x8080
Apr 22 19:12:56 wopr kernel: Call Trace:
Apr 22 19:12:56 wopr kernel:  __schedule+0x24e/0x880
Apr 22 19:12:56 wopr kernel:  schedule+0x2c/0x80
Apr 22 19:12:56 wopr kernel:  cv_wait_common+0x11e/0x140 [spl]
Apr 22 19:12:56 wopr kernel:  ? wait_woken+0x80/0x80
Apr 22 19:12:56 wopr kernel:  __cv_wait+0x15/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  dmu_recv_stream+0xa51/0xef0 [zfs]
Apr 22 19:12:56 wopr kernel:  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
Apr 22 19:12:56 wopr kernel:  ? dbuf_rele+0x36/0x40 [zfs]
Apr 22 19:12:56 wopr kernel:  zfs_ioc_recv_new+0x33d/0x410 [zfs]
Apr 22 19:12:56 wopr kernel:  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
Apr 22 19:12:56 wopr kernel:  ? spl_vmem_alloc+0x19/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
Apr 22 19:12:56 wopr kernel:  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
Apr 22 19:12:56 wopr kernel:  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
Apr 22 19:12:56 wopr kernel:  zfsdev_ioctl+0x

[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76

[Guilherme G. Piccoli]

Hi yamato, thank you for the great report! I think I found the problem -
can you test my fix proposal? It's just a matter of adding the following
PPA to your system and installing the kernel:

launchpad.net/~gpiccoli/+archive/ubuntu/test1869672

You can run the following commands in order to achieve that:
sudo add-apt-repository ppa:gpiccoli/test1869672
sudo apt-get update
sudo apt-get install linux-image-4.15.0-97-generic 
linux-modules-4.15.0-97-generic linux-modules-extra-4.15.0-97-generic

After that, reboot into this new kernel, and test kdump load if
possible. Also, please send me the output of the commands "uname -a" and
"kdump-config show" when running the PPA kernel.

Thanks again,


Guilherme

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

Title:
  kdump kernel can't be loaded using kernel 4.15.0-76

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  Thank you for reading this report.
  This may caused by bugs in kernel, not in kdump. If so, I will report this to 
kernel team.
  I need your comment to solve this.

  [Impact]
  * Kdump kernel can't be loaded using linux kernel 4.15.0-76.

  [Environment]
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  uname:
  Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  Secure boot is enabled.

  Versions:
  * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1
  * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4

  [Test case]
  1)After OS booted, run systemctl status kdump-tools shows these messages 
below:

  
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago
    Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
   Main PID: 895 (code=exited, status=0/SUCCESS)

  Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format 
error
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * failed to load kdump kernel
  Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service.
  

  2)Run kexec directly:
  $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic 
root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic 
/boot/vmlinuz-4.15.0-64-generic

  Then,these messages are shown:
  Cannot open /proc/kcore: Operation not permitted
  Cannot read /proc/kcore: Operation not permitted
  Cannot load /boot/vmlinuz-4.15.0-76-generic

  On dmesg, these messages are shown:
  
  [  538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7
  

  3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can
  be loaded.

  $ sudo systemctl status kdump-tools
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago
   Main PID: 832 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
     CGroup: /system.slice/kdump-tools.service

  Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 25 13:39:02 ubuntu kdump-tools[832]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 25 13:39:03 ubuntu kdump-tools[832]:  * loaded kdump kernel
  Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel
  Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service.

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

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

[Kernel-packages] [Bug 1874359] 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 1874359

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

Title:
  alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a
  regression in the  asoc machine driver)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.6 source package in Focal:
  New

Bug description:
  Please apply the fix for #1872569 first, then apply this patch.

  [Impact]
  The fix for #1872569 introduces a regression, the driver access a
  NULL pointer on the machiens without Intel hdmi audio codec.

  [Fix]
  pick a fixing patch from alsa/asoc repo, the patch doesn't assume
  the first rtd is for hda codec, it will look for that rtd through
  strstr()

  [Test Case]
  Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses
  this driver, the audio could work. disable the intel hdmi audio codec
  through bios, the analogue audio still works

  
  [Regression Risk]
  Low, I have tested this patch Lenovo / Dell machines, they all worked well.

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

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

[Kernel-packages] [Bug 1874359] Re: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver)

[Hui Wang]

** Description changed:

- This bug is for tracking purpose.
+ Please apply the fix for #1872569 first, then apply this patch.
+ 
+ [Impact]
+ The fix for #1872569 introduces a regression, the driver access a
+ NULL pointer on the machiens without Intel hdmi audio codec.
+ 
+ [Fix]
+ pick a fixing patch from alsa/asoc repo, the patch doesn't assume
+ the first rtd is for hda codec, it will look for that rtd through
+ strstr()
+ 
+ [Test Case]
+ Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses
+ this driver, the audio could work. disable the intel hdmi audio codec
+ through bios, the analogue audio still works
+ 
+ 
+ [Regression Risk]
+ Low, I have tested this patch Lenovo / Dell machines, they all worked 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/1874359

Title:
  alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a
  regression in the  asoc machine driver)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.6 source package in Focal:
  New

Bug description:
  Please apply the fix for #1872569 first, then apply this patch.

  [Impact]
  The fix for #1872569 introduces a regression, the driver access a
  NULL pointer on the machiens without Intel hdmi audio codec.

  [Fix]
  pick a fixing patch from alsa/asoc repo, the patch doesn't assume
  the first rtd is for hda codec, it will look for that rtd through
  strstr()

  [Test Case]
  Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses
  this driver, the audio could work. disable the intel hdmi audio codec
  through bios, the analogue audio still works

  
  [Regression Risk]
  Low, I have tested this patch Lenovo / Dell machines, they all worked well.

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

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

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Dexuan Cui]

Sorry, I did miss this part of your previous reply:

root@stock19:~# systemctl list-jobs
JOB UNIT TYPE STATE
 48 setvtrgb.service start waiting
137 system-getty.slice start waiting
  1 graphical.target start waiting
102 systemd-update-utmp-runlevel.service start waiting
 83 plymouth-quit-wait.service start running
  2 multi-user.target start waiting

I'm wondering if you can disable setvtrgb.service, system-getty.slice,
systemd-update-utmp-runlevel.service, and plymouth-quit-wait.service,
and see if the long delay will disappear. I guess these 4 services don't
look critical to the GUI desktop.

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouve

[Kernel-packages] [Bug 1874359] [NEW] alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver)

[Hui Wang]

Public bug reported:

This bug is for tracking purpose.

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

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Focal)
   Importance: Critical
 Assignee: Hui Wang (hui.wang)
   Status: New

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

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

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

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

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

** No longer affects: linux (Ubuntu Bionic)

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

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

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

** No longer affects: linux-oem-osp1 (Ubuntu 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/1874359

Title:
  alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a
  regression in the  asoc machine driver)

Status in linux package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  New

Bug description:
  This bug is for tracking purpose.

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

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

[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded

[Dexuan Cui]

I agree with David. IMO this bug should be fixed ASAP. Thanks!

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

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

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

[Kernel-packages] [Bug 1874354] [NEW] limited wireles channels on a RPi 3B

[Brian Murray]

Public bug reported:

I saw the following in my dmesg:

[   13.113608] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[   13.113640] cfg80211: failed to load regulatory.db
[   13.259143] brcmfmac: F1 signature read @0x1800=0x1541a9a6
[   13.268452] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio 
for chip BCM43430/1
[   13.279732] usbcore: registered new interface driver brcmfmac
[   13.520854] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio 
for chip BCM43430/1
[   13.532110] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available 
(err=-2), device may have limited channels available
[   13.552859] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 
23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f

I don't know if the channels are really limited.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-raspi 5.4.0.1008.8
ProcVersionSignature: User Name 5.4.0-1008.8-raspi 5.4.29
Uname: Linux 5.4.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27
Architecture: arm64
CasperMD5CheckResult: skip
Date: Thu Apr 23 00:29:47 2020
SourcePackage: linux-meta-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 focal rls-ff-incoming uec-images

** Tags added: rls-ff-incoming

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

Title:
  limited wireles channels on a RPi 3B

Status in linux-meta-raspi package in Ubuntu:
  New

Bug description:
  I saw the following in my dmesg:

  [   13.113608] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
  [   13.113640] cfg80211: failed to load regulatory.db
  [   13.259143] brcmfmac: F1 signature read @0x1800=0x1541a9a6
  [   13.268452] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac43430-sdio for chip BCM43430/1
  [   13.279732] usbcore: registered new interface driver brcmfmac
  [   13.520854] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac43430-sdio for chip BCM43430/1
  [   13.532110] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available 
(err=-2), device may have limited channels available
  [   13.552859] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 
23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f

  I don't know if the channels are really limited.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-raspi 5.4.0.1008.8
  ProcVersionSignature: User Name 5.4.0-1008.8-raspi 5.4.29
  Uname: Linux 5.4.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Thu Apr 23 00:29:47 2020
  SourcePackage: linux-meta-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules -
5.4.0-26.30+2

---
linux-restricted-modules (5.4.0-26.30+2) focal; urgency=medium

  * /bin/in-target check is flawed as it does not tell the difference
between live-session and in-target chroot. (LP: #1874278)

 -- Dimitri John Ledkov   Wed, 22 Apr 2020 22:43:55
+0100

** Changed in: linux-restricted-modules (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

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

-- 
Mailing list: https://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 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Javier]

I could solve it with these links, it was difficult for me, now I no longer
use that Ultrabox, but you can:

drivers - Bluetooth Broadcom 43142 isn't working - Ask Ubuntu

networking - ubuntu 14.04 bluetooth BCM43142 no discovery (tx timeout) -
Ask Ubuntu


Regards

El mié., 24 jul. 2019 a las 19:09, Brad Figg ()
escribió:

> ** Tags added: cscc
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1743336).
> https://bugs.launchpad.net/bugs/1366418
>
> Title:
>   Bluetooth BCM43142A0 doesn’t work
>
> Status in bluez package in Ubuntu:
>   Invalid
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-firmware package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
>   (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
>   displayed in the menu bar, if I open the bluetooth UI and switch on,
>   nothing happens and the result of “hcitool dev” is empty.
>
>   I have tried to install the windows driver with ndiswrapper, and the
>   bluetooth device seems to be detected as an usb bluetooth device but
>   still not working. I then add the device to the bluetooth usb device
>   and was able to activate bluetooth in the UI but it does not detect
>   any other devices (I’ve tested with a smartphone).
>
>   The driver I have installed can be found in asus page =>
>   http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
>   Select Windows OS, then “bluetooth” section, take the Broadcom driver
>   (should be the first one).
>
>   If you extract this archive, you will find a file named “bcbtums-
>   win8x64-brcm.inf” which I installed using the following command:
>
>   ndiswrapper -i bcbtums-win8x64-brcm.inf
>
>   Then, the result of “ndiswrapper -l” is:
>
>   bcbtums-win8x64-brcm : driver installed
> device (04CA:2006) present
>
>   in usb-devices, I find a device which was not present before
>   installation (I might have activated btusb before on this paste):
>
>   T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
>   D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
>   P:  Vendor=04ca ProdID=2006 Rev=01.12
>   S:  Manufacturer=Broadcom Corp
>   S:  Product=BCM43142A0
>   S:  SerialNumber=B8EE6593D989
>   C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
>   I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>   I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
>   then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
>   can switch usb on, but no device will be detected and I’ve found this
>   in the dmesg:
>
>   [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout
>
>   which looks pretty much like a “bluetooth not working” message which I
>   don’t understand in details.
>
>   I leave here my full dmesg:
>
>   [0.253889] NetLabel:  domain hash size = 128
>   [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
>   [0.253901] NetLabel:  unlabeled traffic allowed by default
>   [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>   [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>   [0.255995] Switched to clocksource hpet
>   [0.260468] AppArmor: AppArmor Filesystem Enabled
>   [0.260488] pnp: PnP ACPI init
>   [0.260500] ACPI: bus type PNP registered
>   [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been
> reserved
>   [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01
> (active)
>   [0.260642] pnp 00:01: [dma 4]
>   [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
>   [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
>   [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
>   [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
>   [0.260927] system 00:04: [io  0x] has been reserved
>   [0.260928] system 00:04: [io  0x] has been reserved
>   [0.260930] system 00:04: [io  0x] has been reserved
>   [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
>   [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
>   [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
>   [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
>   [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
>   [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
>   [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02
> (active)
>   [0.260969] pnp 00:05: Plug and Play ACPI device, IDs P

Re: [Kernel-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Javier]

I could solve it with these links, it was difficult for me, now I no longer
use that Ultrabox, but you can:

drivers - Bluetooth Broadcom 43142 isn't working - Ask Ubuntu

networking - ubuntu 14.04 bluetooth BCM43142 no discovery (tx timeout) -
Ask Ubuntu


Regards

El mié., 24 jul. 2019 a las 19:09, Brad Figg ()
escribió:

> ** Tags added: cscc
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1743336).
> https://bugs.launchpad.net/bugs/1366418
>
> Title:
>   Bluetooth BCM43142A0 doesn’t work
>
> Status in bluez package in Ubuntu:
>   Invalid
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-firmware package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
>   (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
>   displayed in the menu bar, if I open the bluetooth UI and switch on,
>   nothing happens and the result of “hcitool dev” is empty.
>
>   I have tried to install the windows driver with ndiswrapper, and the
>   bluetooth device seems to be detected as an usb bluetooth device but
>   still not working. I then add the device to the bluetooth usb device
>   and was able to activate bluetooth in the UI but it does not detect
>   any other devices (I’ve tested with a smartphone).
>
>   The driver I have installed can be found in asus page =>
>   http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
>   Select Windows OS, then “bluetooth” section, take the Broadcom driver
>   (should be the first one).
>
>   If you extract this archive, you will find a file named “bcbtums-
>   win8x64-brcm.inf” which I installed using the following command:
>
>   ndiswrapper -i bcbtums-win8x64-brcm.inf
>
>   Then, the result of “ndiswrapper -l” is:
>
>   bcbtums-win8x64-brcm : driver installed
> device (04CA:2006) present
>
>   in usb-devices, I find a device which was not present before
>   installation (I might have activated btusb before on this paste):
>
>   T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
>   D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
>   P:  Vendor=04ca ProdID=2006 Rev=01.12
>   S:  Manufacturer=Broadcom Corp
>   S:  Product=BCM43142A0
>   S:  SerialNumber=B8EE6593D989
>   C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
>   I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>   I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
>   then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
>   can switch usb on, but no device will be detected and I’ve found this
>   in the dmesg:
>
>   [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout
>
>   which looks pretty much like a “bluetooth not working” message which I
>   don’t understand in details.
>
>   I leave here my full dmesg:
>
>   [0.253889] NetLabel:  domain hash size = 128
>   [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
>   [0.253901] NetLabel:  unlabeled traffic allowed by default
>   [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>   [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>   [0.255995] Switched to clocksource hpet
>   [0.260468] AppArmor: AppArmor Filesystem Enabled
>   [0.260488] pnp: PnP ACPI init
>   [0.260500] ACPI: bus type PNP registered
>   [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been
> reserved
>   [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01
> (active)
>   [0.260642] pnp 00:01: [dma 4]
>   [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
>   [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
>   [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
>   [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
>   [0.260927] system 00:04: [io  0x] has been reserved
>   [0.260928] system 00:04: [io  0x] has been reserved
>   [0.260930] system 00:04: [io  0x] has been reserved
>   [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
>   [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
>   [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
>   [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
>   [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
>   [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
>   [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02
> (active)
>   [0.260969] pnp 00:05: Plug and Play ACPI device, IDs P

Re: [Kernel-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Javier]

I could solve it with these links, it was difficult for me, now I no longer
use that Ultrabox, but you can:

drivers - Bluetooth Broadcom 43142 isn't working - Ask Ubuntu

networking - ubuntu 14.04 bluetooth BCM43142 no discovery (tx timeout) -
Ask Ubuntu


Regards


El mié., 22 abr. 2020 a las 19:10, Gannet (<1366...@bugs.launchpad.net>)
escribió:

> Kubuntu 20.04 LTS
> HP ProBook 455 G3
>
> $ dmesg | grep -i error
> [   20.229516] bluetooth hci0: Direct firmware load for
> brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
> [ 1242.727869] bluetooth hci0: Direct firmware load for
> brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
> [ 5759.316789] bluetooth hci0: Direct firmware load for
> brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
>
> ** Tags added: focal
>
> ** Changed in: linux-firmware (Ubuntu)
>Status: Incomplete => Confirmed
>
> ** Changed in: bluez (Ubuntu)
>Status: Invalid => Confirmed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1743336).
> https://bugs.launchpad.net/bugs/1366418
>
> Title:
>   Bluetooth BCM43142A0 doesn’t work
>
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-firmware package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
>   (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
>   displayed in the menu bar, if I open the bluetooth UI and switch on,
>   nothing happens and the result of “hcitool dev” is empty.
>
>   I have tried to install the windows driver with ndiswrapper, and the
>   bluetooth device seems to be detected as an usb bluetooth device but
>   still not working. I then add the device to the bluetooth usb device
>   and was able to activate bluetooth in the UI but it does not detect
>   any other devices (I’ve tested with a smartphone).
>
>   The driver I have installed can be found in asus page =>
>   http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
>   Select Windows OS, then “bluetooth” section, take the Broadcom driver
>   (should be the first one).
>
>   If you extract this archive, you will find a file named “bcbtums-
>   win8x64-brcm.inf” which I installed using the following command:
>
>   ndiswrapper -i bcbtums-win8x64-brcm.inf
>
>   Then, the result of “ndiswrapper -l” is:
>
>   bcbtums-win8x64-brcm : driver installed
> device (04CA:2006) present
>
>   in usb-devices, I find a device which was not present before
>   installation (I might have activated btusb before on this paste):
>
>   T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
>   D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
>   P:  Vendor=04ca ProdID=2006 Rev=01.12
>   S:  Manufacturer=Broadcom Corp
>   S:  Product=BCM43142A0
>   S:  SerialNumber=B8EE6593D989
>   C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
>   I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>   I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
>   then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
>   can switch usb on, but no device will be detected and I’ve found this
>   in the dmesg:
>
>   [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout
>
>   which looks pretty much like a “bluetooth not working” message which I
>   don’t understand in details.
>
>   I leave here my full dmesg:
>
>   [0.253889] NetLabel:  domain hash size = 128
>   [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
>   [0.253901] NetLabel:  unlabeled traffic allowed by default
>   [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>   [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>   [0.255995] Switched to clocksource hpet
>   [0.260468] AppArmor: AppArmor Filesystem Enabled
>   [0.260488] pnp: PnP ACPI init
>   [0.260500] ACPI: bus type PNP registered
>   [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been
> reserved
>   [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01
> (active)
>   [0.260642] pnp 00:01: [dma 4]
>   [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
>   [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
>   [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
>   [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
>   [0.260927] system 00:04: [io  0x] has been reserved
>   [0.260928] system 00:04: [io  0x] has been reserved
>   [0.260930] system 00:04: [io  0x] has be

[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

[Andrew Vagin]

https://lists.ubuntu.com/archives/kernel-team/2020-April/109089.html

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

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to checkpoint a container (docker/podman) on 18.04 fails
  starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
  this in Travis starting a few weeks ago. Manually testing it locally
  shows that linux-image-5.0.0-32-generic still works and linux-
  image-5.0.0-35-generic does not longer work. It seems to be overlayfs
  related, at least that is what we believe. The CRIU error message we
  see is:

  (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 
path=/bin/busybox
  (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed 
with -1

  
  We have not seen this only in Travis, but also multiple CRIU users reported 
that bug already. Currently we have to tell them to downgrade the kernel.

  I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
  on the 4.18.0 kernel series does not show this error.
  4.18.0-25-generic works without problems.

  See also https://github.com/checkpoint-restore/criu/issues/860

  One of the possible explanations from our side include:

  "Looks like we have the same as for st_dev now with mnt_id, that is
  bad, because we can't find on which mount to open the file if kernel
  hides these information from us."

  Running on the upstream 5.5.0-rc1 kernel does not show this error.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 18:52 seq
   crw-rw 1 root audio 116, 33 Jan  7 18:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 19.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  eoan uec-images
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

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

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

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Matthew Swift]

To clarify, I say the purple login screen is "more native" because
that's what I get on the monitor of a physically independent machine
(not a VM) running Ubunutu; naturally I do not get an (X)RDP screen on
that machine ever.

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Matthew Swift]

You missed that I did include the output of 'systemctl list-jobs' during
the crucial interval of delay.

I will follow your instructions regarding boot parameters etc. and post
results asap.

I expect there is an enormous difference between accessing the VM via
RPD (XRDP) protocol and accessing the VM via the more native interface
(purple screen) which is eventually available on 19.10, even though both
are accessed through the Hyper-V "Connection" interface. XRDP seems like
the preferred way, it's the only way I get to 18.04, and forcing it on
19.10 is the only way I get screen size control and cut-and-paste from
guest to host. Am seeking confirmation of what is the correct/preferred
behavior is with 19.10. Should I be getting the "native" purple login
screen quickly and then have cut-paste and screen control, or should be
getting the XRDP interface quickly, just like I do with 18.04?

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0

[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded

[David Baird]

Hi, this issue needs attention because it renders the cloud images for
Ubuntu 20.04 potentially unusable. Thanks.

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

Title:
  initramfs does not get loaded

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel boots, it can boot up successfully -- this
  “panic/success/panic/success” pattern repeats forever…

  
  The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
  /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
  /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
  The v5.6 kernel uses =m rather than =y, so is affected here.

  
  It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

  This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 
19.04 as well?) on Azure. 
  We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

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

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

[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Launchpad Bug Tracker]

** Branch linked: lp:~kubuntu-dev/ubuntu-seeds/kubuntu.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/1873867

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

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

[Sultan Alsawaf]

@eggie You shouldn't be using nouveau on your hardware; it has almost no
support for the Turing architecture from Nvidia. You should blacklist
nouveau and then reboot. If you want to make use of your Nvidia card,
you'll have to use the binary Nvidia driver sadly.

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

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

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

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

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

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  

[Kernel-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Martin Wimpress]

** Changed in: linux-restricted-modules (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

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

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

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

[Egbert van der Wal]

@arighi - it helps, but introduces different problems on my Dell XPS 15
7590. I get much less frequent lockups but they still do occur. It seems
to introduce similar issues with Nouveau.

My dmesg gives me lots of messages like this:

[   67.714761] nouveau :01:00.0: fifo: SCHED_ERROR 08 []
[   67.855754] nouveau :01:00.0: DRM: failed to idle channel 0 [DRM]

[ 5396.978950] nouveau :01:00.0: tmr: stalled at 

[ 5412.086427] nouveau :01:00.0: timeout
[ 5412.086464] WARNING: CPU: 11 PID: 11576 at 
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmtu102.c:44 
tu102_vmm_flush+0x130/0x140 [nouveau]

and lots of more information. I'll add the full output of dmesg as an
attachment.

Not sure if the new problems are introduced by your patch but I didn't
experience them before on 5.3 and are also not occuring on the
5.4.28-050428-generic kernel from `mainline`. So back to 5.4.28 for me,
again.


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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

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

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

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

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

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)

[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

[Matthew Ruffell]

** Description changed:

  BugLink: https://bugs.launchpad.net/bugs/1872863
  
  [Impact]
  
  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.
  
  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.
  
  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in
  LP #1378648 due to bochs-drm causing problems in a PowerKVM machine.
  This problem appears to be fixed now, and bochs-drm has been re-enabled
  for Disco and up, in LP #1795857 and has been proven safe.
  
  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.
  
  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.
  
  [Fix]
  
  I noticed on Focal, if you boot, the framebuffer is initially efifb:
  
  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device
  
  This soon changes to bochs-drm about a second later:
  
  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48
  
  On bionic, the framebuffer never changes from efifb, since the bochs-drm
  kernel module is not built, and it is also present on the module banlist
  in /etc/modprobe.d/blacklist-framebuffer.conf
  
  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.
  
  [Testcase]
  
  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In the
  "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64:
  /usr/share/OVMF/OVMF_CODE.secboot.fd".
  
  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you have
  grub2 2.02-2ubuntu8.15 installed.
  
  Shut the VM down, and set the video device to VGA. Or VGA=std if you use
  the QEMU command line.
  
  Start the VM up, and the screen will be garbled. See attached picture.
  
  If you install my test packages, which are available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test
  
  Instructions to install (on a bionic system):
  
  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020
  
  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.
  
  [Regression Potential]
  
  We are enabling a display driver on Bionic which was previously
  disabled, so there will be some virtual machines making the jump to
  using bochs-drm since it would now be available.
  
  I don't think that this is a bad thing, and in many ways will probably
  end up improving some user's experience. Although there are two
  scenarios where a regression could happen:
  
  1 - frequently gamers use GPU passthrough to their kvm based virtual
  machines, and I have seen them expect, o

[Kernel-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

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

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

[Kernel-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

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

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

[Kernel-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Gannet]

Kubuntu 20.04 LTS
HP ProBook 455 G3

$ dmesg | grep -i error
[   20.229516] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
[ 1242.727869] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
[ 5759.316789] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2

** Tags added: focal

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

** Changed in: bluez (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Pl

[Kernel-packages] [Bug 1806681] Re: hp_wmi: query 0xd returned error 0x5

[Gannet]

HP ProBook 455 G3
[   18.373200] hp_wmi: query 0x4 returned error 0x5
[   18.377701] hp_wmi: query 0x4 returned error 0x5
[   18.385171] hp_wmi: query 0xd returned error 0x5
[   18.397105] hp_wmi: query 0x1b returned error 0x5

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

Title:
  hp_wmi: query 0xd returned error 0x5

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

Bug description:
  Hello,

  dmesg:
  [   18.296366] hp_wmi: query 0xd returned error 0x5

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:05:38 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

[Matthew Ruffell]

** Description changed:

  BugLink: https://bugs.launchpad.net/bugs/1872863
  
  [Impact]
  
  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.
  
  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.
  
  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in
  LP #1378648 due to bochs-drm causing problems in a PowerKVM machine.
  This problem appears to be fixed now, and bochs-drm has been re-enabled
  for Disco and up, in LP #1795857 and has been proven safe.
  
  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.
  
  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.
  
  [Fix]
  
  I noticed on Focal, if you boot, the framebuffer is initially efifb:
  
  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device
  
  This soon changes to bochs-drm about a second later:
  
  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48
  
  On bionic, the framebuffer never changes from efifb, since the bochs-drm
  kernel module is not built, and it is also present on the module banlist
  in /etc/modprobe.d/blacklist-framebuffer.conf
  
  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.
  
  [Testcase]
  
  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In the
  "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64:
  /usr/share/OVMF/OVMF_CODE.secboot.fd".
  
  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you have
  grub2 2.02-2ubuntu8.15 installed.
  
  Shut the VM down, and set the video device to VGA. Or VGA=std if you use
  the QEMU command line.
  
  Start the VM up, and the screen will be garbled. See attached picture.
  
  If you install my test packages, which are available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test
  
  Instructions to install (on a bionic system):
  
  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020
  
  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.
  
  [Regression Potential]
  
  We are enabling a display driver on Bionic which was previously
  disabled, so there will be some virtual machines making the jump to
  using bochs-drm since it would now be available.
  
  I don't think that this is a bad thing, and in many ways will probably
  end up improving some user's experience. Although there are two
  scenarios where a regression could happen:
  
  1 - frequently gamers use GPU passthrough to their kvm based virtual
  machines, and I have seen them expect, o

[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76

[Guilherme G. Piccoli]

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

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

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

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: makedumpfile (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  kdump kernel can't be loaded using kernel 4.15.0-76

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  Thank you for reading this report.
  This may caused by bugs in kernel, not in kdump. If so, I will report this to 
kernel team.
  I need your comment to solve this.

  [Impact]
  * Kdump kernel can't be loaded using linux kernel 4.15.0-76.

  [Environment]
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  uname:
  Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  Secure boot is enabled.

  Versions:
  * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1
  * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4

  [Test case]
  1)After OS booted, run systemctl status kdump-tools shows these messages 
below:

  
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago
    Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
   Main PID: 895 (code=exited, status=0/SUCCESS)

  Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format 
error
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * failed to load kdump kernel
  Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service.
  

  2)Run kexec directly:
  $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic 
root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic 
/boot/vmlinuz-4.15.0-64-generic

  Then,these messages are shown:
  Cannot open /proc/kcore: Operation not permitted
  Cannot read /proc/kcore: Operation not permitted
  Cannot load /boot/vmlinuz-4.15.0-76-generic

  On dmesg, these messages are shown:
  
  [  538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7
  

  3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can
  be loaded.

  $ sudo systemctl status kdump-tools
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago
   Main PID: 832 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
     CGroup: /system.slice/kdump-tools.service

  Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 25 13:39:02 ubuntu kdump-tools[832]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 25 13:39:03 ubuntu kdump-tools[832]:  * loaded kdump kernel
  Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel
  Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service.

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

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

[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

[Dan Streetman]

** Tags added: sts-sponsor-ddstreet

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

  Instructions to install (on a bionic system):

  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020

  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.

  [Regression Potential]

  We are enabling a display 

[Kernel-packages] [Bug 1874325] [NEW] Eoan update: upstream stable patchset 2020-04-22

[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-04-22

Ported from the following upstream stable releases:
v4.19.116, v5.4.33

   from git://git.kernel.org/

ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
net: vxge: fix wrong __VA_ARGS__ usage
hinic: fix a bug of waitting for IO stopped
hinic: fix wrong para of wait_for_completion_timeout
cxgb4/ptp: pass the sign of offset delta in FW CMD
qlcnic: Fix bad kzalloc null test
i2c: st: fix missing struct parameter description
cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL
media: venus: hfi_parser: Ignore HEVC encoding for V1
firmware: arm_sdei: fix double-lock on hibernate with shared events
null_blk: Fix the null_add_dev() error path
null_blk: Handle null_add_dev() failures properly
null_blk: fix spurious IO errors after failed past-wp access
xhci: bail out early if driver can't accress host in resume
x86: Don't let pgprot_modify() change the page encryption bit
block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
irqchip/versatile-fpga: Handle chained IRQs properly
sched: Avoid scale real weight down to zero
selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
PCI/switchtec: Fix init_completion race condition with poll_wait()
media: i2c: video-i2c: fix build errors due to 'imply hwmon'
libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
pstore/platform: fix potential mem leak if pstore_init_fs failed
gfs2: Don't demote a glock until its revokes are written
x86/boot: Use unsigned comparison for addresses
efi/x86: Ignore the memory attributes table on i386
genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
block: Fix use-after-free issue accessing struct io_cq
media: i2c: ov5695: Fix power on and off sequences
usb: dwc3: core: add support for disabling SS instances in park mode
irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
md: check arrays is suspended in mddev_detach before call quiesce operations
firmware: fix a double abort case with fw_load_sysfs_fallback
locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
block, bfq: fix use-after-free in bfq_idle_slice_timer_body
btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is at 
least queued
btrfs: remove a BUG_ON() from merge_reloc_roots()
btrfs: track reloc roots based on their commit root bytenr
ASoC: fix regwmask
ASoC: dapm: connect virtual mux with default value
ASoC: dpcm: allow start or stop during pause for backend
ASoC: topology: use name_prefix for new kcontrol
usb: gadget: f_fs: Fix use after free issue as part of queue failure
usb: gadget: composite: Inform controller driver of self-powered
ALSA: usb-audio: Add mixer workaround for TRX40 and co
ALSA: hda: Add driver blacklist
ALSA: hda: Fix potential access overflow in beep helper
ALSA: ice1724: Fix invalid access for enumerated ctl items
ALSA: pcm: oss: Fix regression by buffer overflow fix
ALSA: doc: Document PC Beep Hidden Register on Realtek ALC256
ALSA: hda/realtek - Set principled PC Beep configuration for ALC256
ALSA: hda/realtek - Remove now-unnecessary XPS 13 headphone noise fixups
ALSA: hda/realtek - Add quirk for MSI GL63
media: ti-vpe: cal: fix disable_irqs to only the intended target
acpi/x86: ignore unspecified bit positions in the ACPI global lock field
thermal: devfreq_cooling: inline all stubs for CONFIG_DEVFREQ_THERMAL=n
nvme-fc: Revert "add module to ops template to allow module references"
nvme: Treat discovery subsystems as unique subsystems
PCI: pciehp: Fix indefinite wait on sysfs requests
PCI/ASPM: Clear the correct bits when enabling L1 substates
PCI: Add boot interrupt quirk mechanism for Xeon chipsets
PCI: endpoint: Fix for concurrent memory allocation in OB address region
tpm: Don't make log failures fatal
tpm: tpm1_bios_measurements_next should increase position index
tpm: tpm2_bios_measurements_next should increase position index
irqchip/versatile-fpga: Apply clear-mask earlier
pstore: pstore_ftrace_seq_next should increase position index
MIPS/tlbex: Fix LDDIR usage in setup_pw() for Loongson-3
MIPS: OCTEON: irq: Fix potential NULL pointer dereference
ath9k: Handle txpower changes even when TPC is disabled
signal: Extend exec_id to 64bits
x86/entry/32: Add missing ASM_CLAC to general_protection entry
KVM: nVMX: Properly handle userspace interrupt window request
KVM: s390: vsie: Fix region 1 ASCE sanity shado

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

[Anton Keks]

Wilson, does it happen when charging or the laptop is in the sun?
It seems to me this is a battery temperature sensor and it is only mildly 
affected by the CPU temperature.

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

Title:
  Lenovo Yoga C940 frequently does thermal shutdown

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

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

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

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

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

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

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

  Is there a workaround?

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

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

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

[Kernel-packages] [Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

This issue extends to the daily desktop cd image for focal. When booted
from a usb memory stick and the safe graphics (which uses nomodeset) is
selected from grub, the screen remains black and never completes
booting. This issue doesn't exist with the current 19.10 cd images which
boot without issue on a GTX680.

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

Title:
  booting into recovery mode hangs under 20.04

Status in linux-meta package in Ubuntu:
  New

Bug description:
  On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the
  recovery mode from grub hangs on loading of the ramdisk with the
  Recovery Menu dialog never appearing. This problem doesn't exist for a
  fresh install of Ubuntu 18.04 updated to the current package updates.
  In that case, the Recovery Menu appears as expected. This bug in
  Ubuntu 20.04 was reproduced for both an existing Ubuntu 19.10
  installation dist-upgraded to Ubuntu 20.04 as well as for a fresh
  install of Ubuntu 20.04.

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

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

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

[bmaupin]

Due to the aforementioned issue, I believe I was getting a lot of false
negatives and my previous bisects were faulty as a result.

I redid the bisect from the beginning, and this is what I got:

# first bad commit: [c4e1be9ec1130fff4d691cdc0e0f9d666009f9ae] mm,
sparsemem: break out of loops early

I was able to boot with the previous commit
(7660a6fddcbae344de8583aa4092071312f110c3). With
c4e1be9ec1130fff4d691cdc0e0f9d666009f9ae I can only boot using either
noapic or intremap=off.

What should I do now?

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

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

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

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

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

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

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

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

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

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

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

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

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

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

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

[sanette]

@Andrea, for me this seems to solve the problem. Thanks!

(except that my demo is still slightly slower than with 4.4.0 (13fps
instead of 15fps) but this is probably unrelated)

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

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

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

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

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

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.mod

[Kernel-packages] [Bug 1874309] 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/1874309

Title:
  package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to
  install/upgrade: installed linux-image-5.4.0-25-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  (In virtualbox)

  terminal->
  sudo apt install virtualbox-guest-utils-hwe virtualbox-guest-dkms-hwe 
virtualbox-guest-x11-hwe

  during installation, all kernels and modules are erased, and error screen 
stating that user will not be able to log in if every kernel is erased is 
presented. After selecting yes, process is aborted. 
  After that, deleted packages are reinstalled with
  sudo apt install linux-generic linux-modules-extra-5.4.0-21-generic 
linux-image-5.4.0-21-generic linux-image-generic 
linux-modules-extra-5.4.0-25-generic linux-image-5.4.0-25-generic

  Upon every consequent reboot, error pops up on screen, and asks user
  to send information.

  
  Ubuntu 5.4.0-25.29-generic 5.4.30

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-25-generic 5.4.0-25.29
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pixxel 1620 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Apr 20 15:04:22 2020
  ErrorMessage: installed linux-image-5.4.0-25-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-04-20 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic 
root=UUID=1e4016f9-5151-41ca-8098-999f643fdf2a ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to 
install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1874124] Re: Add hw timestamps to received skbs in peak_canfd

[Sultan Alsawaf]

** Description changed:

+ [Impact]
+ 
  In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw
  timestamps were added to received messages in the peak_canfd driver.
  Backport the patch so users of our kernels can make use of the
  timestamps.
+ 
+ [Test case]
+ 
+ Apply the patch and compile.
+ 
+ [Fix]
+ 
+ Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F.
+ 
+ [Regression potential]
+ 
+ Low. This is a small upstream commit to an uncommonly used device
+ driver.

** Description changed:

  [Impact]
- 
- In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw
- timestamps were added to received messages in the peak_canfd driver.
- Backport the patch so users of our kernels can make use of the
- timestamps.
+ In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw 
timestamps were added to received messages in the peak_canfd driver. Backport 
the patch so users of our kernels can make use of the timestamps.
  
  [Test case]
- 
  Apply the patch and compile.
  
  [Fix]
- 
  Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F.
  
  [Regression potential]
- 
- Low. This is a small upstream commit to an uncommonly used device
- driver.
+ Low. This is a small upstream commit to an uncommonly used device driver.

** Description changed:

  [Impact]
  In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw 
timestamps were added to received messages in the peak_canfd driver. Backport 
the patch so users of our kernels can make use of the timestamps.
+ 
+ SF 274042.
  
  [Test case]
  Apply the patch and compile.
  
  [Fix]
  Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F.
  
  [Regression potential]
  Low. This is a small upstream commit to an uncommonly used device driver.

** Description changed:

  [Impact]
- In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw 
timestamps were added to received messages in the peak_canfd driver. Backport 
the patch so users of our kernels can make use of the timestamps.
- 
- SF 274042.
+ SF 274042: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, 
useful hw timestamps were added to received messages in the peak_canfd driver. 
Backport the patch so users of our kernels can make use of the timestamps.
  
  [Test case]
  Apply the patch and compile.
  
  [Fix]
  Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F.
  
  [Regression potential]
  Low. This is a small upstream commit to an uncommonly used device driver.

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

Title:
  Add hw timestamps to received skbs in peak_canfd

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  SF 274042: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, 
useful hw timestamps were added to received messages in the peak_canfd driver. 
Backport the patch so users of our kernels can make use of the timestamps.

  [Test case]
  Apply the patch and compile.

  [Fix]
  Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F.

  [Regression potential]
  Low. This is a small upstream commit to an uncommonly used device driver.

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

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

[Kernel-packages] [Bug 1874266] Re: Intensive NFS operations could lock whole system

[Paweł Hikiert]

Of course all apport information were collected prior to hangup. After
hangup running new processes is almost impossible (if it requires
performing some IO operations, and almost always it does).

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCm

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVersions

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

[Sultan Alsawaf]

@jlammrs You can't use that kernel with secure boot because it's
unsigned.

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

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

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

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

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

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0K0DFT:rvrA

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVersions:

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVe

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVersions:
   linux-

[Kernel-packages] [Bug 1874266] PciMultimedia.txt

[Paweł Hikiert]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1874266/+attachment/5358072/+files/PciMultimedia.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/1874266

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVers

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVersions:
   linux-re

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVersio

[Kernel-packages] [Bug 1874266] Re: Intensive NFS operations could lock whole system

[Paweł Hikiert]

apport information

** Tags added: apport-collected

** Description changed:

  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:
  
  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61
  
  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.23
+ Architecture: i386
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 16.04
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb:
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 vboxdrmfb
+ ProcKernelCmdLine: root=/dev/sda2 quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-177-generic N/A
+  linux-backports-modules-4.4.0-177-generic  N/A
+  linux-firmware 1.157.22
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-177-generic i686
+ UnreportableReason: The report belongs to a package that is not installed.
+ Upgr

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedP

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

[Paweł Hikiert]

apport information

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

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPackageVersions:
   linux-rest

[Kernel-packages] [Bug 1874266] Card0.Codecs.codec97.0.ac97.0-0.regs.txt

[Paweł Hikiert]

apport information

** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.regs.txt"
   
https://bugs.launchpad.net/bugs/1874266/+attachment/5358068/+files/Card0.Codecs.codec97.0.ac97.0-0.regs.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/1874266

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.

[Kernel-packages] [Bug 1874266] Card0.Codecs.codec97.0.ac97.0-0.txt

[Paweł Hikiert]

apport information

** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.txt"
   
https://bugs.launchpad.net/bugs/1874266/+attachment/5358067/+files/Card0.Codecs.codec97.0.ac97.0-0.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/1874266

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-

[Kernel-packages] [Bug 1874266] HookError_generic.txt

[Paweł Hikiert]

apport information

** Attachment added: "HookError_generic.txt"
   
https://bugs.launchpad.net/bugs/1874266/+attachment/5358070/+files/HookError_generic.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/1874266

Title:
  Intensive NFS operations could lock whole system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After last update from kernel version 4.4.0-176-generic to 4.4.0-177-generic 
my machine which does repository mirrors on NFS filesystem hung.
  After hang the system is pingable, and all processes run well until they need 
to perform IO operation. Then they end in 'D' state.
  If dmesg -w -H is run prior to hang you could get following report:

  [Apr22 16:06] INFO: task find:986 blocked for more than 120 seconds.
  [  +0.34]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.13] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.24] findD f4bbdd2c 0   986721 0x
  [  +0.10]  f4bbdd1c 0086 41ed78a0 f4bbdd2c eb5b7844 c1b36ec0 95907572 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab6e00 f4bbe000 f3ab6e00 f53ae3a8 f4bbdd28 
c17ec5cd
  [  +0.02]  01ff f4bbdd78 c11a8b57 f4bbdd3c f87bb75b f76ae800 f4bbdd50 
f87b2bdd
  [  +0.02] Call Trace:
  [  +0.06]  [] schedule+0x2d/0x80
  [  +0.12]  [] kmap_high+0x117/0x290
  [  +0.13]  [] ? nfs_revalidate_inode_rcu+0x1b/0x40 [nfs]
  [  +0.05]  [] ? nfs_check_verifier+0x6d/0x80 [nfs]
  [  +0.04]  [] ? kmem_cache_alloc_trace+0x185/0x1e0
  [  +0.12]  [] ? wake_up_q+0x70/0x70
  [  +0.03]  [] kmap+0x40/0x50
  [  +0.06]  [] nfs_readdir_xdr_to_array+0xdd/0x370 [nfs]
  [  +0.05]  [] ? nfs4_lookup_revalidate+0x25/0x140 [nfs]
  [  +0.02]  [] ? mem_cgroup_commit_charge+0x62/0xe0
  [  +0.11]  [] nfs_readdir_filler+0x1b/0x80 [nfs]
  [  +0.02]  [] do_read_cache_page+0x102/0x190
  [  +0.19]  [] ? nfs_readdir_xdr_to_array+0x370/0x370 [nfs]
  [  +0.02]  [] read_cache_page+0x24/0x30
  [  +0.04]  [] nfs_readdir+0x141/0x740 [nfs]
  [  +0.03]  [] ? _copy_to_user+0x26/0x30
  [  +0.02]  [] ? common_file_perm+0x55/0x1b0
  [  +0.16]  [] ? nfs4_xdr_dec_fsinfo+0x80/0x80 [nfsv4]
  [  +0.03]  [] iterate_dir+0x8e/0x130
  [  +0.02]  [] ? set_close_on_exec+0x62/0x70
  [  +0.02]  [] SyS_getdents64+0x6d/0xf0
  [  +0.01]  [] ? filldir+0x140/0x140
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.11]  [] sysenter_past_esp+0x3d/0x61
  [  +0.02] INFO: task bash:1065 blocked for more than 120 seconds.
  [  +0.15]   Not tainted 4.4.0-177-generic #207-Ubuntu
  [  +0.20] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  +0.18] bashD 0017 0  1065760 0x
  [  +0.02]  f1b87e44 0086 c11a799b 0017  f1f1eff8 b37c5095 
0025
  [  +0.03]  f4eb7e00 c1b1da80 f3ab3c00 f1b88000 f3ab3c00 f53b0298 f1b87e50 
c17ec5cd
  [  +0.02]  01ff f1b87ea0 c11a8b57 f3ab3c00 f3131000 f3ab3c00 0001 

  [  +0.02] Call Trace:
  [  +0.03]  [] ? follow_page_mask+0x16b/0x290
  [  +0.01]  [] schedule+0x2d/0x80
  [  +0.01]  [] kmap_high+0x117/0x290
  [  +0.02]  [] ? wake_up_q+0x70/0x70
  [  +0.01]  [] kmap+0x40/0x50
  [  +0.02]  [] copy_strings+0x1f8/0x2d0
  [  +0.02]  [] copy_strings_kernel+0x26/0x30
  [  +0.01]  [] do_execveat_common+0x479/0x6f0
  [  +0.02]  [] ? getname_flags+0x3a/0x1a0
  [  +0.01]  [] SyS_execve+0x34/0x40
  [  +0.02]  [] do_fast_syscall_32+0x9f/0x190
  [  +0.02]  [] sysenter_past_esp+0x3d/0x61

  I did NOT noticed such behaviour on x86_64 architecture, only on i386.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-177-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: root=/dev/sda2 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  RelatedPac

[Kernel-packages] [Bug 1874309] [NEW] package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned

[Саша Поповић]

Public bug reported:

Steps to reproduce:
(In virtualbox)

terminal->
sudo apt install virtualbox-guest-utils-hwe virtualbox-guest-dkms-hwe 
virtualbox-guest-x11-hwe

during installation, all kernels and modules are erased, and error screen 
stating that user will not be able to log in if every kernel is erased is 
presented. After selecting yes, process is aborted. 
After that, deleted packages are reinstalled with
sudo apt install linux-generic linux-modules-extra-5.4.0-21-generic 
linux-image-5.4.0-21-generic linux-image-generic 
linux-modules-extra-5.4.0-25-generic linux-image-5.4.0-25-generic

Upon every consequent reboot, error pops up on screen, and asks user to
send information.


Ubuntu 5.4.0-25.29-generic 5.4.30

Description:Ubuntu 20.04 LTS
Release:20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-25-generic 5.4.0-25.29
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pixxel 1620 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Apr 20 15:04:22 2020
ErrorMessage: installed linux-image-5.4.0-25-generic package pre-removal script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-04-20 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
MachineType: innotek GmbH VirtualBox
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic 
root=UUID=1e4016f9-5151-41ca-8098-999f643fdf2a ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
RfKill:
 
SourcePackage: linux
Title: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to 
install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package focal

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1874309/+attachment/5358046/+files/lspci-vnvn.log

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

Title:
  package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to
  install/upgrade: installed linux-image-5.4.0-25-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  (In virtualbox)

  terminal->
  sudo apt install virtualbox-guest-utils-hwe virtualbox-guest-dkms-hwe 
virtualbox-guest-x11-hwe

  during installation, all kernels and modules are erased, and error screen 
stating that user will not be able to log in if every kernel is erased is 
presented. After selecting yes, process is aborted. 
  After that, deleted packages are reinstalled with
  sudo apt install linux-generic linux-modules-extra-5.4.0-21-generic 
linux-image-5.4.0-21-generic linux-image-generic 
linux-modules-extra-5.4.0-25-generic linux-image-5.4.0-25-generic

  Upon every consequent reboot, error pops up on screen, and asks user
  to send information.

  
  Ubuntu 5.4.0-25.29-generic 5.4.30

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-25-generic 5.4.0-25.29
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:

[Kernel-packages] [Bug 1874307] [NEW] Xserver crashes after resuming from sleep

[Mathieu Tarral]

Public bug reported:

I am experiencing frequent Gnome-Shell crashes when resuming from sleep mode.
The screen is flickering and Gnome-Shell is creating a new session instead of 
restoring the old one.

After investigation with the Gnome team, we realized that the real issue is the 
X server crashing:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2495

The log messages suggest that this issue might be related to the Nvidia
driver:

avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) modeset(G0): 
failed to set mode: No space left on device
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Fatal server error:
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) EnterVT failed 
for gpu screen 0
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Please consult the 
The X.Org Foundation support
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]:  at 
http://wiki.x.org
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]:  for help.
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Please also 
check the log file at "/home/wenzel/.local/share/xorg/Xorg.1.log" for 
additional information.
avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)

avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Server
terminated with error (1). Closing log file.


Especially "EnterVT failed for gpu screen 0"

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-video-nvidia-435 435.21-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 22 20:34:17 2020
InstallationDate: Installed on 2019-09-26 (209 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: nvidia-graphics-drivers-435
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-435 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  Xserver crashes after resuming from sleep

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

Bug description:
  I am experiencing frequent Gnome-Shell crashes when resuming from sleep mode.
  The screen is flickering and Gnome-Shell is creating a new session instead of 
restoring the old one.

  After investigation with the Gnome team, we realized that the real issue is 
the X server crashing:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2495

  The log messages suggest that this issue might be related to the
  Nvidia driver:

  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) modeset(G0): 
failed to set mode: No space left on device
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Fatal server 
error:
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) EnterVT 
failed for gpu screen 0
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Please consult 
the The X.Org Foundation support
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]:  at 
http://wiki.x.org
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]:  for help.
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Please also 
check the log file at "/home/wenzel/.local/share/xorg/Xorg.1.log" for 
additional information.
  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)

  avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE)
  Server terminated with error (1). Closing log file.

  
  Especially "EnterVT failed for gpu screen 0"

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nvidia-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 20:34:17 2020
  InstallationDate: Installed on 2019-09-26 (209 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: nvidia-graphics-drivers-435
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-gr

[Kernel-packages] [Bug 1874305] 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 1874305

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

Title:
  Wifi goes down when change bluetooth configuration

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  WiFi connection goes down when having a Bluetooth headset connected and 
change from A2DP to HSP. 
  The connection goes down instantly. If you change back to A2DP connection 
works again, but in some cases it goes down forever till you disconnect from 
the current WiFi and connect again.

  [How to reproduce]
   1. connect a Bluetooth headset and change from A2DP to HSP.

  [System Info]
   Ubuntu 5.4.0-24.28-generic 5.4.30
   03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
   
   No LSB modules are available.
   Distributor ID:  Ubuntu
   Description: Ubuntu 20.04 LTS
   Release: 20.04
   Codename:focal

  [DMESG info]
  348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072
  [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48
  [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0

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

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

[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.1

---
ubuntu-drivers-common (1:0.8.1) focal; urgency=medium

  [ Alberto Milone ]
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py,
tests/test_ubuntu_drivers.py,
ubuntu-drivers:
- Add tests for the -generic-hwe-20.04 flavour and for
  the -oem-20.04 linux flavour.
- Add detection logic to get the linux metapackage and
  linux-modules for -hwe-20.04 (LP: #1873867).
- List the modules provider when it is either a dkms package
  or a linux-modules package.
- Install linux-modules packages when available.
  This makes the NVIDIA drivers work with Secure Boot.

  [ Dimitri John Ledkov ]
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py:
- Use exact matching in find_reverse_deps() with both
  installed and candidate.

 -- Alberto Milone   Tue, 21 Apr 2020
21:14:15 +0200

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Kernel-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules -
5.4.0-26.30+1

---
linux-restricted-modules (5.4.0-26.30+1) focal; urgency=medium

  * Can't install any packages with ubuntu-drivers using ubuntu-drivers when
invoked from ubiquity (LP: #1874278)
- [Packaging] work around lack of debconf in the installer host

 -- Andy Whitcroft   Wed, 22 Apr 2020 17:03:46 +0100

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

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

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

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

[Kernel-packages] [Bug 1874305] [NEW] Wifi goes down when change bluetooth configuration

[Leonidas S. Barbosa]

Public bug reported:

WiFi connection goes down when having a Bluetooth headset connected and change 
from A2DP to HSP. 
The connection goes down instantly. If you change back to A2DP connection works 
again, but in some cases it goes down forever till you disconnect from the 
current WiFi and connect again.

[How to reproduce]
 1. connect a Bluetooth headset and change from A2DP to HSP.

[System Info]
 Ubuntu 5.4.0-24.28-generic 5.4.30
 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter (rev 31)
 
 No LSB modules are available.
 Distributor ID:Ubuntu
 Description:   Ubuntu 20.04 LTS
 Release:   20.04
 Codename:  focal

[DMESG info]
348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0
[348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072
[348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48
[348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0

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


** Tags: focal

** Attachment added: "lscpi -vnvn file"
   
https://bugs.launchpad.net/bugs/1874305/+attachment/5358029/+files/lspci-vnvn.log

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

Title:
  Wifi goes down when change bluetooth configuration

Status in linux package in Ubuntu:
  New

Bug description:
  WiFi connection goes down when having a Bluetooth headset connected and 
change from A2DP to HSP. 
  The connection goes down instantly. If you change back to A2DP connection 
works again, but in some cases it goes down forever till you disconnect from 
the current WiFi and connect again.

  [How to reproduce]
   1. connect a Bluetooth headset and change from A2DP to HSP.

  [System Info]
   Ubuntu 5.4.0-24.28-generic 5.4.30
   03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
   
   No LSB modules are available.
   Distributor ID:  Ubuntu
   Description: Ubuntu 20.04 LTS
   Release: 20.04
   Codename:focal

  [DMESG info]
  348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0
  [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072
  [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48
  [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0

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

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

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

[Jozef Lammers]

@Andrea, can I use this kernel with UEFI/SecureBoot?

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

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

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

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

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

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0K0DFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0K0DFT:rvrA00:cvnDellInc.:ct10:cv

[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Dimitri John Ledkov]

I am very happy with the new  ubuntu-drivers-common and l-r-m in
proposed! Installed all the right things, with latelink=false on the
host system, and latelink=true in target.

Just need all of these to migrate, respin, retest, ship.

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

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev

[Paul Larson]

I'm pretty sure it gets links to the artifacts that it needs via streams
at http://images.maas.io/ephemeral-v3/daily/focal/amd64/

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

Title:
  failed to boot focal image in maas: /root.tmp.img: can't open blockdev

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
  /root.tmp.img: can't open blockdev

  I'll also post the images of the screen for further details.

  There are other devices that boot the image from maas just fine, but I
  did try re-importing it just to be sure nothing was messed up with it.

  The two systems we're having problems with at the moment are:
  - Dell latitude 5758 i5-5200
  - Dell latitude 5759 i5-6200
  It's unknown yet whether there are others affected by this.

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

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

[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

[Marcel Munce]

Yes, I have a Dual Boot Setup with Ubuntu as primary System.

I actually don't know what happened between the time it was working and
then stopped...

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

[Kai-Heng Feng]

Do you happen to dual boot to Windows?

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev

[Colin Ian King]

I'm not familiar with the way these are being provisioned.  What images
exact are you provisioning them with and how is mass kicking off the
install?

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  failed to boot focal image in maas: /root.tmp.img: can't open blockdev

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
  /root.tmp.img: can't open blockdev

  I'll also post the images of the screen for further details.

  There are other devices that boot the image from maas just fine, but I
  did try re-importing it just to be sure nothing was messed up with it.

  The two systems we're having problems with at the moment are:
  - Dell latitude 5758 i5-5200
  - Dell latitude 5759 i5-6200
  It's unknown yet whether there are others affected by this.

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

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

[Kernel-packages] [Bug 1874286] Re: Add debian/rules targets to compile/run kernel selftests

[Kleber Sacilotto de Souza]

** Description changed:

- [Impact] 
+ [Impact]
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.
  
  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in order
  to be able to detect such breaks.
  
  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:
  
  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests
  
- [Regression Potential] 
- None. This only adds a new rules target that will not break any existing 
target.
+ [Regression Potential]
+ None. This only adds new rules targets that will not break any existing 
targets.

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

Title:
  Add debian/rules targets to compile/run kernel selftests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in
  order to be able to detect such breaks.

  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:

  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests

  [Regression Potential]
  None. This only adds new rules targets that will not break any existing 
targets.

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

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

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Colin Ian King]

BTW, Is this still and open issue?

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 0033:0x7fc305a905d7
  [  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 
0010
  [  967.637943] RAX: ffda RBX: 5a46 RCX: 
7fc305a905d7
  [  967.637945] RDX: 7ffc4

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Colin Ian King]

*still an open issue?

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 0033:0x7fc305a905d7
  [  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 
0010
  [  967.637943] RAX: ffda RBX: 5a46 RCX: 
7fc305a905d7
  [  967.637945] RDX: 7ffc45e39630 RSI: 

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[suKo]

Using an NVIDIA GTX 1080 on 20.04 with the latest daily image I can
confirm this bug still exists. Removing the "splash" option from the
/etc/default/grub file variable GRUB_CMDLINE_LINUX_DEFAULT seems to fix
the issue. I too encountered this with automatic boot enabled, and it
also occurs no matter which version of the NVIDIA driver I use (except
for the FOSS driver). Unusually, this does not occur on my laptop which
also has an NVIDIA GPU (in this case, a 1650).

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserve

[Kernel-packages] [Bug 1874286] Re: Add debian/rules targets to compile/run kernel selftests

[Kleber Sacilotto de Souza]

** Summary changed:

- Add a debian/rules target to compile/run kernel selftests
+ Add debian/rules targets to compile/run kernel selftests

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

Title:
  Add debian/rules targets to compile/run kernel selftests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact] 
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in
  order to be able to detect such breaks.

  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:

  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests

  [Regression Potential] 
  None. This only adds a new rules target that will not break any existing 
target.

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

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

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Colin Ian King]

Incidentally, dnode_free_range hasn't changed much in the focal 8.2.x
zfs, so I'm not sure if upgrading to that will make much of a
difference.

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 0033:0x7fc305a905d7
  [  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 
0010
  [  9

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Colin Ian King]

In this scenario, dmu_object_free has been called and this calls
dnode_free_range using dnode_free_range(dn, 0, DMU_OBJECT_END, tx)

In this case, in dnode_free_range len is DMU_OBJECT_ENDand offset is 0,
so..:

if (len == DMU_OBJECT_END) {
len = UINT64_MAX - off;
trunc = TRUE;
}

makes len is UINT64_MAX and trunc = TRUE. If one follows the code
through we have this stanza:

blkid = off >> blkshift;
nblks = len >> blkshift;
if (trunc)
nblks += 1;

and this is the last place nblks gets updated. This implies blkshift is
zero, nblks = UINT64_MAX >> 0 is UINT64_MAX, trunc is TRUE so nblks +=1
wraps nblks back to 0, hence the assert later on.

For blkshift to be zero blksz dn->dn_datablksz is zero, so this looks
like some form of corruption.

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [

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

[Andrea Righi]

This looks similar to LP: #1861395

I've prepared a test kernel (5.3.0-48.41+lp1861395v1), backporting the
following fixes that seems to have fixed the problem in 5.4:

 b1339ecac661 drm/i915/execlists: Always force a context reload when rewinding 
RING_TAIL
 f26a9e959a7b drm/i915/gt: Detect if we miss WaIdleLiteRestore
 22b7a426bbe1 drm/i915/execlists: Preempt-to-busy

Test kernel is available here:
https://kernel.ubuntu.com/~arighi/LP-1861395/5.3/

It'd be great if you could give it a try, thanks.

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

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

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

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

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

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

  I note another user has reported similar issues on the same kernel at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  3920 F pulseaudio
   /dev/snd/pcmC0D0p:   steve  3920 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.3
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2019-12-27 (104 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  MachineType: Dell Inc. Inspiron 5580
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  tricia
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install

[Kernel-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Steve Langasek]

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Kernel-packages] [Bug 1874286] 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 1874286

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
   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/1874286

Title:
  Add a debian/rules target to compile/run kernel selftests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact] 
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in
  order to be able to detect such breaks.

  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:

  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests

  [Regression Potential] 
  None. This only adds a new rules target that will not break any existing 
target.

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

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

[Kernel-packages] [Bug 1874286] Re: Add a debian/rules target to compile/run kernel selftests

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Precise)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

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

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

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

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

Title:
  Add a debian/rules target to compile/run kernel selftests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact] 
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in
  order to be able to detect such breaks.

  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:

  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests

  [Regression Potential] 
  None. This only adds a new rules target that will not break any existing 
target.

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

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

[Kernel-packages] [Bug 1874286] [NEW] Add a debian/rules target to compile/run kernel selftests

[Kleber Sacilotto de Souza]

Public bug reported:

[Impact] 
When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

I am proposing that we add some simple debian/rules targets that will
keep a list of the selftests that Ubuntu cares about, compile and run
them. This could be plugged into our test build infrastructure in order
to be able to detect such breaks.

[Test Case]
With these changes, one would be able to run the following to compile/run the 
selftests:

# fakeroot debian/rules clean
# fakeroot debian/rules compileselftests
# fakeroot debian/rules runselftests

[Regression Potential] 
None. This only adds a new rules target that will not break any existing target.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kleber Sacilotto de Souza (kleber-souza)
 Status: In Progress

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

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

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

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

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

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

Title:
  Add a debian/rules target to compile/run kernel selftests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact] 
  When compiling and building the Ubuntu kernels, the kernel selftests located 
under 'tools/testing/selftests/' do not get compiled. Some of these testcases 
are used by our test infrastructure, which downloads the kernel source, 
compiles and run them. The problem with this approach is that patches applied 
to the testcases can break the compilation and this is detected only after the 
kernels are already released to -proposed.

  I am proposing that we add some simple debian/rules targets that will
  keep a list of the selftests that Ubuntu cares about, compile and run
  them. This could be plugged into our test build infrastructure in
  order to be able to detect such breaks.

  [Test Case]
  With these changes, one would be able to run the following to compile/run the 
selftests:

  # fakeroot debian/rules clean
  # fakeroot debian/rules compileselftests
  # fakeroot debian/rules runselftests

  [Regression Potential] 
  None. This only adds a new rules target that will not break any existing 
target.

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

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

[Kernel-packages] [Bug 1864005] Re: Fix AMD Stoney Ridge screen flickering under 4K resolution

[Kleber Sacilotto de Souza]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Fix AMD Stoney Ridge screen flickering under 4K resolution

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display.

  [Fix]
  Disable IOMMU on Stoney Ridge.

  [Test]
  Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be
  observed.
  The flickering/tearing is gone once the patch is applied.

  [Regression Potential]
  Low. This fix limits to one specific SoC.
  According to AMD, IOMMU isn't enabled for this SoC under Windows.
  So it's expected behavior.

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

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

[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

[Po-Hsu Lin]

Hello, Marcel
Is that the same 5.3.0-42 kernel that's not working in your comment #19?

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight

[Po-Hsu Lin]

Marked as incomplete for request in comment #6
please change it back to confirmed after the test.

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

Title:
  [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust
  brightness of backlight

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am unable to adjust the brightness of the backlight of my laptop
  screen either by using the slider of by changing the value in
  /sys/class/backlight/intel_backlight/brightness directly.

  I have tried changing my GRUB configuration:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  But that did not help.

  I am using Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 14:03:33 2019
  DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
   NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] 
[1558:65d1]
  InstallationDate: Installed on 2019-10-09 (30 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Notebook PB50_70RF,RD,RC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: PB50_70RF,RD,RC
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: PB50_70RF,RD,RC
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic

[Po-Hsu Lin]

Closing this bug as per Mario's response in comment #19

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

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

Title:
  [Dell XPS 15 9575] Screen brightness stopped working with linux-
  image-5.4.0-9-generic

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I upgraded to Focal Fossa 3 days ago and nothing broke. At the time,
  it was still using linux 5.3 (linux-image-5.3.0-24-generic).

  Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after
  rebooting, the screen brightness does not work anymore - neither from
  keyboard keys nor from the slider in the gnome-shell panel.

  It works again when rebooting into the previous linux-
  image-5.3.0-24-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mario  1892 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 20:23:31 2020
  InstallationDate: Installed on 2018-09-13 (481 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1867060] Re: no brightness control support on Aspire A715-72G

[Po-Hsu Lin]

Marked as Incomplete for request in comment #3

Please change it back to confirmed after pasting the debug result.
Thanks

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

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

Title:
  no brightness control support on Aspire A715-72G

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness disappear, no entries in /sys/class/backlight

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brian  1822 F pulseaudio
   /dev/snd/controlC1:  brian  1822 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 03:10:15 2020
  InstallationDate: Installed on 2020-03-10 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A715-72G
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=405a07bf-f671-40e7-984b-b478fb7b70e3 ro quiet splash nomodeset 
acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmeleon_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnAspireA715-72G:pvrV1.28:rvnCFL:rnCharmeleon_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-72G
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1872229] Re: screen backlight can't be changed

[Po-Hsu Lin]

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

Mark it as dup for bug 1866994, 
if the kernel in -proposed can't solve your problem, please feel free to remove 
the dup.
Thanks.

** This bug has been marked a duplicate of bug 1866994
   Screen backlight control not working on Dell XPS 15 7590

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

Title:
  screen backlight can't be changed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  changing the screen brightness in the Ubuntu settings does not change the 
brightness of the screen.
  Changing the brightness for example with the fn keys changes the value in 
/sys/class/backlight/dell_backlight/brightness but not the screen brightness. 
There is also a /sys/class/backlight/intel_backlight but changing the 
brightness file there manually also has no effect. 

  The acpi_backlight=vendor option did not work out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benedict   1744 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 20:38:51 2020
  InstallationDate: Installed on 2020-04-08 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. XPS 15 7590
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=8bbcafe3-01fd-4b8e-8924-1c0d0efa9270 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0T8KGX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/11/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1874279] 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 1874279

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

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

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

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

** Tags added: focal

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

Title:
  failed to boot focal image in maas: /root.tmp.img: can't open blockdev

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
  /root.tmp.img: can't open blockdev

  I'll also post the images of the screen for further details.

  There are other devices that boot the image from maas just fine, but I
  did try re-importing it just to be sure nothing was messed up with it.

  The two systems we're having problems with at the moment are:
  - Dell latitude 5758 i5-5200
  - Dell latitude 5759 i5-6200
  It's unknown yet whether there are others affected by this.

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

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

[Kernel-packages] [Bug 1865406] Re: Add support to test 5.0 Bionic kernel

[Po-Hsu Lin]

In that case I think I can revert this in KT.
Thanks for the info!

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

Title:
  Add support to test 5.0 Bionic kernel

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

Bug description:
  For Bionic-5.0 hwe kernel, the requested meta package "linux-generic-
  hwe-18.04-5.0" from the test request is not available:

  sudo DEBIAN_FRONTEND=noninteractive UCF_FORCE_CONFFNEW=1 apt-get install 
--yes linux-generic-hwe-18.04-5.0
 ShellError Raised
 Reading package lists...
 Building dependency tree...
 Reading state information...
 E: Unable to locate package linux-generic-hwe-18.04-5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-76-generic 4.15.0-76.86
  ProcVersionSignature: User Name 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  2 03:09 seq
   crw-rw 1 root audio 116, 33 Mar  2 03:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Mar  2 03:12:05 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-76-generic N/A
   linux-backports-modules-4.15.0-76-generic  N/A
   linux-firmware 1.173.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867218] Re: Ubuntu 18.04 running 5.0.0.23 kernel contains bios measurements in SHA1 instead of SHA256

[Marcelo Cerri]

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

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

Title:
  Ubuntu 18.04 running 5.0.0.23 kernel contains bios measurements in
  SHA1 instead of SHA256

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Ubuntu18.04 running Linux Kernel 5.0.0.23 logs bios measurements in
  SHA1 instead of SHA256. OS attestation mechanisms that we are working
  on expect the bios measurements to have SHA256 digests. Is it possible
  to make sure that the measurements are SHA256 instead of SHA1.

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

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

[Kernel-packages] [Bug 1874278] [NEW] Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Iain Lane]

Public bug reported:

We are in the process of switching ubuntu-drivers to installing linux-
restricted-modules versions of NVidia drivers when it can, but this
fails when Ubiquity invokes ubuntu-drivers, like:

Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
 /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 3: B
ad file descriptor
 dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic (--con
figure):
  installed linux-modules-nvidia-440-5.4.0-25-generic package post-installation 
script subprocess returned error exit status 2
 dpkg: dependency problems prevent configuration of linux-modules-nvidia-440-gen
eric-hwe-20.04:
  linux-modules-nvidia-440-generic-hwe-20.04 depends on linux-modules-nvidia-440
-5.4.0-25-generic (= 5.4.0-25.29); however:
   Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
 
 dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
  dependency problems - leaving unconfigured

It's a problem with the nesting of debconf: Ubiquity itself is using
debconf, and ubuntu-drivers is installing -nvidia- packages which
themselves also use debconf, and we don't know how to connect ubuntu-
drivers use of debconf with the ubiquity one.

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

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

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

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

** Summary changed:

- Can't install any packages via ubuntu-drivers which use debconf
+ Can't install any packages from ubiquity via ubuntu-drivers which use debconf

** Summary changed:

- Can't install any packages from ubiquity via ubuntu-drivers which use debconf
+ Can't install any packages with ubuntu-drivers using ubuntu-drivers when 
invoked from ubiquity

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

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

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

[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev

[Paul Larson]

Screenshot 1 with errors at boot

** Attachment added: "20200422_111045.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+attachment/5358002/+files/20200422_111045.jpg

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

Title:
  failed to boot focal image in maas: /root.tmp.img: can't open blockdev

Status in linux package in Ubuntu:
  New

Bug description:
  We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
  /root.tmp.img: can't open blockdev

  I'll also post the images of the screen for further details.

  There are other devices that boot the image from maas just fine, but I
  did try re-importing it just to be sure nothing was messed up with it.

  The two systems we're having problems with at the moment are:
  - Dell latitude 5758 i5-5200
  - Dell latitude 5759 i5-6200
  It's unknown yet whether there are others affected by this.

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

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

[Kernel-packages] [Bug 1867002] Re: Add XHCI/USB support to linux-azure

[Marcelo Cerri]

** Changed in: linux-azure (Ubuntu Disco)
   Status: Fix Committed => Invalid

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

Title:
  Add XHCI/USB support to linux-azure

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Disco:
  Invalid
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released

Bug description:
  Enable xHCI for PCI passthrough for USB support.

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

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

[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev

[Paul Larson]

Screenshot 2 with errors at boot

** Attachment added: "20200422_112031.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+attachment/5358003/+files/20200422_112031.jpg

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

Title:
  failed to boot focal image in maas: /root.tmp.img: can't open blockdev

Status in linux package in Ubuntu:
  New

Bug description:
  We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
  /root.tmp.img: can't open blockdev

  I'll also post the images of the screen for further details.

  There are other devices that boot the image from maas just fine, but I
  did try re-importing it just to be sure nothing was messed up with it.

  The two systems we're having problems with at the moment are:
  - Dell latitude 5758 i5-5200
  - Dell latitude 5759 i5-6200
  It's unknown yet whether there are others affected by this.

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

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

[Kernel-packages] [Bug 1874279] [NEW] failed to boot focal image in maas: /root.tmp.img: can't open blockdev

[Paul Larson]

Public bug reported:

We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
/root.tmp.img: can't open blockdev

I'll also post the images of the screen for further details.

There are other devices that boot the image from maas just fine, but I
did try re-importing it just to be sure nothing was messed up with it.

The two systems we're having problems with at the moment are:
- Dell latitude 5758 i5-5200
- Dell latitude 5759 i5-6200
It's unknown yet whether there are others affected by this.

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

Title:
  failed to boot focal image in maas: /root.tmp.img: can't open blockdev

Status in linux package in Ubuntu:
  New

Bug description:
  We have at least two systems in our lab that are seeing this problem. Both of 
them are able to boot other images (bionic, etc) just fine, and at least one of 
them was definitely booting focal earlier this week from the stream import in 
maas. But now, whenever we try to provision them with the focal image, it fails 
to boot for provisioning.  I got someone to look at the console and take 
pictures (no serial or bmc on these, sorry) and they were dropped to busybox on 
boot. One error did jump out in dmesg:
  /root.tmp.img: can't open blockdev

  I'll also post the images of the screen for further details.

  There are other devices that boot the image from maas just fine, but I
  did try re-importing it just to be sure nothing was messed up with it.

  The two systems we're having problems with at the moment are:
  - Dell latitude 5758 i5-5200
  - Dell latitude 5759 i5-6200
  It's unknown yet whether there are others affected by this.

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[ricsdeol]

Hi, Dell G3 3579 (086F)
Ubuntu 20.04

LOG: 
[72720.138307] pcieport :00:1d.6: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[72720.138314] pcieport :00:1d.6: AER:   device [8086:a336] error 
status/mask=1000/2000
[72720.138320] pcieport :00:1d.6: AER:[12] Timeout   

PCI INFO:
➜ sudo lspci -v 
00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Processor Host 
Bridge/DRAM Registers [Coffee Lake H] (rev 07)
DeviceName: Onboard - Other
Subsystem: Dell 8th Gen Core 4-core Processor Host Bridge/DRAM 
Registers [Coffee Lake H]
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=10 
Kernel driver in use: skl_uncore

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 122
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 4000-4fff [size=4K]
Memory behind bridge: a300-a40f [size=17M]
Prefetchable memory behind bridge: 9000-a1ff 
[size=288M]
Capabilities: [88] Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor PCIe Controller (x16)
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [a0] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [140] Root Complex Link
Capabilities: [d94] Secondary PCI Express
Kernel driver in use: pcieport

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) 
(prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: Dell UHD Graphics 630 (Mobile)
Flags: bus master, fast devsel, latency 0, IRQ 130
Memory at a200 (64-bit, non-prefetchable) [size=16M]
Memory at 8000 (64-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c 
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Process Address Space ID (PASID)
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Thermal Subsystem (rev 07)
DeviceName: Onboard - Other
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem
Flags: fast devsel, IRQ 16
Memory at a461 (64-bit, non-prefetchable) [size=32K]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 3
Capabilities: [e0] Vendor Specific Information: Len=0c 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th/8th Gen Core Processor Gaussian Mixture Model
DeviceName: Onboard - Other
Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core 
Processor Gaussian Mixture Model
Flags: fast devsel, IRQ 255
Memory at a4628000 (64-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [dc] Power Management version 2
Capabilities: [f0] PCI Advanced Features

00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal 
Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Dell Cannon Lake PCH Thermal Controller
Flags: fast devsel, IRQ 16
Memory at a4627000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host 
Controller (rev 10) (prog-if 30 [XHCI])
DeviceName: Onboard - Other
Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller
Flags: bus master, medium devsel, latency 0, IRQ 126
Memory at a460 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Capabilities: [90] Vendor Specific Information: Len=14 
Kernel driver in use: xhci_hc

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

[bugproxy]

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

--- Comment From lagar...@br.ibm.com 2020-04-22 10:53 EDT---
My understanding is that at this point Canonical is not accepting new features 
into Ubuntu 16.04, even simple ones as this one.

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

Title:
  Provide mode where all vCPUs on a core must be the same VM

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Leonardo Augusto Guimaraes Garcia  - 
2018-09-13 07:33:25 ==
  +++ This bug was initially created as a clone of Bug #171443 +++

  Please, add the following patch:

  http://patchwork.ozlabs.org/patch/968786/

  which adds a mode where all vCPUs on a core must be the same VM on
  POWER8 and POWER9.

  This is intended for use in security-conscious settings where users
  are concerned about possible side-channel attacks between threads
  which could perhaps enable one VM to attack another VM on the same
  core, or the host.

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

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

[Kernel-packages] [Bug 1865406] Re: Add support to test 5.0 Bionic kernel

[Sean Feole]

Sam, linux-image-virtual-gkeop-5.0 has been testing in the GKE cloud on
baremetal and virtual instances.  This package does not need to consume
resources in the metal labs. I would prefer it not be tested in any of
the MAAS clouds.

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

Title:
  Add support to test 5.0 Bionic kernel

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

Bug description:
  For Bionic-5.0 hwe kernel, the requested meta package "linux-generic-
  hwe-18.04-5.0" from the test request is not available:

  sudo DEBIAN_FRONTEND=noninteractive UCF_FORCE_CONFFNEW=1 apt-get install 
--yes linux-generic-hwe-18.04-5.0
 ShellError Raised
 Reading package lists...
 Building dependency tree...
 Reading state information...
 E: Unable to locate package linux-generic-hwe-18.04-5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-76-generic 4.15.0-76.86
  ProcVersionSignature: User Name 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  2 03:09 seq
   crw-rw 1 root audio 116, 33 Mar  2 03:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Mar  2 03:12:05 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-76-generic N/A
   linux-backports-modules-4.15.0-76-generic  N/A
   linux-firmware 1.173.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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