date:20200424

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

Title:
  Activation of network connection failed - TP-Link TL-WN8200ND [Realtek
  RTL8192CU]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can't connect to any WIFI network. I'm getting a popup message
  "Activation of network connection failed" using a TP Link TL-WN8200ND,
  Realtek8192CU.

  
  More info on this thread:
  https://ubuntuforums.org/showthread.php?t=2439662

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-46-generic 5.3.0-46.38
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ramiro 1852 F pulseaudio
   /dev/snd/controlC0:  ramiro 1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 23:21:35 2020
  HibernationDevice: RESUME=UUID=d17302fc-9fd5-4b96-9d4a-17a0272bd0bd
  InstallationDate: Installed on 2016-06-13 (1411 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=f5d7a7ab-6a3d-47e6-83d8-96ecb50dbedd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.183.5
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (185 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

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

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

Title:
  Activation of network connection failed - TP-Link TL-WN8200ND [Realtek
  RTL8192CU]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Can't connect to any WIFI network. I'm getting a popup message
  "Activation of network connection failed" using a TP Link TL-WN8200ND,
  Realtek8192CU.

  
  More info on this thread:
  https://ubuntuforums.org/showthread.php?t=2439662

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-46-generic 5.3.0-46.38
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ramiro 1852 F pulseaudio
   /dev/snd/controlC0:  ramiro 1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 23:21:35 2020
  HibernationDevice: RESUME=UUID=d17302fc-9fd5-4b96-9d4a-17a0272bd0bd
  InstallationDate: Installed on 2016-06-13 (1411 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=f5d7a7ab-6a3d-47e6-83d8-96ecb50dbedd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.183.5
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (185 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Kernel-packages] [Bug 1874958] Re: Activation of network connection failed - TP-Link TL-WN8200ND [Realtek RTL8192CU]

2020-04-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Activation of network connection failed - TP-Link TL-WN8200ND [Realtek
  RTL8192CU]

Status in linux package in Ubuntu:
  New

Bug description:
  Can't connect to any WIFI network. I'm getting a popup message
  "Activation of network connection failed" using a TP Link TL-WN8200ND,
  Realtek8192CU.

  
  More info on this thread:
  https://ubuntuforums.org/showthread.php?t=2439662

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-46-generic 5.3.0-46.38
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ramiro 1852 F pulseaudio
   /dev/snd/controlC0:  ramiro 1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 23:21:35 2020
  HibernationDevice: RESUME=UUID=d17302fc-9fd5-4b96-9d4a-17a0272bd0bd
  InstallationDate: Installed on 2016-06-13 (1411 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=f5d7a7ab-6a3d-47e6-83d8-96ecb50dbedd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.183.5
  RfKill:
   1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (185 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Kernel-packages] [Bug 1874958] [NEW] Activation of network connection failed - TP-Link TL-WN8200ND [Realtek RTL8192CU]

You have been subscribed to a public bug:

Can't connect to any WIFI network. I'm getting a popup message
"Activation of network connection failed" using a TP Link TL-WN8200ND,
Realtek8192CU.


More info on this thread:
https://ubuntuforums.org/showthread.php?t=2439662

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-46-generic 5.3.0-46.38
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ramiro 1852 F pulseaudio
 /dev/snd/controlC0:  ramiro 1852 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 23:21:35 2020
HibernationDevice: RESUME=UUID=d17302fc-9fd5-4b96-9d4a-17a0272bd0bd
InstallationDate: Installed on 2016-06-13 (1411 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=f5d7a7ab-6a3d-47e6-83d8-96ecb50dbedd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-46-generic N/A
 linux-backports-modules-5.3.0-46-generic  N/A
 linux-firmware1.183.5
RfKill:
 1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-22 (185 days ago)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

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


** Tags: amd64 apport-bug eoan
-- 
Activation of network connection failed - TP-Link TL-WN8200ND [Realtek 
RTL8192CU]
https://bugs.launchpad.net/bugs/1874958
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

2020-04-24 Thread Can Peter Yildirim

I installed this kernel to check to see if the issue was fixed for me as well:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.28/

I found that it did not solve the problem, I still get the long delay on
resume

```
[ 1097.833212] usb 1-7: reset high-speed USB device number 4 using xhci_hcd
[ 1142.739475] ucsi_ccg 0-0008: PPM NOT RESPONDING
[ 1142.739486] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 [ucsi_ccg] 
returns -110
[ 1142.739489] PM: Device 0-0008 failed to resume: error -110
```

does this kernel not have the fix in it, if not, What release version
contains this 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/1850238

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

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

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

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

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

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

  === Original Bug Report ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1848831] Re: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi

2020-04-24 Thread Christian Ohrfandl

I get the same propblem on Ubuntu 20.04

uname -a
Linux christian-vie-ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

sudo lspci -vvnk -s 01:00.0
01:00.0 0280: 8086:2723 (rev 1a)
Subsystem: 8086:0084
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1848831

Title:
  Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading
  error resulting in no wifi

Status in Gaming Edition:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 |

[Kernel-packages] [Bug 1858811] Re: Linux 5.3.0-26-generic kernel

2020-04-24 Thread Gerald Rozner

Just did a fresh install of Ubuntu 20.04 LTS on a NUC replacing 19.10.
The aforementioned issue has changed and it appears whatever was changed
post 5.3.0-24 was done intentionally.

The machine finishes post and the normal Intel NUC splash screen appears
with the F Keys displayed. The screen stays longer than before with the
F Keys slowly fading away to be replaced with only the Intel NUC splash
and the new Ubuntu logo. Both sharing the same screen. Then continuing
on to the normal desktop if the auto login is enabled. The entire
process about 7 seconds.

I don't think this is a bug as I reported it. Folks that actually work
on the kernel would know more than I but this certainly looks like the
latest kernel was designed to use and control the Intel splash screen.

On the Z77 using legacy boot the screen just stays black and boots in
the same amount of time.

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

Title:
  Linux 5.3.0-26-generic kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just after installation and reboot of Linux 5.3.0-26 kernel and reboot
  on two NUC machines UEFI they displayed the normal Intel splash screen
  followed by the normal grub menu. Then went back to the Intel splash
  screen again and continued to the desktop. I have another machine Asus
  Z77 with legacy boot and the same kernel update with no such issue.

  It should be noted that both NUC machines have been running since
  October last year with Ubuntu 18.10 without kernel issues up until
  now. As a result I have rolled back to Linux 5.3.0-24 and no such
  behavior is displayed.

  The NUCs involved are NUC7i7BNH and NUC5i7RYH.

  Thanks,
  Gerald Rozner

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gerald  915 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 10:08:41 2020
  InstallationDate: Installed on 2018-11-08 (426 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation NUC7i7BNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0e89ac23-8213-483e-9102-240ad3cfe107 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (78 days ago)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-310
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-311:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-310:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-311
  dmi.sys.vendor: Intel Corporation

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

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

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

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 1874374

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

Title:
  thinkbook 14-iil elan touchpad does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Here is the output of 
  cat /proc/bus/input/devices

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.0/0003:062A:4C01.0001/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input6
  U: Uniq=
  H: Handlers=mouse0 event6 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse Consumer Control"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=1f
  B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 
677bfad9415fed 19ed6804400 1002
  B: REL=1040
  B: ABS=1
  B: MSC=10

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse System Control"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=13
  B: KEY=c000 10 0
  B: MSC=10

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input10
  U: Uniq=
  H: Handlers=rfkill kbd event10 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-6/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input11
  U: Uniq=
  H: Handlers=kbd event11 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B:

[Kernel-packages] [Bug 1874374] Re: thinkbook 14-iil elan touchpad does not work

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

** No longer affects: linux-signed-hwe (Ubuntu)

** Tags added: hwe-touchpad

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

Title:
  thinkbook 14-iil elan touchpad does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Here is the output of 
  cat /proc/bus/input/devices

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.0/0003:062A:4C01.0001/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input6
  U: Uniq=
  H: Handlers=mouse0 event6 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse Consumer Control"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=1f
  B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 
677bfad9415fed 19ed6804400 1002
  B: REL=1040
  B: ABS=1
  B: MSC=10

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse System Control"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=13
  B: KEY=c000 10 0
  B: MSC=10

  I: Bus=0003 Vendor=062a Product=4c01 Version=0110
  N: Name="MOSART Semi. 2.4G Keyboard Mouse"
  P: Phys=usb-:00:14.0-4/input1
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input10
  U: Uniq=
  H: Handlers=rfkill kbd event10 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-6/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input11
  U: Uniq=
  H: Handlers=kbd event11 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
  U: Uniq=
  H:

[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

2020-04-24 Thread Dexuan Cui

Sorry, I made a typo above: systemd.dsystemd.default_standard_output=kmsg ==> 
systemd.default_standard_output=kmsg.
BTW, it looks systemd.show_status=true makes no difference for me. I don't see 
any status info during the boot-up time -- not sure if I did something wrong.

-- 
You 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   :

[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

2020-04-24 Thread Dexuan Cui

I don't have much knowledge bout systemd, either :-) I just did a "man
systemd" and found the options of systemd.  "man systemd" says that we
can use pass these kernel parameters to systemd:

systemd.service_watchdogs=true systemd.show_status=true
systemd.log_level=debug systemd.dsystemd.default_standard_output=kmsg
systemd.default_standard_error=kmsg

I tried these by adding them into /boot/grub/grub.cfg manually, at the end of 
the line "linux /boot/vmlinuz-5.3.0-23-generic ...". 
I also replaced "quiet splash $vt_handoff" with "ignore_loglevel". So I can get 
more messages from systemd, but not so much as I expected. Not sure if this 
would be helpful to troubleshoot the long delay issue for you, and I'm not even 
sure if I enabled the systemd loggong completely correctly -- again, I'm not 
really familiar with systemd. :-)

To stop/disble a systemd "service", I think we can use something like this 
(taking the setvtrgb.service as an example):
  systemctl stop  setvtrgb.service
  systemctl disable setvtrgb.service
  systemctl status setvtrgb.service

-- 
You 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

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

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 1874933

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

Title:
Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in linux package in Ubuntu:
Incomplete

Bug description:
As reported here:

https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to
5.4 kernel.
The 5.4 kernel added support for "Processor thermal device", for Ice Lake,
which will expose the power tables (via PPCC).

This system default "max RAPL long term power limit" is 15W. But this
power table is specifying as 9W. So thermald will limit power to 9W.

If dptfxtract is executed, then power limit will be higher than power
up value, but most of the users will use out of the box setup. So this
need a workaround.

This workaround will ignore any power limit less than the power up
power limit.

This is addressed in thermald 2.1 with two commits:

https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a

https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

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

[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake

2020-04-24 Thread Srinivas Pandruvada

** Description changed:

As reported here:

https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to
5.4 kernel.
- The 5.4 kernel added support for "Processor thermal device", for Ice Lake,
which will expose the power tables (vi PPCC).
+ The 5.4 kernel added support for "Processor thermal device", for Ice Lake,
which will expose the power tables (via PPCC).

- This system default max RAPL long term power limit is 15W. But this
+ This system default "max RAPL long term power limit" is 15W. But this
power table is specifying as 9W. So thermald will limit power to 9W.

If dptfxtract is executed, then power limit will be higher than power up
value, but most of the users will use out of the box setup. So this need
a workaround.

This workaround will ignore any power limit less than the power up power
limit.

This is addressed in thermald 2.1 with two commits:

https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a

https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

-
I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

Title:
Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in linux package in Ubuntu:
Incomplete

Bug description:
As reported here:

https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

This system default "max RAPL long term power limit" is 15W. But this
power table is specifying as 9W. So thermald will limit power to 9W.

If dptfxtract is executed, then power limit will be higher than power
up value, but most of the users will use out of the box setup. So this
need a workaround.

This workaround will ignore any power limit less than the power up
power limit.

This is addressed in thermald 2.1 with two commits:

https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a

https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

[Kernel-packages] [Bug 1874933] [NEW] Performance workaround for Dell 7390 2-in-1 Ice Lake

2020-04-24 Thread Srinivas Pandruvada

Public bug reported:

As reported here:
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4
kernel.
The 5.4 kernel added support for "Processor thermal device", for Ice Lake,
which will expose the power tables (via PPCC).

This system default "max RAPL long term power limit" is 15W. But this
power table is specifying as 9W. So thermald will limit power to 9W.

If dptfxtract is executed, then power limit will be higher than power up
value, but most of the users will use out of the box setup. So this need
a workaround.

This workaround will ignore any power limit less than the power up power
limit.

This is addressed in thermald 2.1 with two commits:
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

Title:
Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in linux package in Ubuntu:
New

Bug description:
As reported here:

https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

This system default "max RAPL long term power limit" is 15W. But this
power table is specifying as 9W. So thermald will limit power to 9W.

If dptfxtract is executed, then power limit will be higher than power
up value, but most of the users will use out of the box setup. So this
need a workaround.

This workaround will ignore any power limit less than the power up
power limit.

This is addressed in thermald 2.1 with two commits:

https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a

https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

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

[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

2020-04-24 Thread Dexuan Cui

Since Alt-SysRq-w gives nothing, I'm sure the long delay is not a
kernel/driver issue but a user space issue. It looks due to some reason
I just can not reproduce the long delay. :-(

In the Hyper-V Virtual Machine Connection window's "View" menu, there is
an item "Enhanced Session". In my Ubuntu 19.10 VM created by "Quick
Create...", the xrdp daemon/service is configured to automatically run
during the boot-up procedure; I think as soon as the xrdp daemon starts
to run, the "Enhanced Session" item becomes clickable/usable, and I can
click it to toggle between "Enhanced Session" mode (i.e. xrdp mode) and
the native Xorg GUI mode; when I'm in the xrdp mode, I click VM
Connection window's Action | Shut Down, then Start, and the VM will boot
up to the xrdp login screen in about 14 seconds; when I'm in the Xorg
mode, I click Shutdown then Start, the VM will boot up to the Xorg GUI
desktop in about 30 seconds. If I shut down the VM, close the VM
Connection window, and start the VM and open VM Connection window, I'll
be prompted by a small pop-up window to choose a resolution when (I
think) the xrdp daemon starts to run: 1) if I click the close icon of
the small window, I'll be in the Xorg GUI mode; if I accept the default
resolution (or change to a different resolution) and click "connect" in
the small window, I'll be in the xrdp mode. So all these work pretty
good for me.

Note: after I just created the 19.10 VM by "Quick Create..." and set up
the host name and user name/password stuff, I rebooted the VM and when
the VM booted up, I found the "Enhanced Session" was not
clickable/usable -- this looks like a bug -- while I still don't know
the root cause, it looks this can be resolved by manually adding the
line "initrd/boot/initrd.img-5.3.0-23-generic  #This line is
added by Dexuan manually" into "/boot/grub/grub.cfg":

menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-55829715-0091-4b86-b060-1cb88f342faf' {
...
if [ "${initrdfail}" = 1 ]; then
  linux /boot/vmlinuz-5.3.0-23-generic 
root=PARTUUID=43e99d31-1277-402c-a13b-6cc8fb93169b ro  quiet splash $vt_handoff
  initrd/boot/initrd.img-5.3.0-23-generic
else
  linux /boot/vmlinuz-5.3.0-23-generic 
root=PARTUUID=43e99d31-1277-402c-a13b-6cc8fb93169b ro  quiet splash $vt_handoff 
panic=-1
  initrd/boot/initrd.img-5.3.0-23-generic  #This line is added 
by Dexuan manually!!!
fi
initrdfail
}

With the addition of the line, it looks "GRUB_TIMEOUT=0" in "/etc/default/grub" 
is always really applied every time I reboot the VM.
Without the line, it looks sometimes the grub timeout is 30 second and 
sometimes it's 0 second.
BTW, I reported a bug for the missing initrd line a few weeks ago for a 
different issue: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189.

I suggest you also manually add the line, then I guess you should be
able to reliably toggle between xrdp mode and Xorg mode.

Note: "/boot/grub/grub.cfg" is overwritten when update-grub is run by us
or some automatic-update daemon, so we may want to check if the line is
still there when we see something unexpected (i.e. unable to use xrdp
mode, or see a grub timeout of 30s). I hope Bug 1870189 will be fixed by
somebody ASAP...

-- 
You 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

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

2020-04-24 Thread Srinivas Pandruvada

It is not really used in the relationship file. So other OS may not be
using this so probably never validated the critical trips. Better to
disable.

-- 
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 1870614] Re: Unable to boot ubuntu 19.10 or newer on dell xps 9570

2020-04-24 Thread Alistair Burrowes

20.04 does not work. I think this must now be a variant of
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1862751

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

Title:
  Unable to boot ubuntu 19.10 or newer on dell xps 9570

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous
  versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It
  fails with the following error quickly flashing:

error: file `/boot/` not found

  Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...
   
  This occurs when doing an update from 19.04 to 19.10 and also when just 
booting off a usb drive with 19.10.

  When booting off the usb drive. The first error flashes quickly before
  displaying the usb installer options. Selecting any install / boot
  option results in the second error about kernel buffer.

  I have tried all combinations of bios settings I can think of, such as
  toggling secure boot and other options. The only thing that made a
  difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This
  allows the installer to complete, but I cannot then boot off the hard
  drive.

  I have tried the same USB drive with 19.10 on a Dell XPS 7590 with
  BIOS 1.2.3 and the USB stick boots fine. I have also tried many
  different USB drives on my 9570.

  I have tried a few daily builds of 20.04 with the same result. I
  tested with 20.04 beta as well.

  Note: 19.04 and earlier continues to work no problem.

  I have asked for help previously:

  * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
  * https://answers.launchpad.net/ubuntu/+question/689546/+index

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.9
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 06:55:59 2020
  InstallationDate: Installed on 2019-10-24 (162 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bananan2456 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. XPS 15 9570
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-46-generic N/A
   linux-backports-modules-5.3.0-46-generic  N/A
   linux-firmware1.173.17
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 07GHH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1865071] [NEW] Power indicator doesn't show when charging (eoan)

You have been subscribed to a public bug:

On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt  
wrote:
No problem. I suggest the least confusing way for us to discuss that new
problem is to open a new bug by running:

  ubuntu-bug gnome-shell

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1845578


This is almost the same issue as my previous bug with disco, but I've noticed 
that if I'm plugged in before I boot, then the indicator knows it.  But not if 
I plug in while the computer is awake or suspended/hibernating.  If I plug in 
while it's suspended or hibernating, the indicator doesn't update.


jen@jenius:~$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
Uname: Linux 5.3.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 27 10:41:44 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-01-18 (39 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago)

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


** Tags: amd64 apport-bug eoan package-from-proposed
-- 
Power indicator doesn't show when charging (eoan)
https://bugs.launchpad.net/bugs/1865071
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

SRU submitted this morning [0], unfortunately we're not going to make
this cycle, the fix will need to wait for the next cycle.

Cheers,


Guilherme


[0] https://lists.ubuntu.com/archives/kernel-team/2020-April/109324.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/1869672

Title:
  Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

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

Bug description:
  [Impact]
  * Kdump kernel can't be loaded using Linux kernel 4.15.0-65 and newer on 
Bionic; kexec fails to load using the "new" kexec_file_load() syscall, showing 
the following messages in dmesg:

  kexec: Undefined symbol: __stack_chk_fail
  kexec-bzImage64: Loading purgatory failed

  * Reason for this was that backport from upstream commit b059f801a937
  ("x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS")
  makes use of a config option guard that wasn't backported to Ubuntu
  4.15.x series.

  * Also, we found another related issue, an undefined memcpy() symbol,
  that was related to the above patch too. We propose here a specific
  fix for Bionic, in the form of the patch attached in comment #18.

  [Test case]

  * Basically the test consists in booting a signed kernel in a secure
  boot environment (this is required given Ubuntu kernel is built with
  CONFIG_KEXEC_VERIFY_SIG so to use kexec_file_load() we must be in a
  proper signed/secure booted system). It works until 4.15.0-64, and
  starts to fail after this release, until the current proposed version
  4.15.0-97. We can also check kdump-tools service in the failing case,
  which shows:

  systemctl status kdump-tools
  [...]
  kdump-tools[895]: Starting kdump-tools: * Creating symlink 
/var/lib/kdump/vmlinuz
  kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img
  kdump-tools[895]: kexec_file_load failed: Exec format error
  kdump-tools[895]: * failed to load kdump kernel
  [...]

  * With the patch attached in the LP, it works normally again and I was
  able to collect a kdump.

  [Regression potential]

  * Given the patch is quite simple and fixes the build of purgatory, I
  think the regression potential is low. One potential regression in
  future would be on backports to purgatory Makefile, making them more
  difficult/prone to errors; given purgatory is a pretty untouchable
  code, I consider the regression potential here to be really low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1865071] Re: Power indicator doesn't show when charging (eoan)

2020-04-24 Thread Sebastien Bacher

The upower log has 
state:   discharging
likely a kernel issue rather than userspace one

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Power indicator doesn't show when charging (eoan)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt 
 wrote:
  No problem. I suggest the least confusing way for us to discuss that new
  problem is to open a new bug by running:

    ubuntu-bug gnome-shell

  -- 
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/1845578

  
  This is almost the same issue as my previous bug with disco, but I've noticed 
that if I'm plugged in before I boot, then the indicator knows it.  But not if 
I plug in while the computer is awake or suspended/hibernating.  If I plug in 
while it's suspended or hibernating, the indicator doesn't update.


  jen@jenius:~$ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 27 10:41:44 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-18 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago)

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

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

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

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 1865071

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

Title:
  Power indicator doesn't show when charging (eoan)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt 
 wrote:
  No problem. I suggest the least confusing way for us to discuss that new
  problem is to open a new bug by running:

    ubuntu-bug gnome-shell

  -- 
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/1845578

  
  This is almost the same issue as my previous bug with disco, but I've noticed 
that if I'm plugged in before I boot, then the indicator knows it.  But not if 
I plug in while the computer is awake or suspended/hibernating.  If I plug in 
while it's suspended or hibernating, the indicator doesn't update.


  jen@jenius:~$ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.3-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 27 10:41:44 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-18 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago)

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

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

[Kernel-packages] [Bug 1847832] Re: Backport ZoL pull request 9203 into the official packages.

2020-04-24 Thread Mathew Hodson

** Changed in: zfs-linux (Ubuntu Eoan)
   Importance: Undecided => High

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

Title:
  Backport ZoL pull request 9203 into the official packages.

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Eoan:
  Fix Released

Bug description:
  == SRU Justification, EOAN ==

  ZFS can deadlock, this can be sometimes triggered with a zfs rollback
  - "the zfs_resume_fs() code path may cause zfs to spawn new threads as
  it reinstantiates the suspended fs's zil. When a new thread is
  spawned, the kernel may attempt to free memory for that thread by
  freeing some unreferenced inodes. If it happens to select inodes that
  are a a part of the suspended fs a deadlock will occur because freeing
  inodes requires holding the fs's z_teardown_inactive_lock which is
  still held from the suspend."

  == The Fix ==

  Backport of ZFS upstream commit
  e7a2fa70c3b0d8c8cee2b484038bb5623c7c1ea9 ("Fix deadlock in 'zfs
  rollback'")

  The backport is relatively simple context wiggle.

  == Test Case ==

  This is hard to trigger so testing is non-trivial. To check for
  regressions we run the entire Ubuntu ZFS regression test suite.
  Without the fix rollbacks can very occasionally trip this issue. With
  the test, it's not possible.

  == Regression Potential ==

  The fix adds in an extra z_suspended flag to track suspended state and
  adds an extra reference to stop the kernel from free'ing inodes on a
  suspected file system.  The changes are small and are well-used in
  upstream ZFS so I believe if a regression was to have occurred it
  would have been found by the regression testing.

  - Original Bug Report Below ---

  Hopefully this is the correct bug tracker to report this on.

  Recently, I ran into a bug in ZFS as shipped in Ubuntu 19.10 that
  caused the kernel to deadlock and the system to eventually hang.

  I was advised by a ZFS on Linux project maintainer that this was a bug
  that was fixed in 0.8.2.

  The relevant pull request is here:
  https://github.com/zfsonlinux/zfs/pull/9203

  It would probably be a good idea to backport that pull request into
  19.10's build of ZFS.

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

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

2020-04-24 Thread bmaupin

I just upgraded to 20.04 and I can confirm that this bug affects the
default 5.4 kernel that it ships with.

-- 
You 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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire

@lordbaco Please install this kernel and see if it still crashes:
https://kernel.ubuntu.com/~sultan/i915-lp1870265/

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

Title:
  Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
  i915_active_acquire

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0 
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi 
snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal 
intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate 
intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152
  [ 2556.956409]

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

2020-04-24 Thread Brian Chen

@vicamo here is my bug report

https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1874374

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

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

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

Bug description:
  The Elan touchpad on my Lenovo Thinkbook isn't being detected, and
  hence isn't working.

  `sudo acpidump | grep -C3 ELAN` gives me the device's ACPI id:

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

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

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

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

** This bug has been marked a duplicate of bug 1868551
   Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) 
i915_active_acquire

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

  The syslog contains the following:

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

[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3

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

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

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

Title:
  Fix unusable USB hub on Dell TB16 after S3

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

Bug description:
  [Impact]
  Sometimes USB hub on Dell TB16 stop working after S3.

  [Fix]
  Attempt to power cycle USB device when a it's stuck at eSS.Disabled
  state, it's basically not recoverable.

  [Test]
  After applying the patch, USB ports and USB ethernet are still working
  after 100 times S3 stress test.

  Tested on other platforms and didn't observe any regression.
  However, I have never seen any other USB device stuck in eSS.Disabled state,
  so the code path wasn't executed at all.

  [Regression Potential]
  Low. This is a last resort attempt, in most cases this code path won't
  be reached.

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

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

[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3

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

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

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

Title:
  Fix unusable USB hub on Dell TB16 after S3

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

Bug description:
  [Impact]
  Sometimes USB hub on Dell TB16 stop working after S3.

  [Fix]
  Attempt to power cycle USB device when a it's stuck at eSS.Disabled
  state, it's basically not recoverable.

  [Test]
  After applying the patch, USB ports and USB ethernet are still working
  after 100 times S3 stress test.

  Tested on other platforms and didn't observe any regression.
  However, I have never seen any other USB device stuck in eSS.Disabled state,
  so the code path wasn't executed at all.

  [Regression Potential]
  Low. This is a last resort attempt, in most cases this code path won't
  be reached.

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

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

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

@leozinho29-eu Please install this kernel and see if it still crashes:
https://kernel.ubuntu.com/~sultan/i915-lp1870265/

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

  The syslog contains the following:

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

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

This bug is fixed by upstream commit
da42104f589d979bbe402703fd836cec60befae1:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da42104f589d979bbe402703fd836cec60befae1

It looks like that commit was *supposed* to be backported to 5.4 ("Cc:
 # v5.4+"), but the i915 maintainers didn't do
it, so we'll need to backport it ourselves.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

  The syslog contains the following:

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

I did the bisection and found that the bad kernels started at 5.3-rc1.
The last 5.2 kernel, 5.2.21, was good. I have attached the SystemD
analysis here of the boots of both kernels. You can see from it that the
problem in rc1 is related to the gpu-manager service.

I will attach the dmesg log of the rc1 boot in the next message.

** Attachment added: "SystemD critical chain and blame outputs: 5.3-rc1vs 
5.2.21 kernels"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359788/+files/SystemD5.2.21%265.3.rc1%20kernel%20bootup.odt

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

Here is the dmesg log for the bad boot of 5.3-rc1.

** Attachment added: "Log of 5.3-rc1 kernel boot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359789/+files/dmesg.0

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

I should add that I tested kernels 5.2.15, 5.2.18 and 5.2.20 as well.
All were OK, so the good-bad line is clearly after 5.2.21.

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

2020-04-24 Thread Kirt Runolfson

Confirmed that these errors do not appear in a fresh 20.04 release
installation.

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

Title:
  amdgpu kernel errors in Linux 5.4

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

Bug description:
  [Impact]

  amdgpu generates assert warning messages when retimer is not supported.
  This behaviour can cause confusions to users.

  [Fix]

  This is fixed by commit a0e40018dcc3f59a. It silences ASSERTs by
  outputing a debug message and exiting when retimer is not supported by
  hardware.

  [Test]

  Verified on B450 I AORUS PRO WIFI with AMD Ryzen 3 3200G as discussed
  on LP:1871248.

  [Regression Potential]

  Low. It is for unsupported hardware features, and the patch was cherry-picked
  from upstream kernel 5.7 rc1.

  ==

  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019

  These errors keep appearing in the kernel messages.
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]

  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/controlC1:  kirt   1293 F pulseaudio
   /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list:

[Kernel-packages] [Bug 1874713] Re: Instabilities when returning from idle mode and delay when detecting Intel bluetooth [8087:07da] peripherals

It seems that the cause is tlp. I made adjustments to the suggested line
(thanks You-Sheng Yang) and got some improvement in the detection time
of the mouse and keyboard (the keyboard is still slow but less worse). I
will monitor what happens when I return from idle mode.

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  Intel bluetooth [8087:07da] peripherals

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  etm2253 F pulseaudio
   /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: Sony Corporation SVS151290X
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS151290X
  dmi.product.sku: 54520726
  dmi.product.version: C60BKPK7
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1872583] Re: a fake headset key event will be triggered when plugging the headset on Lenovo x1c7

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => 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/1872583

Title:
  a fake headset key event will be triggered when plugging the headset
  on Lenovo x1c7

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  When users plug a headset into the audio jack on Lenovo x1c7, the
  audio driver can't stay in the rt_suspend state anymore

  [Fix]
  don't let the driver trigger the fake key event

  [Test Case]
  boot the kenrel, enable the dyndbg on the codec driver,
  plug/unplug the headset, check the runime pm status in the dmesg

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

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

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

[Kernel-packages] [Bug 1871688] Re: LIO hanging in iscsit_free_session and iscsit_stop_session

** No longer affects: linux (Ubuntu Xenial)

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

Title:
  LIO hanging in iscsit_free_session and iscsit_stop_session

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  The target subsystem (LIO) can hang if multiple threads try to destroy
  iSCSI sessions simultaneously. This is reproducible on systems that
  have multiple targets with initiators regularly
  connecting/disconnecting.

  This may happen when a "targetcli iscsi/iqn.../tpg1 disable" command
  is executed when a logout operation is underway.

  The iscsi target doesn't handle such events in a correct way: two or
  more threads may end up sleeping while waiting for the driver to close
  the remaining connections on the session. When the connections are
  closed, the driver wakes up only the first thread that will then
  proceed to destroy the session structure. The remaining threads are
  blocked there forever, waiting on a completion synchronization
  mechanism that doesn't exist in memory anymore because it has been
  freed by the first thread.

  Note that if the blocked threads are somehow forced to wake up, they
  will try to free the same iSCSI session structure destroyed by the
  first thread, causing double frees, memory corruptions, etc.

  The driver has been reorganized so the concurrent threads will set a
  flag in the session structure to notify the driver that the session
  should be destroyed; then, they wait for the driver to close the
  remaining connections. When the connections are all closed, the driver
  will wake up all the threads and will wait for the refcount of the
  iSCSI session structure to reach zero. When the last thread wakes up,
  the refcount is decreased to zero and the driver can proceed to
  destroy the session structure because no one is referencing it
  anymore.

  I've witnessed this happening on hundreds of Ubuntu 16.04.5 systems.
  It is a regression, because this did not occur several years ago.
  Unfortunately, I don't have detailed records from that far back to
  determine exactly which kernel I was running that was not affected by
  this bug (I believe it was either 4.8.x or 4.10.x).

  I've attached the requested uname, version_signature, dmesg, and lspci
  from my system. However, I've seen this happen on a wide array of
  hardware: 2 to 24 cores, 8GB to 256GB RAM, both AMD and Intel CPUs,
  onboard storage and PCIe SAS cards, etc.

  This has been fixed in the upstream master branch, but it hasn't yet
  been backported to "-stable".

  To fix this in the Ubuntu kernel, these three commits should be backported:
  * 
https://github.com/torvalds/linux/commit/e49a7d994379278d3353d7ffc7994672752fb0ad
  * 
https://github.com/torvalds/linux/commit/57c46e9f33da530a2485fa01aa27b6d18c28c796
  * 
https://github.com/torvalds/linux/commit/626bac73371eed79e2afa2966de393da96cf925e

  I'd like these commits to be added to the xenial, bionic, and focal
  kernels.

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

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

2020-04-24 Thread Egbert van der Wal

I've been running the 5.3.0-48-generic_5.3.0-48.41+lp1861395v1 for 2
days now. It definitely did get better but this afternoon I did get
another "Resetting rcs0 for hang on rcs0" so it doesn't seem to be
solved completely.


@kerneltoast: thanks for the suggestion, I did that. No more nouveau errors in 
dmesg and battery life has improved significantly. Awesome.

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

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

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

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

[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4

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

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

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

Title:
  amdgpu kernel errors in Linux 5.4

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

Bug description:
  [Impact]

  amdgpu generates assert warning messages when retimer is not supported.
  This behaviour can cause confusions to users.

  [Fix]

  This is fixed by commit a0e40018dcc3f59a. It silences ASSERTs by
  outputing a debug message and exiting when retimer is not supported by
  hardware.

  [Test]

  Verified on B450 I AORUS PRO WIFI with AMD Ryzen 3 3200G as discussed
  on LP:1871248.

  [Regression Potential]

  Low. It is for unsupported hardware features, and the patch was cherry-picked
  from upstream kernel 5.7 rc1.

  ==

  Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 20.04 beta fresh installation. Upgrades applied.
  AMD Ryzen 3 3200G with Radeon Vega Graphics
  Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS 
F50 11/27/2019

  These errors keep appearing in the kernel messages.
  [3.258890] [ cut here ]
  [3.258944] WARNING: CPU: 1 PID: 621 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 
write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]
  [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash 
algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi 
snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 
glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof 
ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd 
fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic 
ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables 
autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core 
i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic
  [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic 
#25-Ubuntu
  [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO 
WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019
  [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu]

  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/controlC1:  kirt   1293 F pulseaudio
   /dev/snd/controlC0:  kirt   1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 15:52:30 2020
  InstallationDate: Installed on 2020-04-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1806437]

2020-04-24 Thread kenny

It's benign; your BIOS has "duplicate WMI entries" within its ACPI
tables and the kernel is reporting that.

Ignore it, and/or complain to your device's manufacturer (... and good
luck with that).

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

Title:
  acpi PNP0C14:02: duplicate WMI GUID
  05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  PNP0C14:01)

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

Bug description:
  Hello,

  dmesg:
  [   15.390738] acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

  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   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 12:49:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 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 (0 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/1806437/+subscriptions

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

[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected

2020-04-24 Thread javi

I have found the solution for me finally!

My conflict was with my home assistant installation when alsa and
pulseaudio were conflicting with hassio_audio container.

For anyone with the same problem you can refer to: https://community
.home-assistant.io/t/audio-not-working-after-installing-hass-io-in-
docker/178858/3

Thank you very much to everyone!

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

Title:
  PCI/internal sound card not detected

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

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  In the -41 kernel, we introduced a patch from stable kernel, that
  make the sof driver crash, and there is a fix patch in the 5.6-rc1,
  and this fix patch is already in the stable and is merged to focal
  kernel, now we backport this patch to Eoan kernel if -42 doesn't
  introduce this fix patch from stable.

  The patch introduced the crash:
  commit 063821115e02229d5fd3de31bad270d5e30aeb41
  Author: Dragos Tarcatu 
  Date: Mon Dec 9 18:39:38 2019 -0600

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

  snd_soc_add_dai_link() might fail. This situation occurs for
  instance in a very specific use case where a PCM device and a
  Back End DAI link are given identical names in the topology.
  When this happens, soc_new_pcm_runtime() fails and then
  snd_soc_add_dai_link() returns -ENOMEM when called from
  soc_tplg_fe_link_create(). Because of that, the link will not
  get added into the card list, so any attempt to remove it later
  ends up in a panic.

  Fix that by checking the return status and free the memory in case
  of an error.

  Reviewed-by: Ranjani Sridharan 
  Signed-off-by: Dragos Tarcatu 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Khalid Elmously 

  
  [Impact]
  During the boot, the sof driver crash because the hdmi_pcm_list
  is not initialized before it is used.

  [Fix]
  This bug is fixed in the mainline kernel v5.6-rc1, now backport
  this patch to ubuntu kernel

  [Test Case]
  Boot the -41 kernel with this patch added.
  blacklist the snd_soc_skl
  the kernel can boot successfully, and sof driver worked well

  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  this patch on Lenovo and Dell dmic machines. Focal kernel already
  has this patch and works well.



  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion:

[Kernel-packages] [Bug 1806437]

2020-04-24 Thread kenny

https://lkml.org/lkml/2017/12/8/914

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

Title:
  acpi PNP0C14:02: duplicate WMI GUID
  05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  PNP0C14:01)

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

Bug description:
  Hello,

  dmesg:
  [   15.390738] acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)

  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   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 12:49:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 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 (0 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/1806437/+subscriptions

-- 
Mailing list: https://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 1872964] Re: Reliable crash in lowlatency kernel with LXD

2020-04-24 Thread Mark Shuttleworth

OK, will circle back to this bug in due course. From what you say it
might even be specific to that Nuc.

Mark

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

Title:
  Reliable crash in lowlatency kernel with LXD

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This
  machine in an Intel NUC, part of a three-member LXD cluster. The other
  machines do not show this crash and they are not running the
  lowlatency kernel, but that might be incidental. I will swap out the
  generic kernel for a while to see if the behaviour continues there.

  Here is the crash:

  [ 3222.385724] [ cut here ]
  [ 3222.385732] WARNING: CPU: 1 PID: 59852 at kernel/rcu/tree_plugin.h:293 
rcu_note_context_switch+0x46/0x460
  [ 3222.385733] Modules linked in: binfmt_misc veth nft_masq nft_chain_nat 
vxlan ip6_udp_tunnel udp_tunnel dummy bridge stp llc ebtable_filter ebtables 
ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables 
iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink unix_diag ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs pps_ldisc zfs(PO) zunicode(PO) zavl(PO) 
icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) dm_multipath zlua(PO) 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek 
snd_hda_codec_generic ledtrig_audio intel_rapl_msr snd_hda_intel mei_hdcp 
snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm kvm snd_timer 
intel_cstate mei_me intel_rapl_perf mei snd soundcore mac_hid acpi_pad 
sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor
  [ 3222.385779]  async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel i2c_algo_bit 
crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt 
e1000e i2c_i801 fb_sys_fops ahci drm libahci lpc_ich video
  [ 3222.385795] CPU: 1 PID: 59852 Comm: systemd-resolve Tainted: P   O 
 5.4.0-21-lowlatency #25-Ubuntu
  [ 3222.385796] Hardware name:  /NUC5i5MYBE, BIOS 
MYBDWi5v.86A.0034.2017.0116.2148 01/16/2017
  [ 3222.385801] RIP: 0010:rcu_note_context_switch+0x46/0x460
  [ 3222.385803] Code: 54 53 48 c7 c3 80 ba 02 00 65 48 03 1d 8b 57 ce 6d 0f 1f 
44 00 00 41 8b 85 80 07 00 00 45 84 f6 0f 85 55 02 00 00 85 c0 7e 0c <0f> 0b 41 
80 bd 84 07 00 00 00 74 33 4c 89 ef e8 36 fb ff ff 65 66
  [ 3222.385804] RSP: 0018:a7bf48e3bcf8 EFLAGS: 00010002
  [ 3222.385806] RAX: 0001 RBX: 9817c5caba80 RCX: 
0001
  [ 3222.385807] RDX:  RSI: 92ce6379 RDI: 

  [ 3222.385808] RBP: a7bf48e3bd20 R08:  R09: 

  [ 3222.385808] R10:  R11:  R12: 
9817c5caad00
  [ 3222.385809] R13: 9816c39ecd00 R14:  R15: 
0002ad00
  [ 3222.385811] FS:  7f9c0f530940() GS:9817c5c8() 
knlGS:
  [ 3222.385812] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3222.385812] CR2: 55988bb4b080 CR3: 0003b5e9a005 CR4: 
003606e0
  [ 3222.385813] DR0:  DR1:  DR2: 

  [ 3222.385814] DR3:  DR6: fffe0ff0 DR7: 
0400
  [ 3222.385815] Call Trace:
  [ 3222.385823]  __schedule+0x9d/0x750
  [ 3222.385826]  ? ___sys_sendmsg+0x95/0xd0
  [ 3222.385829]  schedule+0x49/0xd0
  [ 3222.385831]  schedule_hrtimeout_range_clock+0xf9/0x110
  [ 3222.385834]  ? __seccomp_filter+0x85/0x6b0
  [ 3222.385837]  schedule_hrtimeout_range+0x13/0x20
  [ 3222.385839]  ep_poll+0x3c8/0x410
  [ 3222.385843]  ? wake_up_q+0x70/0x70
  [ 3222.385845]  do_epoll_wait+0xb8/0xd0
  [ 3222.385847]  __x64_sys_epoll_wait+0x1e/0x30
  [ 3222.385850]  do_syscall_64+0x57/0x190
  [ 3222.385852]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 3222.385854] RIP: 0033:0x7f9c0f04eb77
  [ 3222.385856] Code: 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 
48 8d 05 91 ed 2c 00 41 89 ca 8b 00 85 c0 75 18 b8 e8 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 61 f3 c3 0f 1f 80 00 00 00 00 41 55 41 54 41
  [ 3222.385857] RSP: 002b:7ffc6fd86d88 EFLAGS: 0246 ORIG_RAX: 
00e8
  [ 3222.385859] RAX: ffda RBX: 55988d0ad3c0 RCX: 
7f9c0f04eb77
  [ 3222.385859] RDX: 000e RSI: 7ffc6fd86d90 RDI: 
0004
  [ 3222.385861] RBP: 7ffc6fd86f40 R08: 7ffc6fd86d90 R09: 
55988d0b645c
  [ 3222.385861] R10:  R11: 0246 R12: 
00cf
  [ 3222.385862] R13:  R14: 7ffc6fd86d90 R15:

[Kernel-packages] [Bug 1873292] Re: Focal update: v5.4.32 upstream stable release

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

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

Title:
  Focal update: v5.4.32 upstream stable release

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

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

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

  net: phy: realtek: fix handling of RTL8105e-integrated PHY
  cxgb4: fix MPS index overwrite when setting MAC address
  ipv6: don't auto-add link-local address to lag ports
  net: dsa: bcm_sf2: Do not register slave MDIO bus with OF
  net: dsa: bcm_sf2: Ensure correct sub-node is parsed
  net: dsa: mt7530: fix null pointer dereferencing in port5 setup
  net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before 
accessing PHY registers
  net_sched: add a temporary refcnt for struct tcindex_data
  net_sched: fix a missing refcnt in tcindex_init()
  net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
  tun: Don't put_page() for all negative return values from XDP program
  mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
  r8169: change back SG and TSO to be disabled by default
  s390: prevent leaking kernel address in BEAR
  random: always use batched entropy for get_random_u{32,64}
  usb: dwc3: gadget: Wrap around when skip TRBs
  uapi: rename ext2_swab() to swab() and share globally in swab.h
  slub: improve bit diffusion for freelist ptr obfuscation
  tools/accounting/getdelays.c: fix netlink attribute length
  hwrng: imx-rngc - fix an error path
  ACPI: PM: Add acpi_[un]register_wakeup_handler()
  platform/x86: intel_int0002_vgpio: Use acpi_register_wakeup_handler()
  ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
  IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
  IB/hfi1: Fix memory leaks in sysfs registration and unregistration
  IB/mlx5: Replace tunnel mpls capability bits for tunnel_offloads
  ARM: imx: Enable ARM_ERRATA_814220 for i.MX6UL and i.MX7D
  ARM: imx: only select ARM_ERRATA_814220 for ARMv7-A
  ceph: remove the extra slashes in the server path
  ceph: canonicalize server path in place
  include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for 
swap
  RDMA/ucma: Put a lock around every call to the rdma_cm layer
  RDMA/cma: Teach lockdep about the order of rtnl and lock
  RDMA/siw: Fix passive connection establishment
  Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
  RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
  blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync
  fbcon: fix null-ptr-deref in fbcon_switch
  iommu/vt-d: Allow devices with RMRRs to use identity domain
  Linux 5.4.32
  UBUNTU: upstream stable to v5.4.32

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

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

[Kernel-packages] [Bug 1872757] Re: shiftfs: O_TMPFILE reports ESTALE

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

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

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

Title:
  shiftfs: O_TMPFILE reports ESTALE

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Christian Kellner reported that creating temporary files via
  O_TMPFILE shiftfs reports ESTALE. This can be reproduced via:

  import tempfile
  import os

  def test():
  with tempfile.TemporaryFile() as fd:
  fd.write("data".encode('utf-8'))
  # re-open the file to get a read-only file descriptor
  return open(f"/proc/self/fd/{fd.fileno()}", "r")

  def main():
     fd = test()
     fd.close()

  if __name__ == "__main__":
  main()

  a similar issue was reported here:
  https://github.com/systemd/systemd/issues/14861

  Fix: Our revalidate methods were very opinionated about whether or not
  a dentry was valid when we really should've just let the underlay tell
  us what's what. This has led to bugs where a ESTALE was returned for
  e.g.  temporary files that were created and directly re-opened
  afterwards through /proc//fd/. When a file is
  re-opened through /proc//fd/ LOOKUP_JUMP is set and the vfs
  will revalidate via d_weak_revalidate(). Since the file has been
  unhashed or even already gone negative we'd fail the open when we
  should've succeeded.

  I had also foolishly provided a .tmpfile method which so far only has
  caused us trouble. If we really need this then we can reimplement it
  properly but I doubt it. Remove it for now.

  Regression Potential: Limited to shiftfs.

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

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

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

[Kernel-packages] [Bug 1873481] Re: Focal update: v5.4.33 upstream stable release

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

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

Title:
  Focal update: v5.4.33 upstream stable release

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

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

     v5.4.33 upstream stable release
     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
  ARM: dts: Fix dm814x Ethernet by changing to use rgmii-id mode
  bpf: Fix deadlock with rq_lock in bpf_send_signal()
  iwlwifi: mvm: Fix rate scale NSS configuration
  Input: tm2-touchkey - add support for Coreriver TC360 variant
  soc: fsl: dpio: register dpio irq handlers after dpio create
  rxrpc: Abstract out the calculation of whether there's Tx space
  rxrpc: Fix call interruptibility handling
  net: stmmac: platform: Fix misleading interrupt error msg
  net: vxge: fix wrong __VA_ARGS__ usage
  hinic: fix a bug of waitting for IO stopped
  hinic: fix the bug of clearing event queue
  hinic: fix out-of-order excution in arm cpu
  hinic: fix wrong para of wait_for_completion_timeout
  hinic: fix wrong value of MIN_SKB_LEN
  selftests/net: add definition for SOL_DCCP to fix compilation errors for old 
libc
  cxgb4/ptp: pass the sign of offset delta in FW CMD
  drm/scheduler: fix rare NULL ptr race
  cfg80211: Do not warn on same channel at the end of CSA
  qlcnic: Fix bad kzalloc null test
  i2c: st: fix missing struct parameter description
  i2c: pca-platform: Use platform_irq_get_optional
  media: rc: add keymap for Videostrong KII Pro
  cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL
  staging: wilc1000: avoid double unlocking of 'wilc->hif_cs' mutex
  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
  media: imx: imx7_mipi_csis: Power off the source when stopping streaming
  media: imx: imx7-media-csi: Fix video field handling
  xhci: bail out early if driver can't accress host in resume
  ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()
  x86: Don't let pgprot_modify() change the page encryption bit
  dma-mapping: Fix dma_pgprot() for unencrypted coherent pages
  block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
  debugfs: Check module state before warning in {full/open}_proxy_open()
  irqchip/versatile-fpga: Handle chained IRQs properly
  time/sched_clock: Expire timer in hardirq context
  media: allegro: fix type of gop_length in channel_create message
  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()
  block, bfq: move forward the getting of an extra ref in bfq_bfqq_move
  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: Do log_flush in gfs2_ail_empty_gl even if ail list is empty
  gfs2: Don't demote a glock until its revokes are written
  cpufreq: imx6q: fix error handling
  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
  spi: spi-fsl-dspi: Replace interruptible wait queue with a simple completion
  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: restart relocate_tree_blocks properly
  btrfs: track reloc

[Kernel-packages] [Bug 1871651] Re: Focal update: v5.4.31 upstream stable release

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

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

Title:
  Focal update: v5.4.31 upstream stable release

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

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

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

  nvme-rdma: Avoid double freeing of async event data
  kconfig: introduce m32-flag and m64-flag
  drm/amd/display: Add link_rate quirk for Apple 15" MBP 2017
  drm/bochs: downgrade pci_request_region failure from error to warning
  initramfs: restore default compression behavior
  drm/amdgpu: fix typo for vcn1 idle check
  tools/power turbostat: Fix gcc build warnings
  tools/power turbostat: Fix missing SYS_LPI counter on some Chromebooks
  tools/power turbostat: Fix 32-bit capabilities warning
  net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow
  XArray: Fix xa_find_next for large multi-index entries
  padata: fix uninitialized return value in padata_replace()
  brcmfmac: abort and release host after error
  misc: rtsx: set correct pcr_ops for rts522A
  misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
  misc: pci_endpoint_test: Avoid using module parameter to determine irqtype
  PCI: sysfs: Revert "rescan" file renames
  coresight: do not use the BIT() macro in the UAPI header
  mei: me: add cedar fork device ids
  nvmem: check for NULL reg_read and reg_write before dereferencing
  extcon: axp288: Add wakeup support
  power: supply: axp288_charger: Add special handling for HP Pavilion x2 10
  Revert "dm: always call blk_queue_split() in dm_process_bio()"
  ALSA: hda/ca0132 - Add Recon3Di quirk to handle integrated sound on EVGA X99 
Classified motherboard
  soc: mediatek: knows_txdone needs to be set in Mediatek CMDQ helper
  net/mlx5e: kTLS, Fix wrong value in record tracker enum
  iwlwifi: consider HE capability when setting LDPC
  iwlwifi: yoyo: don't add TLV offset when reading FIFOs
  iwlwifi: dbg: don't abort if sending DBGC_SUSPEND_RESUME fails
  rxrpc: Fix sendmsg(MSG_WAITALL) handling
  IB/hfi1: Ensure pq is not left on waitlist
  tcp: fix TFO SYNACK undo to avoid double-timestamp-undo
  watchdog: iTCO_wdt: Export vendorsupport
  watchdog: iTCO_wdt: Make ICH_RES_IO_SMI optional
  i2c: i801: Do not add ICH_RES_IO_SMI for the iTCO_wdt device
  net: Fix Tx hash bound checking
  padata: always acquire cpu_hotplug_lock before pinst->lock
  mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
  Linux 5.4.31
  UBUNTU: upstream stable to v5.4.31

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

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

[Kernel-packages] [Bug 1874111] Re: Focal update: v5.4.34 upstream stable release

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

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

Title:
  Focal update: v5.4.34 upstream stable release

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

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

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

  amd-xgbe: Use __napi_schedule() in BH context
  hsr: check protocol version in hsr_newlink()
  l2tp: Allow management of tunnels and session in user namespace
  net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode
  net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin
  net: ipv6: do not consider routes via gateways for anycast address check
  net: phy: micrel: use genphy_read_status for KSZ9131
  net: qrtr: send msgs from local of same id as broadcast
  net: revert default NAPI poll timeout to 2 jiffies
  net: tun: record RX queue in skb before do_xdp_generic()
  net: dsa: mt7530: move mt7623 settings out off the mt7530
  net: ethernet: mediatek: move mt7623 settings out off the mt7530
  net/mlx5: Fix frequent ioread PCI access during recovery
  net/mlx5e: Add missing release firmware call
  net/mlx5e: Fix nest_level for vlan pop action
  net/mlx5e: Fix pfnum in devlink port attribute
  net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes
  ovl: fix value of i_ino for lower hardlink corner case
  scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic
  platform/chrome: cros_ec_rpmsg: Fix race with host event
  jbd2: improve comments about freeing data buffers whose page mapping is NULL
  acpi/nfit: improve bounds checking for 'func'
  perf report: Fix no branch type statistics report issue
  pwm: pca9685: Fix PWM/GPIO inter-operation
  ext4: fix incorrect group count in ext4_fill_super error message
  ext4: fix incorrect inodes per group in error message
  clk: at91: sam9x60: fix usb clock parents
  clk: at91: usb: use proper usbs_mask
  ARM: dts: imx7-colibri: fix muxing of usbc_det pin
  arm64: dts: librem5-devkit: add a vbus supply to usb0
  usb: dwc3: gadget: Don't clear flags before transfer ended
  ASoC: Intel: mrfld: fix incorrect check on p->sink
  ASoC: Intel: mrfld: return error codes when an error occurs
  ALSA: hda/realtek - Enable the headset mic on Asus FX505DT
  ALSA: usb-audio: Filter error from connector kctl ops, too
  ALSA: usb-audio: Don't override ignore_ctl_error value from the map
  ALSA: usb-audio: Don't create jack controls for PCM terminals
  ALSA: usb-audio: Check mapping at creating connector controls, too
  arm64: vdso: don't free unallocated pages
  keys: Fix proc_keys_next to increase position index
  tracing: Fix the race between registering 'snapshot' event trigger and 
triggering 'snapshot' operation
  btrfs: check commit root generation in should_ignore_root
  nl80211: fix NL80211_ATTR_FTM_RESPONDER policy
  mac80211: fix race in ieee80211_register_hw()
  mac80211_hwsim: Use kstrndup() in place of kasprintf()
  net/mlx5e: Encapsulate updating netdev queues into a function
  net/mlx5e: Rename hw_modify to preactivate
  net/mlx5e: Use preactivate hook to set the indirection table
  drm/amd/powerplay: force the trim of the mclk dpm_levels if OD is enabled
  drm/amdgpu: fix the hw hang during perform system reboot and reset
  i2c: designware: platdrv: Remove DPM_FLAG_SMART_SUSPEND flag on BYT and CHT
  ext4: do not zeroout extents beyond i_disksize
  irqchip/ti-sci-inta: Fix processing of masked irqs
  x86/resctrl: Preserve CDP enable over CPU hotplug
  x86/resctrl: Fix invalid attempt at removing the default resource group
  scsi: target: remove boilerplate code
  scsi: target: fix hang when multiple threads try to destroy the same iscsi 
session
  x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE
  Linux 5.4.34
  UBUNTU: upstream stable to v5.4.34

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

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

[Kernel-packages] [Bug 1871284] Re: alsa: make the dmic detection align to the mainline kernel-5.6

** Changed in: linux-oem-5.6 (Ubuntu Eoan)
   Status: Invalid => 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/1871284

Title:
  alsa: make the dmic detection align to the mainline kernel-5.6

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux source package in Eoan:
  Incomplete
Status in linux-oem-5.6 source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  This patchset is already in the upstream kernel-5.6, so no need to
  send for unstable.
  And this patchset will remove an existing kernel module and add a new
  kernel module, so need to change the ABI/modules.ignore manually.
  The module removed: snd-intel-nhlt.ko
  The module added:   snd-intel-dspcfg.ko

  [Impact]
  There is already dmic detection code in the eoan and focal kernel, it
  works well on CNL/WHL and later Intel platforms, but it doesn't work
  on KBL, SKL and old Intel machines.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/comments/14

  [Fix]
  The upstream kernel updated the dmic detection code, it will exclude the
  old intel machines by default. Then the old machines will use legacy hda
  driver like before.

  [Test Case]
  Install the testing kernel to Dell/LENOVO WHL/CNL and later machines,
  they work as well as before.

  And a user verifed the testing kernel work on his KBL machine.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/comments/17

  [Regression Risk]
  Low, those patches come from mainline kernel, I have tested those patches
  on the WHL/CNL and later machiens, a user tested it on a KBL machine.

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

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

[Kernel-packages] [Bug 1872533] Re: Eoan update: upstream stable patchset 2020-04-13

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

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

Title:
  Eoan update: upstream stable patchset 2020-04-13

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-04-13

  Ported from the following upstream stable releases:
  v4.19.115, v5.4.31,
     v5.4.32

     from git://git.kernel.org/

  ipv4: fix a RCU-list lock in fib_triestat_seq_show
  net, ip_tunnel: fix interface lookup with no key
  sctp: fix refcount bug in sctp_wfree
  sctp: fix possibly using a bad saddr with a given dst
  nvme-rdma: Avoid double freeing of async event data
  drm/amd/display: Add link_rate quirk for Apple 15" MBP 2017
  drm/bochs: downgrade pci_request_region failure from error to warning
  initramfs: restore default compression behavior
  drm/amdgpu: fix typo for vcn1 idle check
  tools/power turbostat: Fix gcc build warnings
  tools/power turbostat: Fix missing SYS_LPI counter on some Chromebooks
  drm/etnaviv: replace MMU flush marker with flush sequence
  misc: rtsx: set correct pcr_ops for rts522A
  misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
  misc: pci_endpoint_test: Avoid using module parameter to determine irqtype
  coresight: do not use the BIT() macro in the UAPI header
  mei: me: add cedar fork device ids
  extcon: axp288: Add wakeup support
  power: supply: axp288_charger: Add special handling for HP Pavilion x2 10
  ALSA: hda/ca0132 - Add Recon3Di quirk to handle integrated sound on EVGA X99 
Classified motherboard
  rxrpc: Fix sendmsg(MSG_WAITALL) handling
  net: Fix Tx hash bound checking
  padata: always acquire cpu_hotplug_lock before pinst->lock
  mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
  ipv6: don't auto-add link-local address to lag ports
  net: dsa: bcm_sf2: Do not register slave MDIO bus with OF
  net: dsa: bcm_sf2: Ensure correct sub-node is parsed
  net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before 
accessing PHY registers
  net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
  slcan: Don't transmit uninitialized stack data in padding
  mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
  random: always use batched entropy for get_random_u{32,64}
  usb: dwc3: gadget: Wrap around when skip TRBs
  tools/accounting/getdelays.c: fix netlink attribute length
  hwrng: imx-rngc - fix an error path
  ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
  IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
  IB/hfi1: Fix memory leaks in sysfs registration and unregistration
  ceph: remove the extra slashes in the server path
  ceph: canonicalize server path in place
  RDMA/ucma: Put a lock around every call to the rdma_cm layer
  RDMA/cma: Teach lockdep about the order of rtnl and lock
  Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
  RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
  fbcon: fix null-ptr-deref in fbcon_switch
  clk: qcom: rcg: Return failure for RCG update
  usb: dwc3: don't set gadget->is_otg flag
  kconfig: introduce m32-flag and m64-flag
  UBUNTU: [Packaging] add libcap-dev dependency
  tools/power turbostat: Fix 32-bit capabilities warning
  XArray: Fix xa_find_next for large multi-index entries
  brcmfmac: abort and release host after error
  nvmem: check for NULL reg_read and reg_write before dereferencing
  Revert "dm: always call blk_queue_split() in dm_process_bio()"
  soc: mediatek: knows_txdone needs to be set in Mediatek CMDQ helper
  net/mlx5e: kTLS, Fix wrong value in record tracker enum
  iwlwifi: consider HE capability when setting LDPC
  iwlwifi: yoyo: don't add TLV offset when reading FIFOs
  IB/hfi1: Ensure pq is not left on waitlist
  tcp: fix TFO SYNACK undo to avoid double-timestamp-undo
  watchdog: iTCO_wdt: Export vendorsupport
  watchdog: iTCO_wdt: Make ICH_RES_IO_SMI optional
  net: phy: realtek: fix handling of RTL8105e-integrated PHY
  cxgb4: fix MPS index overwrite when setting MAC address
  net_sched: add a temporary refcnt for struct tcindex_data
  net_sched: fix a missing refcnt in tcindex_init()
  tun: Don't put_page() for all negative return values from XDP program
  s390: prevent leaking

[Kernel-packages] [Bug 1872569] Re: alsa/sof: external mic can't be deteced on Lenovo and HP laptops

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

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => 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/1872569

Title:
  alsa/sof: external mic can't be deteced on Lenovo and HP laptops

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

Bug description:
  [Impact]
  When users plug a headset into the audio jack, the driver
  can't detect the mic, only can detect the headhpone. If users open the
  gnome-sound-setting, the mic could be detected.

  [Fix]
  Need to set auto_suspend_delay to the codec driver

  [Test Case]
  boot the kenrel, plug/unplug the headset, run amixer contents
  to check the "Jack Mic" state

  [Regression Risk]
  Low, this patch comes from intel sof kernel, I have tested this patch
  on HP and Lenovo machine, they all worked well.

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

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

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

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

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

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

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:

[Kernel-packages] [Bug 1873537] Re: PCIe AER device recovery failed due to logic flaw

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

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

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

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

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

Title:
  PCIe AER device recovery failed due to logic flaw

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

Bug description:
  SRU Justification

  Impact:

  During PCI Express Downstream Port Containment (DPC) recovery,
  certain types of failures do not recover due to a logic flaw
  in pcie_do_recovery().

  The upstream git commit log explains the change:

  PCI/ERR: Update error status after reset_link()
  Commit bdb5ac85777d ("PCI/ERR: Handle fatal error recovery") uses
  reset_link() to recover from fatal errors.  But during fatal error
  recovery, if the initial value of error status is PCI_ERS_RESULT_DISCONNECT
  or PCI_ERS_RESULT_NO_AER_DRIVER then even after successful recovery (using
  reset_link()) pcie_do_recovery() will report the recovery result as
  failure.  Update the status of error after reset_link().

  You can reproduce this issue by triggering a SW DPC using "DPC Software
  Trigger" bit in "DPC Control Register".  You should see recovery failed
  dmesg log as below:

pcieport :00:16.0: DPC: containment event, status:0x1f27 source:0x
pcieport :00:16.0: DPC: software trigger detected
pci :04:00.0: AER: can't recover (no error_detected callback)
pcieport :00:16.0: AER: device recovery failed

  Fixes: bdb5ac85777d ("PCI/ERR: Handle fatal error recovery")
  Link: 
https://lore.kernel.org/r/a255fcb3a3fdebcd90f84e08b555f1786eb8eba2.158584.git.sathyanarayanan.kuppusw...@linux.intel.com
  [bhelgaas: split pci_channel_io_frozen simplification to separate patch]
  Signed-off-by: Kuppuswamy Sathyanarayanan 

  Signed-off-by: Bjorn Helgaas 
  Acked-by: Keith Busch 
  Cc: Ashok Raj 

  Note that a second prerequisite patch is necessary as well.  This
  patch,

  commit b5dfbeacf74865a8d62a4f70f501cdc61510f8e0
  Author: Kuppuswamy Sathyanarayanan 

  Date:   Fri Mar 27 17:33:24 2020 -0500

  PCI/ERR: Combine pci_channel_io_frozen cases

  is a code readability change, and makes no functional changes.

  
  Testcase:

  On a system with DPC enabled, setpci may be used to set the DPC Software
  Trigger bit (bit 6, value 0x40) in the DPC Control register of a suitable
  PCIe device (a PCIe bridge, for example).

  On a system lacking the fix, the output will be as shown above (i.e.,
  culminating in the "device recovery failed" message).  With the fix
  applied, the device successfully recovers, resulting in a message of the
  form

  pcieport :d9:01.0: AER: Device recovery successful

  
  Regression Potential:

  The risk of regression is low, as (a) the path in question currently does
  not work, and (b) the changes are minimal, comprising only a housekeeping
  change and the logically correct updating of a status variable that did
  not previously occur.

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

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

[Kernel-packages] [Bug 1872500] Re: Disco update: upstream stable patchset 2020-04-13

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

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

Title:
  Disco update: upstream stable patchset 2020-04-13

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-04-13

  Ported from the following upstream stable releases:
  v4.19.115, v5.4.31,
 v5.4.32

     from git://git.kernel.org/

  ipv4: fix a RCU-list lock in fib_triestat_seq_show
  net, ip_tunnel: fix interface lookup with no key
  sctp: fix refcount bug in sctp_wfree
  sctp: fix possibly using a bad saddr with a given dst
  nvme-rdma: Avoid double freeing of async event data
  drm/amd/display: Add link_rate quirk for Apple 15" MBP 2017
  drm/bochs: downgrade pci_request_region failure from error to warning
  initramfs: restore default compression behavior
  drm/amdgpu: fix typo for vcn1 idle check
  tools/power turbostat: Fix gcc build warnings
  tools/power turbostat: Fix missing SYS_LPI counter on some Chromebooks
  drm/etnaviv: replace MMU flush marker with flush sequence
  media: rc: IR signal for Panasonic air conditioner too long
  misc: rtsx: set correct pcr_ops for rts522A
  misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
  misc: pci_endpoint_test: Avoid using module parameter to determine irqtype
  coresight: do not use the BIT() macro in the UAPI header
  mei: me: add cedar fork device ids
  extcon: axp288: Add wakeup support
  power: supply: axp288_charger: Add special handling for HP Pavilion x2 10
  ALSA: hda/ca0132 - Add Recon3Di quirk to handle integrated sound on EVGA X99 
Classified motherboard
  rxrpc: Fix sendmsg(MSG_WAITALL) handling
  net: Fix Tx hash bound checking
  padata: always acquire cpu_hotplug_lock before pinst->lock
  mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
  ipv6: don't auto-add link-local address to lag ports
  net: dsa: bcm_sf2: Do not register slave MDIO bus with OF
  net: dsa: bcm_sf2: Ensure correct sub-node is parsed
  net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before 
accessing PHY registers
  net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
  slcan: Don't transmit uninitialized stack data in padding
  mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
  random: always use batched entropy for get_random_u{32,64}
  usb: dwc3: gadget: Wrap around when skip TRBs
  tools/accounting/getdelays.c: fix netlink attribute length
  hwrng: imx-rngc - fix an error path
  ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
  IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
  IB/hfi1: Fix memory leaks in sysfs registration and unregistration
  ceph: remove the extra slashes in the server path
  ceph: canonicalize server path in place
  RDMA/ucma: Put a lock around every call to the rdma_cm layer
  RDMA/cma: Teach lockdep about the order of rtnl and lock
  Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
  RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
  fbcon: fix null-ptr-deref in fbcon_switch
  clk: qcom: rcg: Return failure for RCG update
  drm/msm: stop abusing dma_map/unmap for cache
  arm64: Fix size of __early_cpu_boot_status
  usb: dwc3: don't set gadget->is_otg flag
  drm/msm: Use the correct dma_sync calls in msm_gem
  kconfig: introduce m32-flag and m64-flag
  UBUNTU: [Packaging] add libcap-dev dependency
  tools/power turbostat: Fix 32-bit capabilities warning
  XArray: Fix xa_find_next for large multi-index entries
  brcmfmac: abort and release host after error
  soc: mediatek: knows_txdone needs to be set in Mediatek CMDQ helper
  IB/hfi1: Ensure pq is not left on waitlist
  watchdog: iTCO_wdt: Export vendorsupport
  watchdog: iTCO_wdt: Make ICH_RES_IO_SMI optional
  net: phy: realtek: fix handling of RTL8105e-integrated PHY
  cxgb4: fix MPS index overwrite when setting MAC address
  net_sched: add a temporary refcnt for struct tcindex_data
  net_sched: fix a missing refcnt in tcindex_init()
  tun: Don't put_page() for all negative return values from XDP program
  uapi: rename ext2_swab() to swab() and share globally in swab.h
  slub: improve bit diffusion for freelist ptr obfuscation
  ARM: imx: Enable ARM_ERRATA_814220 for i.MX6UL and i.MX7D
  ARM: imx: only select ARM_ERRATA_814220

[Kernel-packages] [Bug 1874005] Re: QEMU pegs CPU at 100% when running a Focal guest image

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

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

Title:
  QEMU pegs CPU at 100% when running a Focal guest image

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  Running a VM with a guest kernel >=5.2 results in the QEMU process
  pegging the CPU at 100%. Sometimes it recovers but most of the times
  the QEMU process just hangs, libvirt times out trying to talk to it
  and it can't be killed.

  [Test Case]

  Spin up a libvirt VM that runs a kernel >=5.2. Sometimes it takes a
  couple of VM reboots but the QEMU process will eventually hang with
  100% CPU utilization.

  [Fix]

  Cherry pick commit 53a712bae5dd ("powerpc/powernv/idle: Restore
  AMR/UAMOR/AMOR after idle").

  [Regression Potential]

  Moderate. The commit is in 5.2 and is a clean cherry-pick but it's
  POWER assembly voodoo.

  [Original Description]

  Running a Focal guest image with a 5.4 kernel on a POWER9 Bionic host
  with kernel 4.15 leads to the QEMU process pegging the CPU at 100%.

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

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

[Kernel-packages] [Bug 1874221] Re: Fix potential null pointer dereference on kernfs

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => 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/1874221

Title:
  Fix potential null pointer dereference on kernfs

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  We are seeing a null kernel dereference on kernfs during system sleep
  stress.

  [Fix]
  Make sure kernfs root is not null.

  [Test]
  Run sleep stress. Not seeing the issue after the fix is applied.

  [Regression Potential]
  Low. Fix limits to kernfs, also the it has been in upstream kernel for
  quite a while.

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

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

[Kernel-packages] [Bug 1872380] Re: alsa/sof: headphone can't be detected when sof driver enters rt_suspend

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => 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/1872380

Title:
  alsa/sof: headphone can't be detected when sof driver enters
  rt_suspend

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  This patchset is already in the linux-oem-osp1 and focal, so only eoan
  kernel needs this patchset

  
  [Impact]
  When users plug a headset/headphone into the audio jack, the driver
  can't detect them, if users open the gnome-sound-setting, then the
  driver could detect them.

  [Fix]
  Before driver enters runtime_suspend, need to set the WAKEEN, then
  the plug/unplugging will trigger unsol event to the driver.

  [Test Case]
  boot the kenrel, plug/unplug the headset/headphone, run amixer contents
  to check the "Jack Headpone" state

  [Regression Risk]
  Low, those patches come from mainline kernel, I have tested those patches
  on Dell and Lenovo machines, they all worked well.

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

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

[Kernel-packages] [Bug 1873954] Re: Disco update: upstream stable patchset 2020-04-20

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

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

Title:
  Disco update: upstream stable patchset 2020-04-20

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-04-20

  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
  ARM: dts: Fix dm814x Ethernet by changing to use rgmii-id mode
  bpf: Fix deadlock with rq_lock in bpf_send_signal()
  iwlwifi: mvm: Fix rate scale NSS configuration
  Input: tm2-touchkey - add support for Coreriver TC360 variant
  soc: fsl: dpio: register dpio irq handlers after dpio create
  rxrpc: Abstract out the calculation of whether there's Tx space
  rxrpc: Fix call interruptibility handling
  net: stmmac: platform: Fix misleading interrupt error msg
  net: vxge: fix wrong __VA_ARGS__ usage
  hinic: fix a bug of waitting for IO stopped
  hinic: fix the bug of clearing event queue
  hinic: fix out-of-order excution in arm cpu
  hinic: fix wrong para of wait_for_completion_timeout
  hinic: fix wrong value of MIN_SKB_LEN
  selftests/net: add definition for SOL_DCCP to fix compilation errors for old 
libc
  cxgb4/ptp: pass the sign of offset delta in FW CMD
  drm/scheduler: fix rare NULL ptr race
  cfg80211: Do not warn on same channel at the end of CSA
  qlcnic: Fix bad kzalloc null test
  i2c: st: fix missing struct parameter description
  i2c: pca-platform: Use platform_irq_get_optional
  media: rc: add keymap for Videostrong KII Pro
  cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL
  staging: wilc1000: avoid double unlocking of 'wilc->hif_cs' mutex
  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
  media: imx: imx7_mipi_csis: Power off the source when stopping streaming
  media: imx: imx7-media-csi: Fix video field handling
  xhci: bail out early if driver can't accress host in resume
  ACPI: EC: Do not clear boot_ec_is_ecdt in acpi_ec_add()
  x86: Don't let pgprot_modify() change the page encryption bit
  dma-mapping: Fix dma_pgprot() for unencrypted coherent pages
  block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
  debugfs: Check module state before warning in {full/open}_proxy_open()
  irqchip/versatile-fpga: Handle chained IRQs properly
  time/sched_clock: Expire timer in hardirq context
  media: allegro: fix type of gop_length in channel_create message
  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()
  block, bfq: move forward the getting of an extra ref in bfq_bfqq_move
  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: Do log_flush in gfs2_ail_empty_gl even if ail list is empty
  gfs2: Don't demote a glock until its revokes are written
  cpufreq: imx6q: fix error handling
  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
  spi: spi-fsl-dspi: Replace interruptible wait queue with a simple completion
  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()

[Kernel-packages] [Bug 1864642] Re: dscr_sysfs_test / futex_bench / tm-unavailable in powerpc from ubuntu_kernel_selftests timeout on PowerPC nodes with B-5.3

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

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

Title:
  dscr_sysfs_test / futex_bench / tm-unavailable  in powerpc from
  ubuntu_kernel_selftests timeout on PowerPC nodes with B-5.3

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  == SRU Justification ==
  Some specific tests in powerpc can take longer than the default 45
  seconds that added in commit 852c8cbf34d3 ("selftests/kselftest/runner.sh:
  Add 45 second timeout per test") to run, the following test result was
  collected across 2 Power8 nodes and 1 Power9 node in our pool:
powerpc/benchmarks/futex_bench - 52s
powerpc/dscr/dscr_sysfs_test - 116s
powerpc/signal/signal_fuzzer - 88s
powerpc/tm/tm_unavailable_test - 168s
powerpc/tm/tm-poison - 240s

  Thus they will fail with TIMEOUT error.

  == Fix ==
  * 850507f3 ("selftests/powerpc: Turn off timeout setting for benchmarks, 
dscr, signal, tm")

  Only Eoan and newer kernel will need this fix.
  For Eoan, this patch can be applied with some context adjustment. 
  For Focal, there is a SAUCE patch which turned off timeout setting for 
  benchmarks and tm that needs to be reverted first, and this patch can
  be applied with some context adjustment too

  == Test ==
  Patch tested on PowerPC and it works as expected.

  == Regression Potential ==
  Low, changes limited to testing tools for PowerPC.

  
  == Original Bug Report ==
  Issue found on Power9 node baltar with B-5.3 (5.3.0-41.33~18.04.1-generic)

   # selftests: benchmarks: futex_bench
   # test: futex_bench
   # tags: git_version:unknown
   # time = 52.042224
   #
   not ok 5 selftests: benchmarks: futex_bench # TIMEOUT

   # selftests: dscr: dscr_sysfs_test
   # test: dscr_sysfs_test
   # tags: git_version:unknown
   #
   not ok 6 selftests: dscr: dscr_sysfs_test # TIMEOUT

  Need to check if this has something to do with the timeout setting
  like in bug 1864626

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: ppc64el
  Date: Tue Feb 25 11:23:58 2020
  ProcLoadAvg: 1.28 22.46 46.59 3/1347 62287
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3837 00:18:562 0 EOF
   2: POSIX  ADVISORY  WRITE 3864 00:18:588 0 EOF
   3: FLOCK  ADVISORY  WRITE 4515 00:18:463 0 EOF
   4: FLOCK  ADVISORY  WRITE 3844 00:18:579 0 EOF
   5: POSIX  ADVISORY  WRITE 1820 00:18:343 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 5.3.0-40-generic (buildd@bos02-ppc64el-007) (gcc 
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #32~18.04.1-Ubuntu SMP Mon Feb 3 
14:05:15 UTC 2020
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 9
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15

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

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

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

Title:
  Backport MPLS patches from 5.3 to 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==
  Mellanox is requesting a backport of the following commit IDs from 5.3
  back to 5.0 and 4.15:
  * 5dc9520bf04a ("net/mlx5e: Report netdevice MPLS features")
  * 8b6912a50193 ("net: vlan: Inherit MPLS features from parent device")
  * 2e770b507ccd ("net: bonding: Inherit MPLS features from slave devices")
  * e4683f35f8e5 ("net/mlx5e: Move to HW checksumming advertising")

  Netdevice HW MPLS features are not passed from device driver's netdevice
  to upper netdevice, specifically VLAN and bonding netdevice which are
  created by the kernel when needed.

  This prevents enablement and usage of HW offloads, such as TSO and
  checksumming for MPLS tagged traffic when running via VLAN or bonding
  interface.

  The patches introduce changes to the initialization steps of the VLAN
  and bonding netdevices to inherit the MPLS features from lower
  netdevices to allow the HW offloads.

  == Fix ==
  * 5dc9520bf04a ("net/mlx5e: Report netdevice MPLS features")
  * 8b6912a50193 ("net: vlan: Inherit MPLS features from parent device")
  * 2e770b507ccd ("net: bonding: Inherit MPLS features from slave devices")
  * e4683f35f8e5 ("net/mlx5e: Move to HW checksumming advertising")

  The first two patches can be cherry-picked into Disco, and the rest
  will require some context adjustment.

  == Test ==
  Test kernels can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1851446-MPLS-0407/

  Kernel tested with positive test result and approved by their QA.

  == Regression Potential ==
  Low, changes just for adding MPLS feature and comes with positive
  test result.


  == Original Bug Report ==
  Mellanox is requesting a backport of the following commit IDs from 5.3 back 
to 4.15.

  Netdevice HW MPLS features are not passed from device driver's
  netdevice to upper netdevice, specifically VLAN and bonding netdevice
  which are created by the kernel when needed.

  This prevents enablement and usage of HW offloads, such as TSO and
  checksumming for MPLS tagged traffic when running via VLAN or bonding
  interface.

  The patches introduce changes to the initialization steps of the VLAN and
  bonding netdevices to inherit the MPLS features from lower netdevices to 
allow the HW offloads.

  Ariel Levkovich (2):
    net: bonding: Inherit MPLS features from slave devices
    net: vlan: Inherit MPLS features from parent device

   drivers/net/bonding/bond_main.c | 11 +++
   net/8021q/vlan_dev.c|  1 +
   2 files changed, 12 insertions(+)

  https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html

  Commit IDs (All landed in 5.3)
  600bb0318c18e9616d97ad123caaa7c5f7bf222c
  8b6912a5019356d7adb1b8a146c9eef5e679bf98
  2e770b507ccde8eedc129946e4b78ceed0a22df2

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

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

[Kernel-packages] [Bug 1871688] Re: LIO hanging in iscsit_free_session and iscsit_stop_session

Target to Xenial was meant for Xenial-hwe (derivative of Bionic).

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1871688

Title:
  LIO hanging in iscsit_free_session and iscsit_stop_session

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

Bug description:
  The target subsystem (LIO) can hang if multiple threads try to destroy
  iSCSI sessions simultaneously. This is reproducible on systems that
  have multiple targets with initiators regularly
  connecting/disconnecting.

  This may happen when a "targetcli iscsi/iqn.../tpg1 disable" command
  is executed when a logout operation is underway.

  The iscsi target doesn't handle such events in a correct way: two or
  more threads may end up sleeping while waiting for the driver to close
  the remaining connections on the session. When the connections are
  closed, the driver wakes up only the first thread that will then
  proceed to destroy the session structure. The remaining threads are
  blocked there forever, waiting on a completion synchronization
  mechanism that doesn't exist in memory anymore because it has been
  freed by the first thread.

  Note that if the blocked threads are somehow forced to wake up, they
  will try to free the same iSCSI session structure destroyed by the
  first thread, causing double frees, memory corruptions, etc.

  The driver has been reorganized so the concurrent threads will set a
  flag in the session structure to notify the driver that the session
  should be destroyed; then, they wait for the driver to close the
  remaining connections. When the connections are all closed, the driver
  will wake up all the threads and will wait for the refcount of the
  iSCSI session structure to reach zero. When the last thread wakes up,
  the refcount is decreased to zero and the driver can proceed to
  destroy the session structure because no one is referencing it
  anymore.

  I've witnessed this happening on hundreds of Ubuntu 16.04.5 systems.
  It is a regression, because this did not occur several years ago.
  Unfortunately, I don't have detailed records from that far back to
  determine exactly which kernel I was running that was not affected by
  this bug (I believe it was either 4.8.x or 4.10.x).

  I've attached the requested uname, version_signature, dmesg, and lspci
  from my system. However, I've seen this happen on a wide array of
  hardware: 2 to 24 cores, 8GB to 256GB RAM, both AMD and Intel CPUs,
  onboard storage and PCIe SAS cards, etc.

  This has been fixed in the upstream master branch, but it hasn't yet
  been backported to "-stable".

  To fix this in the Ubuntu kernel, these three commits should be backported:
  * 
https://github.com/torvalds/linux/commit/e49a7d994379278d3353d7ffc7994672752fb0ad
  * 
https://github.com/torvalds/linux/commit/57c46e9f33da530a2485fa01aa27b6d18c28c796
  * 
https://github.com/torvalds/linux/commit/626bac73371eed79e2afa2966de393da96cf925e

  I'd like these commits to be added to the xenial, bionic, and focal
  kernels.

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

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Fix Committed

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.

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

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

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

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 1873043] Re: Bionic update: upstream stable patchset 2020-04-15

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

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

Title:
  Bionic update: upstream stable patchset 2020-04-15

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-04-15

  Ported from the following upstream stable releases:
  v4.14.176, v4.19.115

     from git://git.kernel.org/

  ipv4: fix a RCU-list lock in fib_triestat_seq_show
  net, ip_tunnel: fix interface lookup with no key
  sctp: fix refcount bug in sctp_wfree
  sctp: fix possibly using a bad saddr with a given dst
  drm/bochs: downgrade pci_request_region failure from error to warning
  initramfs: restore default compression behavior
  tools/power turbostat: Fix gcc build warnings
  drm/etnaviv: replace MMU flush marker with flush sequence
  blk-mq: sync the update nr_hw_queues with blk_mq_queue_tag_busy_iter
  blk-mq: Allow blocking queue tag iter callbacks
  misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
  coresight: do not use the BIT() macro in the UAPI header
  padata: always acquire cpu_hotplug_lock before pinst->lock
  mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
  ipv6: don't auto-add link-local address to lag ports
  net: dsa: bcm_sf2: Ensure correct sub-node is parsed
  net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before 
accessing PHY registers
  net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
  slcan: Don't transmit uninitialized stack data in padding
  mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
  random: always use batched entropy for get_random_u{32,64}
  tools/accounting/getdelays.c: fix netlink attribute length
  hwrng: imx-rngc - fix an error path
  ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
  IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
  IB/hfi1: Fix memory leaks in sysfs registration and unregistration
  ceph: remove the extra slashes in the server path
  ceph: canonicalize server path in place
  Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
  RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
  fbcon: fix null-ptr-deref in fbcon_switch
  clk: qcom: rcg: Return failure for RCG update
  drm/msm: stop abusing dma_map/unmap for cache
  arm64: Fix size of __early_cpu_boot_status
  rpmsg: glink: Remove chunk size word align warning
  usb: dwc3: don't set gadget->is_otg flag
  drm_dp_mst_topology: fix broken drm_dp_sideband_parse_remote_dpcd_read()
  drm/msm: Use the correct dma_sync calls in msm_gem
  misc: rtsx: set correct pcr_ops for rts522A
  mei: me: add cedar fork device ids
  power: supply: axp288_charger: Add special handling for HP Pavilion x2 10
  rxrpc: Fix sendmsg(MSG_WAITALL) handling
  bitops: protect variables in set_mask_bits() macro
  RDMA/ucma: Put a lock around every call to the rdma_cm layer
  RDMA/cma: Teach lockdep about the order of rtnl and lock
  UBUNTU: upstream stable to v4.14.176, v4.19.115

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

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

[Kernel-packages] [Bug 1874502] Re: Bionic update: upstream stable patchset 2020-04-23

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

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

Title:
  Bionic update: upstream stable patchset 2020-04-23

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-04-23

  Ported from the following upstream stable releases:
 v4.19.116

     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
  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()
  libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
  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
  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
  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
  uapi: rename ext2_swab() to swab() and share globally in swab.h
  slub: improve bit diffusion for freelist ptr obfuscation
  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/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
  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

[Kernel-packages] [Bug 1349028] Re: getitimer returns it_value=0 erroneously

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

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

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

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

Title:
  getitimer returns it_value=0 erroneously

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  According to the 'getitimer()' man page: "The element it_value is set
  to the amount of time remaining on the timer, or zero if the  timer is
  disabled.  Similarly, it_interval is set to the reset value."

  As such the following Perl program should never exit:

  use Time::HiRes;
  $SIG{VTALRM} = sub { };
  Time::HiRes::setitimer(::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
  while (1) {
  my @t = Time::HiRes::getitimer(::HiRes::ITIMER_VIRTUAL);
  exit 0 if $t[0] == 0;
  }

  and on linux-image 3.11.0-18-generic (and all other systems tested) it
  loops forever but 3.13.0-32-generic it exits.  Have not bisected
  between those kernels, nor am I likely to be able to do so soon.

  This Perl program shows the timer countdown:

  use Time::HiRes;
  my $r = [Time::HiRes::gettimeofday()];
  sub display {
  my ($desc) = @_;
  my @t = Time::HiRes::getitimer(::HiRes::ITIMER_VIRTUAL);
  my $i = Time::HiRes::tv_interval($r);
  printf "%s: elasped=%.8f; time left=%.6f reset time=%.6f\n", $desc,
  $i,@t;
  }
  $SIG{VTALRM} = sub {
  display('VTALRM');
  exit;
  };
  Time::HiRes::setitimer(::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
  while (1) {
  display('inloop');
  }

  on other (working) systems it gives:

  inloop: elasped=1.65178400; time left=0.001000 reset time=0.401000
  inloop: elasped=1.65184200; time left=0.001000 reset time=0.401000
  inloop: elasped=1.65186800; time left=0.001000 reset time=0.401000
  inloop: elasped=1.65192300; time left=0.001000 reset time=0.401000
  inloop: elasped=1.65198100; time left=0.001000 reset time=0.401000
  VTALRM: elasped=1.65209800; time left=0.40 reset time=0.401000
  (end of file)

  but on the 3.13.0-32-generic or later kernel I get:

  inloop: elasped=0.54692100; time left=0.33 reset time=0.40
  inloop: elasped=0.54692800; time left=0.26 reset time=0.40
  inloop: elasped=0.54693500; time left=0.20 reset time=0.40
  inloop: elasped=0.54694100; time left=0.13 reset time=0.40
  inloop: elasped=0.54694800; time left=0.07 reset time=0.40
  inloop: elasped=0.54695500; time left=0.00 reset time=0.40
  inloop: elasped=0.54696200; time left=0.004000 reset time=0.40
  [...]
  VTALRM: elasped=0.55013600; time left=0.397062 reset time=0.40
  (end of file)

  The reset time also looks dodgy.

  Hardware is an Intel Core i7-920 on Asus P6T Deluxe v2 (X58)
  motherboard and hasn't changed.

  
  Requested information:

  Ubuntu 3.13.0-32.57-generic 3.13.11.4

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  # apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 3.13.0.32.38
Candidate: 3.13.0.32.38
Version table:
   *** 3.13.0.32.38 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  500 http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/ 
trusty/main amd64 Packages
  100 /var/lib/dpkg/status
   3.13.0.24.28 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tivrusky   3009 F pulseaudio
   /dev/snd/controlC0:  tivrusky   3009 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c026abdc-9fee-425c-b5ae-020bf6ea2ad6
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: root=UUID=3ea7a4cb-eade-4906-b545-5133d8c14080 ro quiet 
splash
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1874713] Re: Instabilities when returning from idle mode and delay when detecting Intel bluetooth [8087:07da] peripherals

Does blacklisting the power saving option in tlp work for you?

Open the tlp configuration file using the terminal: gksu gedit
/etc/default/tlp and search the line containing: USB_BLACKLIST= Then
edit this line and enter the ID of the bluetooth device, e.g.
USB_BLACKLIST="8087:07da"

** Summary changed:

- Instabilities when returning from idle mode and delay when detecting 
bluetooth peripherals
+ Instabilities when returning from idle mode and delay when detecting Intel 
bluetooth [8087:07da] peripherals

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  Intel bluetooth [8087:07da] peripherals

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  etm2253 F pulseaudio
   /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: Sony Corporation SVS151290X
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS151290X
  dmi.product.sku: 54520726
  dmi.product.version: C60BKPK7
  dmi.sys.vendor: Sony Corporation

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

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

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

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

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

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 1874713] Re: Instabilities when returning from idle mode and delay when detecting bluetooth peripherals

** Tags added: hwe-bluetooth

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  bluetooth peripherals

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  etm2253 F pulseaudio
   /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: Sony Corporation SVS151290X
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS151290X
  dmi.product.sku: 54520726
  dmi.product.version: C60BKPK7
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2020-04-24 Thread Matthew Swift

I followed your instructions of 4/21 regarding changing kernel
parameters and attaching PuTTY etc.  Screenshot of the edited parameters
is next to your email attached (if attachment won't get published, I
will post online). I can send the PuTTY output, but I don't think we
learned anything we didn't already see in dmesg. Console login prompt
comes up quickly, then the long delay in the Hyper-V Connection window
before arriving at the Xorg GUI login. Alt-SysRq-w during this time
gives nothing, just two lines like these:

[   70.428525] sysrq: Show Blocked State
[   70.429990]   taskPC stack   pid father 

While doing this, I noticed today that some previously reliable ways to
get to the "shortcut boot" (the XRDP login screen, which comes up
quickly, instead of waiting for the Xorg screen) were no longer reliable
(e.g., sometimes "power off" force in Hyper-V Manager and restart led to
a long boot). I also discovered a state in which starting the VM from an
"off" state in Hyper-V Manager apparently skipped even the Grub screen
and went quickly to XRDP login screen. At this point I rebooted the
host. Some deep kind of Windows caching going on? After reboot,
behaviors earlier described became predictable again.

Three questions:

1) You wrote on 4/22 (second mail): "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)". How did you intentionally
"try XRDP mode"? How do you have any control over whether you get the
XRDP or Xorg login screen? It seems to me I do not have any control.
>From a user's perspective, that is the whole problem here, how to get
the XRDP login screen on first startup (and all subsequent) of a 19.10
VM within a given Hyper-V Connection window.  As shown earlier, when the
user gets the XRDP login, the (presumably) same processes are still
being delayed for the same length of time as when the user is forced to
wait for the Xorg login screen, but the user has meanwhile been able to
log in via XRDP and begin doing his or her work. Furthermore, screen
size control and cut-and-paste from guest to host are available only
with the XRDP login. From user's perspective, I think the problem is
solved once user can log into the VM and start working without waiting
for a 90s timeout, and screen size control and cut-paste are
operational. Which in my case seems to be equivalent to being able to
get the XRDP login screen reliably; if I get it, it always arrives
quickly.

2)  You wrote on 4/21: "It looks systemd can be configured to use
"--log-level=debug --default- standard-output=kmsg --default-standard-
error=kmsg". Please advise me how to do this. I administered Debian
systems from Buzz (1996) to Squeeze (2011), and a lot of the boot
process is new to me. (In those days, one had to use Ctrl-S / Ctrl-Q to
be able to read booting output.)

3) You wrote on 4/22: "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." Likewise, please advise me *how* to disable them. I've
been trying unsuccessfully to disable Ubuntu automatic updates (in
another VM, not the one I am testing) and have concluded that I really
do not understand any of this newfangled .service stuff. (And I
shouldn't have to, to achieve that objective, but that is a different
gripe.)


** Attachment added: "kernel_parameters.PNG"
   
https://bugs.launchpad.net/bugs/1848534/+attachment/5359626/+files/kernel_parameters.PNG

-- 
You 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

[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)

@Redsandro, any cold boot and only cold boot will Intel reload fw and
print fw filename. We know it rarely happens, and that's why we're eager
to know what hardware variant do you have.

@Ian, you can modprobe btusb alone and it will also load btintel as
well. ~lazy engineer.

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

Title:
  Bluetooth unavailable after updates - Reading Intel version
  information failed (-110)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After 10 days of uptime with automatic updates, I rebooted. Bluetooth,
  which I use every day, is no longer available.

  $ dmesg | grep -i bluetooth
  [4.846072] Bluetooth: Core ver 2.22
  [4.846088] Bluetooth: HCI device and connection manager initialized
  [4.846092] Bluetooth: HCI socket layer initialized
  [4.846094] Bluetooth: L2CAP socket layer initialized
  [4.846096] Bluetooth: SCO socket layer initialized
  [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [5.434082] Bluetooth: BNEP filters: protocol multicast
  [5.434086] Bluetooth: BNEP socket layer initialized
  [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout
  [6.874129] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  $ uname -a
  Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04
  LTS.

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

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

[Kernel-packages] [Bug 1874711] Re: wifi probelm

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

Title:
  wifi probelm

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have upgraded my ubuntu to 20.04 and I lost my wifi connection what
  should I do?

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

2020-04-24 Thread Jouni Mettala

Good job. Now v5.2 is known good one. v5.3 is known bad. There are also 
other kernels tested including latest upstream one.

It is possible to bisect bug to a single commit
https://wiki.ubuntu.com/Kernel/KernelBisection
Bisecting is good way to find developer to look at your bug.

Before that you can test 5.3-rc1 Most new code is introduced in rc1. 
Otherwise middle point is good to test.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/

You can see Linux version of your /var/log/dmesg by first line of the 
file. For example less /var/log/dmesg

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874045] Re: Xenial update: 4.4.219 upstream stable release

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

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

Title:
  Xenial update: 4.4.219 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

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

     4.4.219 upstream stable release
     from git://git.kernel.org/

  The following patches from the 4.4.219 stable release shall be applied:
  * drm/bochs: downgrade pci_request_region failure from error to warning
  * ipv4: fix a RCU-list lock in fib_triestat_seq_show
  * net, ip_tunnel: fix interface lookup with no key
  * sctp: fix possibly using a bad saddr with a given dst
  * l2tp: Correctly return -EBADF from pppol2tp_getname.
  * net: l2tp: Make l2tp_ip6 namespace aware
  * l2tp: fix race in l2tp_recv_common()
  * l2tp: ensure session can't get removed during pppol2tp_session_ioctl()
  * l2tp: fix duplicate session creation
  * l2tp: Refactor the codes with existing macros instead of literal number
  * l2tp: ensure sessions are freed after their PPPOL2TP socket
  * l2tp: fix race between l2tp_session_delete() and l2tp_tunnel_closeall()
  * usb: gadget: uac2: Drop unused device qualifier descriptor
  * usb: gadget: printer: Drop unused device qualifier descriptor
  * padata: always acquire cpu_hotplug_lock before pinst->lock
  * mm: mempolicy: require at least one nodeid for MPOL_PREFERRED
  * net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
  * slcan: Don't transmit uninitialized stack data in padding
  * random: always use batched entropy for get_random_u{32,64}
  * tools/accounting/getdelays.c: fix netlink attribute length
  * power: supply: axp288_charger: Fix unchecked return value
  * xen-netfront: Fix mismatched rtnl_unlock
  * xen-netfront: Update features after registering netdev
  * ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
  * IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
  * Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
  * RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
  * clk: qcom: rcg: Return failure for RCG update
  * drm_dp_mst_topology: fix broken drm_dp_sideband_parse_remote_dpcd_read()
  * Linux 4.4.219

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

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

[Kernel-packages] [Bug 1873852] Re: Xenial update: 4.4.218 upstream stable release

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

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

Title:
  Xenial update: 4.4.218 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

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

     4.4.218 upstream stable release
     from git://git.kernel.org/

  The following patches from the 4.4.218 stable release shall be applied:
  * spi: qup: call spi_qup_pm_resume_runtime before suspending
  * powerpc: Include .BTF section
  * ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes
  * spi/zynqmp: remove entry that causes a cs glitch
  * drm/exynos: dsi: propagate error value and silence meaningless warning
  * drm/exynos: dsi: fix workaround for the legacy clock name
  * altera-stapl: altera_get_note: prevent write beyond end of 'key'
  * USB: Disable LPM on WD19's Realtek Hub
  * usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters
  * USB: serial: option: add ME910G1 ECM composition 0x110b
  * usb: host: xhci-plat: add a shutdown
  * USB: serial: pl2303: add device-id for HP LD381
  * ALSA: line6: Fix endless MIDI read loop
  * ALSA: seq: virmidi: Fix running status after receiving sysex
  * ALSA: seq: oss: Fix running status after receiving sysex
  * ALSA: pcm: oss: Avoid plugin buffer overflow
  * ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks
  * staging: rtl8188eu: Add device id for MERCUSYS MW150US v2
  * staging/speakup: fix get_word non-space look-ahead
  * intel_th: Fix user-visible error codes
  * rtc: max8907: add missing select REGMAP_IRQ
  * memcg: fix NULL pointer dereference in __mem_cgroup_usage_unregister_event
  * mm: slub: be more careful about the double cmpxchg of freelist
  * mm, slub: prevent kmalloc_node crashes and memory leaks
  * x86/mm: split vmalloc_sync_all()
  * USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL
  * USB: cdc-acm: fix rounding error in TIOCSSERIAL
  * kbuild: Disable -Wpointer-to-enum-cast
  * futex: Fix inode life-time issue
  * futex: Unbreak futex hashing
  * ALSA: hda/realtek: Fix pop noise on ALC225
  * arm64: smp: fix smp_send_stop() behaviour
  * Revert "drm/dp_mst: Skip validating ports during destruction, just ref"
  * hsr: fix general protection fault in hsr_addr_is_self()
  * net: dsa: Fix duplicate frames flooded by learning
  * net_sched: cls_route: remove the right filter from hashtable
  * net_sched: keep alloc_hash updated after hash allocation
  * NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
  * slcan: not call free_netdev before rtnl_unlock in slcan_open
  * vxlan: check return value of gro_cells_init()
  * hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
  * hsr: add restart routine into hsr_get_node_list()
  * hsr: set .netnsok flag
  * vhost: Check docket sk_family instead of call getname
  * IB/ipoib: Do not warn if IPoIB debugfs doesn't exist
  * uapi glibc compat: fix outer guard of net device flags enum
  * KVM: VMX: Do not allow reexecute_instruction() when skipping MMIO instr
  * drivers/hwspinlock: use correct radix tree API
  * net: ipv4: don't let PMTU updates increase route MTU
  * cpupower: avoid multiple definition with gcc -fno-common
  * dt-bindings: net: FMan erratum A050385
  * scsi: ipr: Fix softlockup when rescanning devices in petitboot
  * mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
  * sxgbe: Fix off by one in samsung driver strncpy size arg
  * i2c: hix5hd2: add missed clk_disable_unprepare in remove
  * perf probe: Do not depend on dwfl_module_addrsym()
  * scripts/dtc: Remove redundant YYLOC global declaration
  * scsi: sd: Fix optimal I/O size for devices that change reported values
  * mac80211: mark station unauthorized before key removal
  * genirq: Fix reference leaks on irq affinity notifiers
  * vti[6]: fix packet tx through bpf_redirect() in XinY cases
  * xfrm: fix uctx len check in verify_sec_ctx_len
  * xfrm: add the missing verify_sec_ctx_len check in xfrm_add_acquire
  * xfrm: policy: Fix doulbe free in xfrm_policy_timer
  * vti6: Fix memory leak of skb if input policy check fails
  * tools: Let O= makes handle a relative path with -C option
  * USB: serial: option: add support for ASKEY WWHC050
  * USB: serial: option: add BroadMobi BM806U
  * USB: serial: option: add Wistron Neweb D19Q1
  * USB: cdc-acm: restore

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

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

Title:
  debugfs: File 'aqm' in directory 'phy0' already present!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Started after 20.04 beta upgrade to 20.04 completed

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1036 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 11:41:44 2020
  InstallationDate: Installed on 2020-04-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   wlan0 no wireless extensions.
  MachineType: LENOVO 81N8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ce238cdc-08cb-44c2-81c6-a1be8dd9bef3 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-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: 07/02/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ALCN27WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: 3192 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S340-15IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrALCN27WW(V2.04):bd07/02/2019:svnLENOVO:pn81N8:pvrLenovoideapadS340-15IWL:rvnLENOVO:rnLNVNB161216:rvr3192WIN:cvnLENOVO:ct10:cvrLenovoideapadS340-15IWL:
  dmi.product.family: ideapad S340-15IWL
  dmi.product.name: 81N8
  dmi.product.sku: LENOVO_MT_81N8_BU_idea_FM_ideapad S340-15IWL
  dmi.product.version: Lenovo ideapad S340-15IWL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1872726] net/mlx5: fix endianness handling in pedit mask

2020-04-24 Thread bugproxy

--- Comment on attachment From niklas.schne...@ibm.com 2020-04-24 11:41 
EDT---


This is the upstream commit

404402abd5f90aa90a134eb9604b1750c1941529 ("net/mlx5: fix endianness
handling in pedit mask")

backported for focal-master next. It has been running internally for a
while so has seen testing on Z, as mentioned before we believe this
should also be necessary for other Big Endian architectures.

** Attachment added: "net/mlx5: fix endianness handling in pedit mask"
   
https://bugs.launchpad.net/bugs/1872726/+attachment/5359595/+files/0001-net-mlx5-fix-endianness-handling-in-pedit-mask.patch

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

Title:
  [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask

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

Bug description:
  Issue found in the Mellanox mlx5 device driver:

  The mask value is provided as 64 bit and has to be casted in
  either 32 or 16 bit. On big endian systems the wrong half was
  casted which resulted in an all zero mask.

  We need to get the upstream commit picked up for the Ubuntu 20.04
  kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=404402abd5f90aa90a134eb9604b1750c1941529

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

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

[Kernel-packages] [Bug 1874844] [NEW] debugfs: File 'aqm' in directory 'phy0' already present!

2020-04-24 Thread paul-lawrenceville

Public bug reported:

Started after 20.04 beta upgrade to 20.04 completed

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
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  paul   1036 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Apr 24 11:41:44 2020
InstallationDate: Installed on 2020-04-21 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
 
 wlan0 no wireless extensions.
MachineType: LENOVO 81N8
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ce238cdc-08cb-44c2-81c6-a1be8dd9bef3 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-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: 07/02/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: ALCN27WW(V2.04)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: 3192 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad S340-15IWL
dmi.modalias: 
dmi:bvnLENOVO:bvrALCN27WW(V2.04):bd07/02/2019:svnLENOVO:pn81N8:pvrLenovoideapadS340-15IWL:rvnLENOVO:rnLNVNB161216:rvr3192WIN:cvnLENOVO:ct10:cvrLenovoideapadS340-15IWL:
dmi.product.family: ideapad S340-15IWL
dmi.product.name: 81N8
dmi.product.sku: LENOVO_MT_81N8_BU_idea_FM_ideapad S340-15IWL
dmi.product.version: Lenovo ideapad S340-15IWL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  debugfs: File 'aqm' in directory 'phy0' already present!

Status in linux package in Ubuntu:
  New

Bug description:
  Started after 20.04 beta upgrade to 20.04 completed

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1036 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 11:41:44 2020
  InstallationDate: Installed on 2020-04-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   wlan0 no wireless extensions.
  MachineType: LENOVO 81N8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ce238cdc-08cb-44c2-81c6-a1be8dd9bef3 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-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: 07/02/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ALCN27WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: 3192 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S340-15IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrALCN27WW(V2.04):bd07/02/2019:svnLENOVO:pn81N8:pvrLenovoideapadS340-15IWL:rvnLENOVO:rnLNVNB161216:rvr3192WIN:cvnLENOVO:ct10:cvrLenovoideapadS340-15IWL:
  dmi.product.family: ideapad S340-15IWL
  dmi.product.name: 81N8
  dmi.product.sku: LENOVO_MT_81N8_BU_idea_FM_ideapad S340-15IWL
  dmi.product.version: Lenovo ideapad S340-15IWL
  dmi.sys.vendor: LENOVO

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

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

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

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 1874257

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: MACs ctos:

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

2020-04-24 Thread Jack Howarth

This offending package for bug is proving very difficult to pin down. I
have tried to sequentially regress all the packages that the recovery
kernel boot are likely to use back to their eoan versions on a 20.04
installation. In each case, I reinstalled the kernels afterwards to
insure that the initrd.img files were full regenerated and reinstalled.
The installed packages from the following have been regression tested...

plymouth
busybox
udev
kmod
grub
initramfs
libklibc

and none of these eliminate the breakage in nomodeset under 20.04 on a
Mac ROMed GTX680.

The only 'workaround' that I have found is to append 'nouveau.modeset=1'
after 'nomodeset' in grub's recovery kernel entry.

-- 
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 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)

2020-04-24 Thread Ian Morris

I too am having this problem after a suspend/resume [deep].

Kubuntu 18.04 (nearly up to date patches (20200424)

dmesg:

[285163.220315] Bluetooth: hci0: command 0xfc05 tx timeout
[285163.220316] Bluetooth: hci0: Reading Intel version information failed (-110)

To restart the BT adapter a simple:-

rmmod btusb
rmmod btintel
modprobe btinel
modprobe btusb

is sufficient for me.

I hope this helps.

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

Title:
  Bluetooth unavailable after updates - Reading Intel version
  information failed (-110)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After 10 days of uptime with automatic updates, I rebooted. Bluetooth,
  which I use every day, is no longer available.

  $ dmesg | grep -i bluetooth
  [4.846072] Bluetooth: Core ver 2.22
  [4.846088] Bluetooth: HCI device and connection manager initialized
  [4.846092] Bluetooth: HCI socket layer initialized
  [4.846094] Bluetooth: L2CAP socket layer initialized
  [4.846096] Bluetooth: SCO socket layer initialized
  [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [5.434082] Bluetooth: BNEP filters: protocol multicast
  [5.434086] Bluetooth: BNEP socket layer initialized
  [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout
  [6.874129] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  $ uname -a
  Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04
  LTS.

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

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

[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

2020-04-24 Thread Jay

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

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: MACs ctos: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: MACs stoc: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: compression ctos: none,z...@openssh.com,zlib
  debug2: compression stoc:

[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

** No longer affects: makedumpfile (Ubuntu 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/1869672

Title:
  Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

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

Bug description:
  [Impact]
  * Kdump kernel can't be loaded using Linux kernel 4.15.0-65 and newer on 
Bionic; kexec fails to load using the "new" kexec_file_load() syscall, showing 
the following messages in dmesg:

  kexec: Undefined symbol: __stack_chk_fail
  kexec-bzImage64: Loading purgatory failed

  * Reason for this was that backport from upstream commit b059f801a937
  ("x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS")
  makes use of a config option guard that wasn't backported to Ubuntu
  4.15.x series.

  * Also, we found another related issue, an undefined memcpy() symbol,
  that was related to the above patch too. We propose here a specific
  fix for Bionic, in the form of the patch attached in comment #18.

  [Test case]

  * Basically the test consists in booting a signed kernel in a secure
  boot environment (this is required given Ubuntu kernel is built with
  CONFIG_KEXEC_VERIFY_SIG so to use kexec_file_load() we must be in a
  proper signed/secure booted system). It works until 4.15.0-64, and
  starts to fail after this release, until the current proposed version
  4.15.0-97. We can also check kdump-tools service in the failing case,
  which shows:

  systemctl status kdump-tools
  [...]
  kdump-tools[895]: Starting kdump-tools: * Creating symlink 
/var/lib/kdump/vmlinuz
  kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img
  kdump-tools[895]: kexec_file_load failed: Exec format error
  kdump-tools[895]: * failed to load kdump kernel
  [...]

  * With the patch attached in the LP, it works normally again and I was
  able to collect a kdump.

  [Regression potential]

  * Given the patch is quite simple and fixes the build of purgatory, I
  think the regression potential is low. One potential regression in
  future would be on backports to purgatory Makefile, making them more
  difficult/prone to errors; given purgatory is a pretty untouchable
  code, I consider the regression potential here to be really low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1871182] Re: [RTL810xE] No ethernet connection

2020-04-24 Thread Michael Born

I could figure out "my" problem: 
https://ubuntuforums.org/showthread.php?t=2441385
somehow the network device name seems to have changed form enp3s0 as written in 
the /etc/netplan/00-installer-config.yaml config file to enp2s0. Then, my 
network was not activated at boot-up any more.

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

Title:
  [RTL810xE] No ethernet connection

Status in linux package in Ubuntu:
  Fix Released

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

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

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

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

This time with the last fast kernel, 5.2. The bootup was slightly slower
than with 4.15, but I think this might relate to snap module loading. I
should also point out that the difference between kernels 4.15, 5.1 and
5.2 vs the kernels after 5.3 is more than what is indicated by the
SystemD analysis. With the newer kernels there is an additional delay of
about a minute from the point where I log in until I get a working
desktop.

Attached is the SystemD analysis for kernel 5.2

** Attachment added: "SystemD analysis 5.2 kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359509/+files/SystemD%205.2%20kernel%20bootup.odt

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

Finally, a second dmesg for the 5.2 kernel boot.(I'm not sure whether
dmesg or dmesg.0 is the right one.

** Attachment added: "dmesg.0 for 5.2 boot (I hope)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359527/+files/dmesg.0

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

Next is the first of two dmesg logs for the 5.2 kernel.

** Attachment added: "dmesg for 5.2 boot (I hope)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359510/+files/dmesg

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

** Description changed:

- 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-65 and newer on 
Bionic; kexec fails to load using the "new" kexec_file_load() syscall, showing 
the following messages in dmesg:
  
- [Impact]
- * Kdump kernel can't be loaded using linux kernel 4.15.0-76.
+ kexec: Undefined symbol: __stack_chk_fail
+ kexec-bzImage64: Loading purgatory failed
  
- [Environment]
- Description:Ubuntu 18.04.4 LTS
- Release:18.04
+ * Reason for this was that backport from upstream commit b059f801a937
+ ("x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS")
+ makes use of a config option guard that wasn't backported to Ubuntu
+ 4.15.x series.
  
- 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
+ * Also, we found another related issue, an undefined memcpy() symbol,
+ that was related to the above patch too. We propose here a specific fix
+ for Bionic, in the form of the patch attached in comment #18.
  
  [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)
+ * Basically the test consists in booting a signed kernel in a secure
+ boot environment (this is required given Ubuntu kernel is built with
+ CONFIG_KEXEC_VERIFY_SIG so to use kexec_file_load() we must be in a
+ proper signed/secure booted system). It works until 4.15.0-64, and
+ starts to fail after this release, until the current proposed version
+ 4.15.0-97. We can also check kdump-tools service in the failing case,
+ which shows:
  
- 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.
- 
+ systemctl status kdump-tools
+ [...]
+ kdump-tools[895]: Starting kdump-tools: * Creating symlink 
/var/lib/kdump/vmlinuz
+ kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img
+ kdump-tools[895]: kexec_file_load failed: Exec format error
+ kdump-tools[895]: * failed to load kdump kernel
+ [...]
  
- 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
+ * With the patch attached in the LP, it works normally again and I was
+ able to collect a kdump.
  
- 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
+ [Regression potential]
  
- 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.
+ * Given the patch is quite simple and fixes the build of purgatory, I
+ think the regression potential is

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

Next, dmesg.0

** Attachment added: "dmesg.0 for 5.3 boot (I hope)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359503/+files/dmesg.0

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

Next, a dmesg for that boot. Not sure which it is so I'll send two.

** Attachment added: "dmesg for 5.3 boot (I hope)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359502/+files/dmesg

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

Title:
  Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
  5k 27" iMac. The new 5.4 kernel was installed and has been updated a
  few times. The former LTS kernel (4.15) was retained. When I start up
  the computer with the new kernel, the process is very slow and it
  takes about 2 1/2 minutes to get to a working desktop. Doing the same
  startup with the old 4.15 kernel (in the 20.04 beta) takes
  approximately 25 seconds to a working desktop. Similarly, changing
  display settings, waking from sleep and shutting down the computer all
  take several minutes with the 5.4 kernel, vs 10-30 seconds with the
  4.15 kernel.

  To provide more information, I tried starting up this computer with
  the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
  Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
  as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
  the 4.15 LTS kernel.

  I suspect that the problem relates to the Radeon m9 390x video card in
  my iMac, but I have no idea what might have changed in the newer
  kernels to affect their compatibility with this iMac.

  ProblemType: Bug
  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/controlC2:  mfox   2497 F pulseaudio
   /dev/snd/controlC0:  mfox   2497 F pulseaudio
   /dev/snd/controlC1:  mfox   2497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 10:55:18 2020
  HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
  InstallationDate: Installed on 2018-05-09 (712 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Apple Inc. iMac17,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro 
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead 
initrd=boot\initrd.img-5.4.0-25-generic
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-25-generic N/A
   linux-backports-modules-5.4.0-25-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 176.0.0.0.0
  dmi.board.name: Mac-B809C3757DA9BB8D
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac17,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-B809C3757DA9BB8D
  dmi.modalias: 
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
  dmi.product.family: iMac17,1
  dmi.product.name: iMac17,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel

I uninstalled Virtualbox and tested kernels 5.1 and 5.2. Both showed
fast boots similar to 4.15. I then tested 5.3 by downloading it from the
ppa/mailine. This is where the slow boot started. I have attached two
dmesg's and a systemd analysis of the critical chain and blame for
kernel 5.3. I can't seem to send more than one file at a time, so I will
send 3 separate messages.

You can contrast this against the equivalent for kernel 5.2, which I
will reboot with and send results in the next set of messages.

** Attachment added: "SystemD analysis 5.3 kernel"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359501/+files/SystemD%205.3%20kernel%20bootup.odt

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

Title:
Very slow boot, wake from sleep and shutdown with 5.4 kernel

Status in linux package in Ubuntu:
Confirmed

Bug description:
I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015
5k 27" iMac. The new 5.4 kernel was installed and has been updated a
few times. The former LTS kernel (4.15) was retained. When I start up
the computer with the new kernel, the process is very slow and it
takes about 2 1/2 minutes to get to a working desktop. Doing the same
startup with the old 4.15 kernel (in the 20.04 beta) takes
approximately 25 seconds to a working desktop. Similarly, changing
display settings, waking from sleep and shutting down the computer all
take several minutes with the 5.4 kernel, vs 10-30 seconds with the
4.15 kernel.

To provide more information, I tried starting up this computer with
the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the
Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is
as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to
the 4.15 LTS kernel.

I suspect that the problem relates to the Radeon m9 390x video card in
my iMac, but I have no idea what might have changed in the newer
kernels to affect their compatibility with this iMac.

ProblemType: Bug
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/controlC2: mfox 2497 F pulseaudio
/dev/snd/controlC0: mfox 2497 F pulseaudio
/dev/snd/controlC1: mfox 2497 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 21 10:55:18 2020
HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a
InstallationDate: Installed on 2018-05-09 (712 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Apple Inc. iMac17,1
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro
root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead
initrd=boot\initrd.img-5.4.0-25-generic
RelatedPackageVersions:
linux-restricted-modules-5.4.0-25-generic N/A
linux-backports-modules-5.4.0-25-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2020
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 176.0.0.0.0
dmi.board.name: Mac-B809C3757DA9BB8D
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac17,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B809C3757DA9BB8D
dmi.modalias:
dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D:
dmi.product.family: iMac17,1
dmi.product.name: iMac17,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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

[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

** Patch added: 
"0001-UBUNTU-SAUCE-x86-purgatory-Fix-Makefile-to-prevent-u.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869672/+attachment/5359499/+files/0001-UBUNTU-SAUCE-x86-purgatory-Fix-Makefile-to-prevent-u.patch

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

Title:
  Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  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/linux/+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 1874713] Re: Instabilities when returning from idle mode and delay when detecting bluetooth peripherals

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  bluetooth peripherals

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  etm2253 F pulseaudio
   /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: Sony Corporation SVS151290X
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS151290X
  dmi.product.sku: 54520726
  dmi.product.version: C60BKPK7
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://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 1871182] Re: [RTL810xE] No ethernet connection

2020-04-24 Thread Ryan Amick

It doesn’t work for me either. I downloaded latest image and booted live. It 
didn’t work there either. 
I’m not sure why it was marked fix when it never worked for me. I was the one 
who first reported the bug. 

Sent from my iPhone

> On Apr 24, 2020, at 1:21 AM, You-Sheng Yang <1871...@bugs.launchpad.net> 
> wrote:
> 
> @Michael, if 5.4.0-26.30 doesn't work for you, please file a new bug
> instead as this one has been marked FIXRELEASED.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871182
> 
> Title:
>  [RTL810xE] No ethernet connection
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871182/+subscriptions

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

Title:
  [RTL810xE] No ethernet connection

Status in linux package in Ubuntu:
  Fix Released

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

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

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

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

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

[Kernel-packages] [Bug 1810214] Re: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all

2020-04-24 Thread Mikhail Klimovich

I think the same bug is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439?comments=all

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

Title:
  [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in linux package in Ubuntu:
  Expired

Bug description:
  There is no sound whatsoever while the controls all seems to indicate
  the playback is working. The patop's internal speaker, headphones,
  even bluetooth is not outputting any sound. Trying to upgrade the
  kernel to two different versions had no effect. There simply is no
  sound output nor is there any indication the microphone is working
  either, but without sound output that's hard to confirm. There are not
  issues with sounds when I boot into Windows

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.13-041913-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1193 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  1 14:18:09 2019
  InstallationDate: Installed on 2018-12-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1193 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FA_UX433FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1874713] Re: Instabilities when returning from idle mode and delay when detecting bluetooth peripherals

apport information

** Tags added: apport-collected

** Description changed:

  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  etm2253 F pulseaudio
+  /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-01-28 (86 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
+ MachineType: Sony Corporation SVS151290X
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-26-generic N/A
+  linux-backports-modules-5.4.0-26-generic  N/A
+  linux-firmware1.187
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
+ _MarkForUpload: True
+ dmi.bios.date: 03/13/2013
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: R1021C8
+ dmi.board.asset.tag: N/A
+ dmi.board.name: VAIO
+ dmi.board.vendor: Sony Corporation
+ dmi.board.version: N/A
+ dmi.chassis.asset.tag: N/A
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Sony Corporation
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
+ dmi.product.family: VAIO
+ dmi.product.name: SVS151290X
+ dmi.product.sku: 54520726
+ dmi.product.version: C60BKPK7
+ dmi.sys.vendor: Sony Corporation

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

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  bluetooth peripherals

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for

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

apport information

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  bluetooth peripherals

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  etm2253 F pulseaudio
   /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: Sony Corporation SVS151290X
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS151290X
  dmi.product.sku: 54520726
  dmi.product.version: C60BKPK7
  dmi.sys.vendor: Sony Corporation

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

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

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

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1874713/+attachment/5359473/+files/Lsusb-t.txt

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

Title:
  Instabilities when returning from idle mode and delay when detecting
  bluetooth peripherals

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I 
return to my desk I go back to using my notebook that went into idle mode. In 
addition, I realize that when turning on the computer and entering the Ubuntu 
login interface, there is a relevant delay before the bluetooth peripherals 
(mouse and keyboard) are detected. The time difference is very relevant 
compared to what happened at Eoan.
  Whenever I leave the idle mode, the mouse pointer became slow, with unstable 
and heavy movements. The keyboard also has erratic and strange functioning.
  I have an old sony vaio notebook and use a wireless keyboard and mouse 
communicating directly with the notebook's bluetooth without the need for 
adapters (dongle). The Mouse is an original sony vaio that I bought with the 
notebook, the keyboard, unlike, was recently purchased.
  For now the workaround solution I've been applying is to turn bluetooth off 
and on again, through the gnome configuration panel. In fact, whenever I do 
this, there is again a long delay before the peripherals are detected. I need 
to keep moving the mouse for about 10 to 20 seconds for detection to occur. I 
need to type on the keyboard many times until detection occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 08:46:37 2020
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  etm2253 F pulseaudio
   /dev/snd/pcmC0D0p:   etm2253 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-28 (86 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: Sony Corporation SVS151290X
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare 
sudo tty uuidd video voice
  _MarkForUpload: True
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1021C8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS151290X
  dmi.product.sku: 54520726
  dmi.product.version: C60BKPK7
  dmi.sys.vendor: Sony Corporation

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

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

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