[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16

[You-Sheng Yang]

Error in comment #50 should has been FIX COMMITTED but not yet released.
A new release pending in https://code.launchpad.net/~canonical-hwe-
team/+git/backport-iwlwifi-dkms/+merge/369867 already, so you can get it
from https://code.launchpad.net/~vicamo/+archive/ubuntu/ci-test-only .
Sorry for the inconvenience.

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

Title:
  Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel >
  5.0.0-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05: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/1832087/+subscriptions

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

[Kernel-packages] [Bug 1835614] Re: Touchpad not recognized

[You-Sheng Yang]

@hamdi-ali-1982, it's in the eoan-proposed, so probably you need to do:

  $ echo "deb http://archive.ubuntu.com/ubuntu/ eoan-proposed main restricted 
universe" |\
  sudo tee /etc/apt/sources.list.d/eoan-proposed.list
  $ sudo apt update
  $ sudo apt install linux-image-unsigned-5.0.0-1013-oem-osp1/eoan-proposed
  $ sudo rm /etc/apt/sources.list.d/eoan-proposed.list

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

Title:
  Touchpad not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Ubuntu 19.04 installed on HP Omen 15ce-006nk
  I can not use the touchpad, it seems unrecognized by the OS
  I attached the output of cat /proc/bus/input/devices > devices

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  exo1549 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  6 16:40:01 2019
  InstallationDate: Installed on 2019-07-02 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:58e6 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 15-ce0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=5c61d159-7664-4d88-86c0-b3884c70e5df ro acpi=off i18042.reset quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 838F
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.08:bd09/29/2017:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-ce0xx
  dmi.product.sku: 2HQ17EA#BH4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL

[You-Sheng Yang]

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

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux-firmware source package in Cosmic:
  New
Status in linux-oem-osp1 source package in Cosmic:
  New
Status in linux-firmware source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  New

Bug description:
  [Impact]
  Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
  platforms.

  [Fix]
  Two changes from Intel maintained backport-iwlwifi repository are
  necessary to add device ID/configs to iwlwifi driver.

  [Test]
  Verified on hardware 9462/9560 on IceLake/CometLake platforms.

  [Regression Potential]
  Low. These changes are part of the series to enable 9462/9560 on
  CometLake/IceLake platforms that don't have the support originally.

  = Original Bug Description =

  Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
  1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
  startup with following error messages with kernel v5.2-rc7:

    iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
    iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
    iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
    iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
    iwlwifi :00:14.3: Failed to start RT ucode: -5
    iwlwifi :00:14.3: Collecting data: trigger 16 fired.
    iwlwifi :00:14.3: Firmware not running - cannot dump error
    iwlwifi :00:14.3: Failed to run INIT ucode: -5

  Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
  the moment) with no luck.

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

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

[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL

[You-Sheng Yang]

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

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

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

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

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

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

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux-firmware source package in Cosmic:
  New
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
  platforms.

  [Fix]
  Two changes from Intel maintained backport-iwlwifi repository are
  necessary to add device ID/configs to iwlwifi driver.

  [Test]
  Verified on hardware 9462/9560 on IceLake/CometLake platforms.

  [Regression Potential]
  Low. These changes are part of the series to enable 9462/9560 on
  CometLake/IceLake platforms that don't have the support originally.

  = Original Bug Description =

  Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
  1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
  startup with following error messages with kernel v5.2-rc7:

    iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
    iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
    iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
    iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
    iwlwifi :00:14.3: Failed to start RT ucode: -5
    iwlwifi :00:14.3: Collecting data: trigger 16 fired.
    iwlwifi :00:14.3: Firmware not running - cannot dump error
    iwlwifi :00:14.3: Failed to run INIT ucode: -5

  Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
  the moment) with no luck.

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

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

[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up

[You-Sheng Yang]

Hi, @wjbarid,

In order to determine the right hardware spec on your device, please
attach `sudo lspci -vvnnk` output. It will contains subsystem ID that
can be used to find the right iwlwifi model.

For bluetooth firmware blob name, you should try:

1. clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git and replace the intel/ subdirectory. Something like:

  $ sudo mv /lib/firmware/intel /lib/firmware/intel.orig
  $ sudo cp -a _git_cloned_firmwares_/intel /lib/firmware

2. power off your machine completely and turn it on again *after* 30
seconds or so.

3. capture the dmesg output for Bluetooth|hci:

  $ dmesg | egrep -i 'blue|hci'

You should find something like:

  Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi

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

Title:
  Bluetooth fails with "Bluetooth: hci0: request failed to create LE
  connection: status 0x0c" message with Kernel 4.20 and up

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  This is similar to https://bugs.launchpad.net/bugs/1829737 - however
  the issue was not fixed by linux-firmware 1.173.8 so I was advised to
  log a new bug.

  I have an ASUS ZenBook 14 - UX433FA - which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
  With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.

  I'm running Linux Mint 19.1

  I tried installing linux-firmware 1.173.8, and it didn't seem to help
  - I also downloaded 1.173.9 proposed from here:
  https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
  that also didn't seem to help.

  Both after a cold reboot and a warm reboot I see
  [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

  in my dmesg output.

  Bluetooth works just fine with earlier kernels (however other aspects
  of the laptop like suspend don't work as well, which is why I'm trying
  the newer kernel.

  Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3
  12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | egrep -i 'blue|firm'
  [
  [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing 
all errors
  [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [   14.641146] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
  [   14.642377] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
  [   14.642392] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
  [   14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [   14.675356] Bluetooth: Core ver 2.22
  [   14.675374] Bluetooth: HCI device and connection manager initialized
  [   14.675377] Bluetooth: HCI socket layer initialized
  [   14.675379] Bluetooth: L2CAP socket layer initialized
  [   14.675382] Bluetooth: SCO socket layer initialized
  [   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [   15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.207801] Bluetooth: BNEP filters: protocol multicast
  [   15.207804] Bluetooth: BNEP socket layer initialized
  [   22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   22.040232] Bluetooth: HIDP socket layer initialized
  [   22.042238] input: Logitech K810 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27
  [   22.042996] input: Logitech K810 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28
  [   22.043235] input: Logitech K810 System Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29
  [   22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID 
v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a
  [   29.296700] Bluetooth: RFCOMM TTY layer initialized
  [   29.296705] Bluetooth: RFCOMM socket layer initialized
  [   29.296711] Bluetooth: RFCOMM ver 1.11
  [  217.675736] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  217.709807] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  218.537827] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  218.767709] Bluetooth: hci0: request failed to 

[Kernel-packages] [Bug 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)

[You-Sheng Yang]

** Tags added: verification-done-bionic

** Tags added: verification-done-xenial

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9260)

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID
  devices.

  [Fix]
  Bluetooth FW Build REL0329 or newer is known to have fixed this problem
  on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes
  a firmware backport from upstream commit
  c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix
  conflicts in the WHENCE file.

  [Test Case]
  Verified on hardware platforms with Intel Wireless AC 9260 installed,
  e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel
  and power off the device completely to trigger firmware reload at the
  next boot.

  [Regression Risk]
  Low. Tried following kernels with REL0329 firmware blobs:

* 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.8.0-58-generic: Xenial, even doesn't boot to console
* 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.13.0-45-generic: Xenial
* 4.15.0-54-generic: Xenial, Bionic
* 4.15.0-1043-oem: Xenial, Bionic

  For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't
  work even with current firmware blobs shipped in Xenial's linux-firmware
  REL0186. So overall, these updated blobs are only loaded by hardware
  requires them, and they doesn't bring harm to known working
  configurations.

   Original Bug Description 

  Same problem exactly as encountered with Intel 9560 is also happening
  with Intel 9260.

  Update to linux-firmware 1.173.8 did not fix the problem.

  Everything is working fine when using 4.15 kernel, but not for 4.18+
  5.0+.

  Reference problem:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737

  You-Sheng Yang advised to do this by email and it fixed my issue, so I
  think the 9260 driver would need to be updated in the bionic branch
  (it seems to be updated in newer branches).

  --
  Basically you should try copy the latest firmware (ibt-*) under
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
  , power off the device completely and power on, then have a check on
  bluetooth pairing.
  --

  Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27
  04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  OS: Linux Mint 19.1 Tessa x86_64
  Host: 81JB Lenovo ideapad 730S-13IWL
  Wifi/Bluetooth card is Intel 9260

  @:/etc$ dmesg | egrep -i 'blue|firm'
  [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.379392] [Firmware Bug]: Invalid critical threshold (0)
  [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [6.337749] Bluetooth: Core ver 2.22
  [6.337767] Bluetooth: HCI device and connection manager initialized
  [6.337770] Bluetooth: HCI socket layer initialized
  [6.337773] Bluetooth: L2CAP socket layer initialized
  [6.33] Bluetooth: SCO socket layer initialized
  [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.309938] Bluetooth: BNEP filters: protocol multicast
  [7.309943] Bluetooth: BNEP socket layer initialized
  [   17.197268] Bluetooth: RFCOMM TTY layer initialized
  [   17.197275] Bluetooth: RFCOMM socket layer initialized
  [   17.197284] Bluetooth: RFCOMM ver 1.11
  [  104.453159] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.509148] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.551340] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.589338] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.623323] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c

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

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

[Kernel-packages] [Bug 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560

[You-Sheng Yang]

** Tags added: verification-done-disco

** Tags added: verification-done-bionic

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

Title:
  Missing bluetooth firmware for Intel Wireless-AC 9462/9560

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  In Progress

Bug description:
  [Impact]
  Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to
  be enabled.

  [Fix]
  Backport newly released firmware blobs from linux-firmware. This will
  also requires minor change to the WHENCE file to resolve cherry-pick
  conflicts. B/C/D would requires this explicitly and Eoan should be
  rebased onto linux-firmware master branch HEAD as usual.

  [Test Case]
  Verified with hardware platforms with corresponding devices. Completely
  power off and power on to trigger firmware reload, check from dmesg to
  see if Bluetooth firmware has been correctly loaded.

  [Regression Risk]
  Low. This adds new binary firmware blobs that are only loaded by
  targeting hardware.

  == original bug description ==

  On systems with Intel Wireless-AC 9462/9560 cards, following failed-
  to-load-firmware kernel messages found:

    bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi
  failed with error -2

  See also Bug #1833065 for wireless firmware & driver fix.

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

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

[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL

[You-Sheng Yang]

For linux-firmware part, we'll only need ibt-19-32-0.{sfi,ddc} for 9462
on ICL, which has been committed as
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=d52556e4592e64023157a83fb0f483661f23ac0e. This
should be backported to B/C/D, and let Eoan to be rebased on latest
upstream HEAD.

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  In Progress
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  In Progress
Status in linux-oem-osp1 source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
  platforms.

  [Fix]
  Two changes from Intel maintained backport-iwlwifi repository are
  necessary to add device ID/configs to iwlwifi driver.

  [Test]
  Verified on hardware 9462/9560 on IceLake/CometLake platforms.

  [Regression Potential]
  Low. These changes are part of the series to enable 9462/9560 on
  CometLake/IceLake platforms that don't have the support originally.

  = Original Bug Description =

  Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
  1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
  startup with following error messages with kernel v5.2-rc7:

    iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
    iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
    iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
    iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
    iwlwifi :00:14.3: Failed to start RT ucode: -5
    iwlwifi :00:14.3: Collecting data: trigger 16 fired.
    iwlwifi :00:14.3: Firmware not running - cannot dump error
    iwlwifi :00:14.3: Failed to run INIT ucode: -5

  Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
  the moment) with no luck.

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

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

[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL

[You-Sheng Yang]

https://lists.ubuntu.com/archives/kernel-team/2019-July/102175.html

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  In Progress
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  In Progress
Status in linux-oem-osp1 source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
  platforms.

  [Fix]
  Two changes from Intel maintained backport-iwlwifi repository are
  necessary to add device ID/configs to iwlwifi driver.

  [Test]
  Verified on hardware 9462/9560 on IceLake/CometLake platforms.

  [Regression Potential]
  Low. These changes are part of the series to enable 9462/9560 on
  CometLake/IceLake platforms that don't have the support originally.

  = Original Bug Description =

  Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
  1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
  startup with following error messages with kernel v5.2-rc7:

    iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
    iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
    iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
    iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
    iwlwifi :00:14.3: Failed to start RT ucode: -5
    iwlwifi :00:14.3: Collecting data: trigger 16 fired.
    iwlwifi :00:14.3: Firmware not running - cannot dump error
    iwlwifi :00:14.3: Failed to run INIT ucode: -5

  Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
  the moment) with no luck.

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

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

[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up

[You-Sheng Yang]

Hi @wjbaird, thank you for the logs. From your lspci output, we should
be able to confirm it's a "Intel(R) Dual Band Wireless AC 9560"[1], and
we should have the support in linux-oem-osp1 kernel since bug 1833065.
For -generic kernel flavors, the backport-iwlwifi-dkms in ppa:canonical-
hwe-team/pc-oem-dkms[2] is required, and we're working on publish it to
ubuntu archive.

For bluetooth, unfortunately we still have no luck to retrieve the
firmware name from dmesg. I met this before. All I know is that it takes
a complete power off, wait for a period, power on and you may find the
line that gives firmware name in this first boot. With the blob firmware
name, we may begin to find out which revision of that given blob works
for you. If the latest one from linux-firmware git repository[3] still
doesn't work well, then we'll probably need to file a bug to Intel
instead.

[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/tree/drivers/net/wireless/intel/iwlwifi/cfg/9000.c#n218
[2]: https://code.launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-dkms
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

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

Title:
  Bluetooth fails with "Bluetooth: hci0: request failed to create LE
  connection: status 0x0c" message with Kernel 4.20 and up

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This is similar to https://bugs.launchpad.net/bugs/1829737 - however
  the issue was not fixed by linux-firmware 1.173.8 so I was advised to
  log a new bug.

  I have an ASUS ZenBook 14 - UX433FA - which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
  With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.

  I'm running Linux Mint 19.1

  I tried installing linux-firmware 1.173.8, and it didn't seem to help
  - I also downloaded 1.173.9 proposed from here:
  https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
  that also didn't seem to help.

  Both after a cold reboot and a warm reboot I see
  [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

  in my dmesg output.

  Bluetooth works just fine with earlier kernels (however other aspects
  of the laptop like suspend don't work as well, which is why I'm trying
  the newer kernel.

  Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3
  12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | egrep -i 'blue|firm'
  [
  [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing 
all errors
  [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [   14.641146] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
  [   14.642377] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
  [   14.642392] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
  [   14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [   14.675356] Bluetooth: Core ver 2.22
  [   14.675374] Bluetooth: HCI device and connection manager initialized
  [   14.675377] Bluetooth: HCI socket layer initialized
  [   14.675379] Bluetooth: L2CAP socket layer initialized
  [   14.675382] Bluetooth: SCO socket layer initialized
  [   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [   15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.207801] Bluetooth: BNEP filters: protocol multicast
  [   15.207804] Bluetooth: BNEP socket layer initialized
  [   22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   22.040232] Bluetooth: HIDP socket layer initialized
  [   22.042238] input: Logitech K810 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27
  [   22.042996] input: Logitech K810 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28
  [   22.043235] input: Logitech K810 System Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29
  [   22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID 
v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a
  [   29.296700] Bluetooth: RFCOMM TTY layer initialize

[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up

[You-Sheng Yang]

Ha, thank you. That's what I'm looking for.

So now we have the firmware name, and the next step would be to find out
which version will work for you. And so far we have:

  * Bionic: REL0440
  * Cosmic: REL0329
  * Disco: REL0420
  * korg/master: REL0472

Since you mentioned neither linux-firmware version 1.173.8 nor 1.173.9
would work for you, which was last updated to REL0440 at bug 1829737 for
the same symptom on also 9560/9462 devices, maybe that's one 9560
variant that we don't have. Then I would like ask you for a favor, to
confirm which version(s) works for you:

  * REL0450: https://git.kernel.org/pub/scm/linux/kernel/git/firmware
/linux-
firmware.git/plain/intel/ibt-17-16-1.sfi?id=abb7cb6465ddaa64eab9ee487024b9aaee780f4b

and/or,

  * REL0472: https://git.kernel.org/pub/scm/linux/kernel/git/firmware
/linux-
firmware.git/plain/intel/ibt-17-16-1.sfi?id=a5ee41544a092e35fb6b8324687e8a32488f6e26

And please also give me the md5sum of
/lib/firmware/intel/ibt-17-16-1.sfi when installed to your system and
that fixes this problem.

>From your comment #9 I suppose at least REL0472 should work, but I also
need to know if REL0450 is sufficient enough. Thank you.

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

Title:
  Bluetooth fails with "Bluetooth: hci0: request failed to create LE
  connection: status 0x0c" message with Kernel 4.20 and up

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This is similar to https://bugs.launchpad.net/bugs/1829737 - however
  the issue was not fixed by linux-firmware 1.173.8 so I was advised to
  log a new bug.

  I have an ASUS ZenBook 14 - UX433FA - which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
  With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.

  I'm running Linux Mint 19.1

  I tried installing linux-firmware 1.173.8, and it didn't seem to help
  - I also downloaded 1.173.9 proposed from here:
  https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
  that also didn't seem to help.

  Both after a cold reboot and a warm reboot I see
  [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

  in my dmesg output.

  Bluetooth works just fine with earlier kernels (however other aspects
  of the laptop like suspend don't work as well, which is why I'm trying
  the newer kernel.

  Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3
  12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | egrep -i 'blue|firm'
  [
  [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing 
all errors
  [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [   14.641146] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
  [   14.642377] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
  [   14.642392] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
  [   14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [   14.675356] Bluetooth: Core ver 2.22
  [   14.675374] Bluetooth: HCI device and connection manager initialized
  [   14.675377] Bluetooth: HCI socket layer initialized
  [   14.675379] Bluetooth: L2CAP socket layer initialized
  [   14.675382] Bluetooth: SCO socket layer initialized
  [   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [   15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.207801] Bluetooth: BNEP filters: protocol multicast
  [   15.207804] Bluetooth: BNEP socket layer initialized
  [   22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   22.040232] Bluetooth: HIDP socket layer initialized
  [   22.042238] input: Logitech K810 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27
  [   22.042996] input: Logitech K810 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28
  [   22.043235] input: Logitech K810 System Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29
  [   22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID 
v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a
  [   29.296700] Bluetooth: RFCOMM TTY layer initialize

[Kernel-packages] [Bug 1836411] Re: Bluetooth: hci0: inquiry failed: status 0x0c

[You-Sheng Yang]

Hi @ejsc,

It seems your CurrentDmesg.txt contains only messages from snap/htop, so
I can't really have some basic information about your Bluetooth module.
Would you redo the dmesg capturing by:

  1. power off the machine completely, remove power cable or so,
  2. wait for 1 minute
  3. power on
  4. do `sudo dmesg | tee dmesg.$(uname -r)` and attach the new log

If your new dump is still filled with snap/htop garbages, please try to
fix/remove that first.

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

Title:
  Bluetooth: hci0: inquiry failed: status 0x0c

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [   64.142848] Bluetooth: hci0: inquiry failed: status 0x0c

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 15:03:07 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  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.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23: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/ubuntu/+source/linux/+bug/1836411/+subscriptions

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

[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16

[You-Sheng Yang]

@phil995511, bug 1830961 fails recent kernel build, so v5.2 is not
available. And, actually backport-iwlwifi-dkms has all the mandatory
changes to enable iwlwifi devices, while mainline kernel may not. So I
would still recommend you to use backport-iwlwifi-dkms instead.

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

Title:
  Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel >
  5.0.0-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05: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/1832087/+subscriptions

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

[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL

[You-Sheng Yang]

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

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Won't Fix
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
  platforms.

  [Fix]
  Two changes from Intel maintained backport-iwlwifi repository are
  necessary to add device ID/configs to iwlwifi driver.

  [Test]
  Verified on hardware 9462/9560 on IceLake/CometLake platforms.

  [Regression Potential]
  Low. These changes are part of the series to enable 9462/9560 on
  CometLake/IceLake platforms that don't have the support originally.

  = Original Bug Description =

  Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
  1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
  startup with following error messages with kernel v5.2-rc7:

    iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
    iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
    iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
    iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
    iwlwifi :00:14.3: Failed to start RT ucode: -5
    iwlwifi :00:14.3: Collecting data: trigger 16 fired.
    iwlwifi :00:14.3: Firmware not running - cannot dump error
    iwlwifi :00:14.3: Failed to run INIT ucode: -5

  Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
  the moment) with no luck.

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

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

[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up

[You-Sheng Yang]

Thank you, Warren. So I think I can begin to send a patch to the series
don't have REL0450 ibt-17-16-1.sfi, so that owners of the same devices
don't have to manually download again.

For polluted /lib/firmware, I think I would restore what it was and copy
only ibt-17-16-1.sfi to keep Bluetooth working. Because I myself run apt
updates everyday, and I don't want to break any installation script as
possible. Besides, yes, keep things simple would also be nice.

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

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

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

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

** Changed in: linux-firmware (Ubuntu Disco)
   Status: New => In Progress

** Summary changed:

- Bluetooth fails with "Bluetooth: hci0: request failed to create LE 
connection: status 0x0c" message with Kernel 4.20 and up
+ Bluetooth fails with "Bluetooth: hci0: request failed to create LE 
connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034]

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

Title:
  Bluetooth fails with "Bluetooth: hci0: request failed to create LE
  connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034]

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  In Progress

Bug description:
  This is similar to https://bugs.launchpad.net/bugs/1829737 - however
  the issue was not fixed by linux-firmware 1.173.8 so I was advised to
  log a new bug.

  I have an ASUS ZenBook 14 - UX433FA - which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
  With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.

  I'm running Linux Mint 19.1

  I tried installing linux-firmware 1.173.8, and it didn't seem to help
  - I also downloaded 1.173.9 proposed from here:
  https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
  that also didn't seem to help.

  Both after a cold reboot and a warm reboot I see
  [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

  in my dmesg output.

  Bluetooth works just fine with earlier kernels (however other aspects
  of the laptop like suspend don't work as well, which is why I'm trying
  the newer kernel.

  Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3
  12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | egrep -i 'blue|firm'
  [
  [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing 
all errors
  [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [   14.641146] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
  [   14.642377] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
  [   14.642392] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
  [   14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [   14.675356] Bluetooth: Core ver 2.22
  [   14.675374] Bluetooth: HCI device and connection manager initialized
  [   14.675377] Bluetooth: HCI socket layer initialized
  [   14.675379] Bluetooth: L2CAP socket layer initialized
  [   14.675382] Bluetooth: SCO socket layer initialized
  [   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [   15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.207801] Bluetooth: BNEP filters: protocol multicast
  [   15.207804] Bluetooth: BNEP socket layer initialized
  [   22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   22.040232] Bluetooth: HIDP socket layer initialized
  [   22.042238] input: Logitech K810 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1

[Kernel-packages] [Bug 1836467] Re: Bluetooth fails with "Bluetooth: hci0: request failed to create LE connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034]

[You-Sheng Yang]

https://lists.ubuntu.com/archives/kernel-team/2019-July/102298.html
https://lists.ubuntu.com/archives/kernel-team/2019-July/102299.html

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to
+ pair BT LE HID devices on recent (>= 4.19) kernel.
+ 
+ [Fix]
+ Bluetooth firmware REL0450 or newer is required to fix this issue.
+ 
+ [Test Case]
+ Install new firmware blob to /lib/firmware/intel, shutdown the machine
+ completely and wait for a couple minutes to trigger firmware reloading
+ at the next boot. Then perform Bluetooth LE HID devices pairing to
+ verify if the proposed fw fixes this issue.
+ 
+ [Regression Risk]
+ Low. This affects only sub models of Intel JeffersonPeak Bluetooth chip
+ series using these firmware blobs.
+ 
+ == Original Bug Description ==
+ 
  This is similar to https://bugs.launchpad.net/bugs/1829737 - however the
  issue was not fixed by linux-firmware 1.173.8 so I was advised to log a
  new bug.
  
  I have an ASUS ZenBook 14 - UX433FA - which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
  With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.
  
  I'm running Linux Mint 19.1
  
  I tried installing linux-firmware 1.173.8, and it didn't seem to help -
  I also downloaded 1.173.9 proposed from here:
  https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
  that also didn't seem to help.
  
  Both after a cold reboot and a warm reboot I see
  [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  
  in my dmesg output.
  
  Bluetooth works just fine with earlier kernels (however other aspects of
  the laptop like suspend don't work as well, which is why I'm trying the
  newer kernel.
  
  Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3
  12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  
  dmesg | egrep -i 'blue|firm'
  [
  [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing 
all errors
  [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [   14.641146] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
  [   14.642377] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
  [   14.642392] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
  [   14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [   14.675356] Bluetooth: Core ver 2.22
  [   14.675374] Bluetooth: HCI device and connection manager initialized
  [   14.675377] Bluetooth: HCI socket layer initialized
  [   14.675379] Bluetooth: L2CAP socket layer initialized
  [   14.675382] Bluetooth: SCO socket layer initialized
  [   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [   15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.207801] Bluetooth: BNEP filters: protocol multicast
  [   15.207804] Bluetooth: BNEP socket layer initialized
  [   22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   22.040232] Bluetooth: HIDP socket layer initialized
  [   22.042238] input: Logitech K810 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27
  [   22.042996] input: Logitech K810 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28
  [   22.043235] input: Logitech K810 System Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input29
  [   22.043426] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID 
v12.02 Keyboard [Logitech K810] on 00:bb:60:09:27:1a
  [   29.296700] Bluetooth: RFCOMM TTY layer initialized
  [   29.296705] Bluetooth: RFCOMM socket layer initialized
  [   29.296711] Bluetooth: RFCOMM ver 1.11
  [  217.675736] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  217.709807] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  218.537827] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  218.767709] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  220.244821] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  
  If there are any other debugging things to try, or info you need, let me
  know...

-- 
You received this bug notification because you

[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor

[You-Sheng Yang]

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

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

** Changed in: linux (Ubuntu Cosmic)
     Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

** Changed in: linux-oem (Ubuntu Bionic)
     Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
   Status: Fix Committed

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

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

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

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

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  System does not auto detect disconnection of external monitor

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  In Progress
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Won't Fix
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

  [Fix]
  two commits from upstream drm-intel-next-queued branch

  [Test case]
  see "steps to reproduce"

  [Regression potential]
  still possible, but for the distro only Eoan will get it. OEM kernels will 
get tested on systems that get it.

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

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

[Kernel-packages] [Bug 1820243] Re: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock

[You-Sheng Yang]

Hi, could you try suspend again with dock connected and paste dmesg of
the last boot. A nvidia xid error 69 was found in your attachments, but
I'm not sure if it's related because it contains log of multiple
boot/suspend.

It would also be helpful if you may enable GDM debug messages (if in
used) and paste syslog messages across that suspend/resume. Before
uploading, please make sure there is no credential information included
accidentally.

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

Title:
  linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 (linux-image-4.18.0-16-generic)
  ThinkPad 460P
  Intel i7-6700HQ
  Nvidia GTX940MX (nvidia 415 drivers)

  When using with dock, attached monitor is not detected, laptop monitor 
remains blank.
  Laptop freezes until I detach it from the UltraDock again.
  Requires a reboot with the UltraDock attached to make it working.

  It worked in the past since 4.18 with the Laptop booted with the
  UltraDock and detach ad attach the laptop again.

  This time I detached the Laptop, worked a few days without the
  UltraDock (used Standby over night) and tried to attach it again.

  Maybe it happens because I use HWE now.

  But the errors in dmesg and logcat are looking like my bugreport for kernel 
4.15 where the UltraDock didn't worked.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin17549 F pulseaudio
   /dev/snd/pcmC0D0p:   martin17549 F...m pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (236 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
   Bus 001 Device 007: ID 04f2:b541 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

[You-Sheng Yang]

Firmware landed in upstream
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=1b3456c3360be6c6333ba0350316500afa9b2524

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

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  New

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

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

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

[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

[You-Sheng Yang]

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
   Status: In Progress

** Also affects: linux-firmware (Ubuntu Disco)
   Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
   Status: New

** No longer affects: linux (Ubuntu Disco)

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

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

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

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  In Progress
Status in linux-firmware source package in Disco:
  In Progress

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

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

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

[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

[You-Sheng Yang]

Most of the time you need only "linux-image-4.9.0+_4.9.0+-1_amd64.deb".
But if you have also some dkms based modules installed, you may want to
install linux-headers-* as well.

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

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

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

[Kernel-packages] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]

[You-Sheng Yang]

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

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

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

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

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

Title:
  Intel I210 Ethernet card not working after hotplug [8086:1533]

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  Summary:
  Intel I210 Ethernet card not working after hotplug

  Steps to reproduce:
  1. Power on system with ethernet cable on Intel I210
  2. Check ethernet is workable
  3. Unplug then plug the ethernet cable

  Expected result:
  Intel I210 Ethernet card is working, e.g. IP address acquired automatically 
if configured as DHCP.

  Actual result:
  Intel I210 Ethernet card not working after hotplug. dmesg has following error 
messages instead:
  [ 16.464321] [ cut here ]
  [ 16.464326] PCI PM: State of device not saved by 
igb_runtime_suspend+0x0/0x90 [igb]
  [ 16.464334] WARNING: CPU: 2 PID: 49 at 
/build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 
pci_pm_runtime_suspend+0x175/0x180
  [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel 
irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep 
ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 
snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi 
intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas 
snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd 
sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci 
intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
  [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect 
i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi 
video
  [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem 
#37-Ubuntu
  [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 
01/14/2019
  [ 16.464369] Workqueue: pm pm_runtime_work
  [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180
  [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282
  [ 16.464372] RAX:  RBX: 8a2557aee0a0 RCX: 0006
  [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490
  [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373
  [ 16.464373] R10:  R11:  R12: 
  [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: 
  [ 16.464374] FS: () GS:8a257c48() 
knlGS:
  [ 16.464375] CS: 0010 DS:  ES:  CR0: 80050033
  [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0
  [ 16.464376] DR0:  DR1:  DR2: 
  [ 16.464376] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 16.464376] Call Trace:
  [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464380] __rpm_callback+0xca/0x210
  [ 16.464381] ? __switch_to_asm+0x40/0x70
  [ 16.464382] ? __switch_to_asm+0x34/0x70
  [ 16.464382] rpm_callback+0x59/0x80
  [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464384] rpm_suspend+0x137/0x640
  [ 16.464385] ? __switch_to_asm+0x40/0x70
  [ 16.464386] pm_runtime_work+0x81/0xa0
  [ 16.464388] process_one_work+0x1de/0x410
  [ 16.464389] worker_thread+0x32/0x410
  [ 16.464390] kthread+0x121/0x140
  [ 16.464391] ? process_one_work+0x410/0x410
  [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70
  [ 16.464392] ret_from_fork+0x35/0x40
  [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b 
b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b 
e9 fd fe ff ff 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53
  [ 16.464408] ---[ end trace 97e5f2cf651b62e6 ]---

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

[Kernel-packages] [Bug 1824472] Re: Brightness issue

[You-Sheng Yang]

Hi, could you also upload a copy of syslog booted without
"acpi_backlight=vendor"?

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

Title:
  Brightness issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell inspiron G3.
  I am not able to change the screen brightness. I tried many solutions, but 
none worked.

  1. I tried changing acpi_backlight = vendor:
  Now this does solve but it creates another problem. Because for my laptop to 
shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset.

  2. I tried installing applications:
  But when I run these applications it show "No backlights were found on the 
system"

  Kindly address the issue and provide a solution. It is causing great
  trouble.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rishita1806 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 11:55:50 2019
  HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090
  InstallationDate: Installed on 2019-02-28 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G3 3579
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 05K0D2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1824472] Re: Brightness issue

[You-Sheng Yang]

Could you also try use `nouveau.modeset=0` instead of nomodeset and
remove acpi_backlight as well? The full kernel parameters would then
become:

  BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic
root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash
nouveau.modeset=0 vt.handoff=1

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

Title:
  Brightness issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell inspiron G3.
  I am not able to change the screen brightness. I tried many solutions, but 
none worked.

  1. I tried changing acpi_backlight = vendor:
  Now this does solve but it creates another problem. Because for my laptop to 
shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset.

  2. I tried installing applications:
  But when I run these applications it show "No backlights were found on the 
system"

  Kindly address the issue and provide a solution. It is causing great
  trouble.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rishita1806 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 11:55:50 2019
  HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090
  InstallationDate: Installed on 2019-02-28 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G3 3579
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 05K0D2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1824472] Re: Unable to set brightness on Dell G3 3579 with nomodeset

[You-Sheng Yang]

** Summary changed:

- Brightness issue
+ Unable to set brightness on Dell G3 3579 with nomodeset

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

Title:
  Unable to set brightness on Dell G3 3579 with nomodeset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell inspiron G3.
  I am not able to change the screen brightness. I tried many solutions, but 
none worked.

  1. I tried changing acpi_backlight = vendor:
  Now this does solve but it creates another problem. Because for my laptop to 
shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset.

  2. I tried installing applications:
  But when I run these applications it show "No backlights were found on the 
system"

  Kindly address the issue and provide a solution. It is causing great
  trouble.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rishita1806 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 11:55:50 2019
  HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090
  InstallationDate: Installed on 2019-02-28 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G3 3579
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 05K0D2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

[You-Sheng Yang]

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

** This bug has been marked a duplicate of bug 1823150
   Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version 
information failed (-110))

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

Title:
  Intel 8260 Bluetooth non-functioning, command timeouts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to use the Gigabyte Z170N-Gaming 5, with Intel 8260
  wifi+bluetooth, bluetooth does not function.

  Dmesg shows:
  [   13.051985] Bluetooth: Core ver 2.22
  [   13.051996] Bluetooth: HCI device and connection manager initialized
  [   13.051998] Bluetooth: HCI socket layer initialized
  [   13.051999] Bluetooth: L2CAP socket layer initialized
  [   13.052031] Bluetooth: SCO socket layer initialized
  [   15.100035] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   15.100036] Bluetooth: hci0: command 0xfc05 tx timeout
  [   15.100270] Bluetooth: hci0: Hardware error 0x08
  [   15.978374] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.978375] Bluetooth: BNEP filters: protocol multicast
  [   15.978377] Bluetooth: BNEP socket layer initialized
  [   17.116013] Bluetooth: hci0: command 0x0c03 tx timeout
  [   25.308049] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   27.324270] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   27.324275] Bluetooth: hci0: command 0xfc05 tx timeout
  [   27.324612] Bluetooth: hci0: Hardware error 0x08
  [   29.340020] Bluetooth: hci0: command 0x0c03 tx timeout
  [   37.340274] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   39.356059] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   39.356071] Bluetooth: hci0: command 0xfc05 tx timeout
  [   39.356499] Bluetooth: hci0: Hardware error 0x08

  
  I have tried the latest intel firmwares from mainline based on:
  https://bugzilla.kernel.org/show_bug.cgi?id=197147#c81
  and
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

  with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fmstrat2489 F pulseaudio
   /dev/snd/controlC0:  fmstrat2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 09:14:54 2019
  InstallationDate: Installed on 2019-01-20 (83 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Z170N-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=16462d84-0501-4b74-aeff-7765953b648f ro modprobe.blacklist=nouveau 
quiet splash intel_iommu=on hugepages=4096 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170N-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/25/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170N-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170N-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170N-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

[You-Sheng Yang]

This was previously marked as duplicate of bug 1823150, which was
actually resolved by upgrading BIOS, not the linux-firmware deb. Maybe
you'd also like to do the same? From GigaByte's support site [1], there
is already several new revisions available.

[1]: https://www.gigabyte.com/Motherboard/GA-Z170N-Gaming-5-rev-10
#support-dl-bios

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

Title:
  Intel 8260 Bluetooth non-functioning, command timeouts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to use the Gigabyte Z170N-Gaming 5, with Intel 8260
  wifi+bluetooth, bluetooth does not function.

  Dmesg shows:
  [   13.051985] Bluetooth: Core ver 2.22
  [   13.051996] Bluetooth: HCI device and connection manager initialized
  [   13.051998] Bluetooth: HCI socket layer initialized
  [   13.051999] Bluetooth: L2CAP socket layer initialized
  [   13.052031] Bluetooth: SCO socket layer initialized
  [   15.100035] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   15.100036] Bluetooth: hci0: command 0xfc05 tx timeout
  [   15.100270] Bluetooth: hci0: Hardware error 0x08
  [   15.978374] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.978375] Bluetooth: BNEP filters: protocol multicast
  [   15.978377] Bluetooth: BNEP socket layer initialized
  [   17.116013] Bluetooth: hci0: command 0x0c03 tx timeout
  [   25.308049] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   27.324270] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   27.324275] Bluetooth: hci0: command 0xfc05 tx timeout
  [   27.324612] Bluetooth: hci0: Hardware error 0x08
  [   29.340020] Bluetooth: hci0: command 0x0c03 tx timeout
  [   37.340274] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   39.356059] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   39.356071] Bluetooth: hci0: command 0xfc05 tx timeout
  [   39.356499] Bluetooth: hci0: Hardware error 0x08

  
  I have tried the latest intel firmwares from mainline based on:
  https://bugzilla.kernel.org/show_bug.cgi?id=197147#c81
  and
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

  with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fmstrat2489 F pulseaudio
   /dev/snd/controlC0:  fmstrat2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 09:14:54 2019
  InstallationDate: Installed on 2019-01-20 (83 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Z170N-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=16462d84-0501-4b74-aeff-7765953b648f ro modprobe.blacklist=nouveau 
quiet splash intel_iommu=on hugepages=4096 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170N-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/25/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170N-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170N-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170N-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works)

[You-Sheng Yang]

How about 4.4.0-144? Would it help to narrow down the issue a bit more?

https://launchpad.net/ubuntu/+source/linux/4.4.0-144.170

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145
  (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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

[Kernel-packages] [Bug 1825074] [NEW] amdgpu resume failure: failed to allocate wb slot

[You-Sheng Yang]

Public bug reported:

[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test failed 
(-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 9202, 
serial_number = 1, manufacture_week = 29, manufacture_year = 18, display_name = 
92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 64bit 
pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 0x0020 
64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 0x0020 
64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
[ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!

[Reproduce Steps]
1. apt-get install -y fwts
2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60

[Results]
Expected: pass the S3 stress test
Actual: system hung at 112nd S3

[Additional Information]
Kernel Version: 4.15.0-1035-oem
GPU: AMD RX550 (OPGA14) 1002:699f

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Incomplete

** Attachment added: "kernel log"
   
https://bugs.launchpad.net/bugs/1825074/+attachment/5256441/+files/kern.txt.gz

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

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplet

[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

[You-Sheng Yang]

This only affects Bionic as Xenial doesn't come with the two commits and
Cosmic/Disco have already included the 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/1825074

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!

  [Reproduce Steps]
  1. apt-get install -y fwts
  2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60

  [Results]
  Expected: pass the S3 stress test
  Actual: system hung at 112nd S3

  [Additional Information]
  Kernel Version: 4.15.0-1035-oem
  GPU: AMD RX550 (OPGA14) 1002:699f

To manage notifications about this

[Kernel-packages] [Bug 1801359] Re: Notebook lid blank after booting with lid closed

[You-Sheng Yang]

I think there is issues in handling such case in gnome-shell/bionic
itself. With an Intel card only platform, one may login via gdm
displayed on the external monitor. But when logged in, the built-in
display will have the content of a second one, and the external monitor
will be blank. Then if you unplug HDMI and replug in, the external
monitor will have the content of a second one, but the built-in display
will be off.

So there might be an hardware/nvidia/i915 issue in `edp_panel_vdd_on()`,
but upgrade the system to Disco/Eoan is still a must to receive new
fixes for related behaviors.

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

Title:
  Notebook lid blank after booting with lid closed

Status in linux package in Ubuntu:
  In Progress

Bug description:
  When using a external monitor on a Dell Precision 5520 Notebook and
  booting with lid closed ...

  1. the lid stays blank when later opening it (happens on Ubuntu 18.10
  and 18.04)

  2. and login using a Xorg is not possible (a login-loop happens on
  Ubuntu 18.10)

  Digging in sysfs I saw that /sys/class/backlight/intel_backlight/bl_power 
  0 (and manually changable) when booted with lid open
  but 4 (and unchangable) when booted with lid closed. 

  Other (eg. power) entires under /sys/class/backlight/intel_backlight
  can't be changed or don't help and changing
  /sys/class/backlight/intel_backlight/brightness don't help as well.

  There is neither a difference in dmesg output (except some additional
  "enabling Extended Tags" when booting with lid open) nor any
  difference in modules loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mm 1720 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 13:38:44 2018
  InstallationDate: Installed on 2018-10-19 (13 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 005: ID 0c45:6713 Microdia 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz 
root=UUID=31b59337-0e21-48d0-bede-155475fc0c7b ro rootflags=subvol=@ rootwait 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

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

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

I've also tried following kernel versions and they are all affected:

* v5.2.8 mainline
* v5.3-rc1 mainline
* v5.3-rc2 mainline
* v5.3-rc3 mainline
* v5.3-rc4 mainline
* drm-intel-next 2019-07-31 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2019-07-31/

** Description changed:

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on IceLake
  platforms.
  
  Right after GDM is login screen is rendered, there might be a thin strap
  of corrupted image at top of the display for a short while. Like f-d-o
  bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times. Etc.
+ 
+ Known work-around so far is to append kernel boot param
+ "i915.enable_fbc=0".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840239] [NEW] tsc marked unstable after entered PC10 on Intel CoffeeLake

[You-Sheng Yang]

Public bug reported:

This is actually a duplicate to
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal
tracking.

[Overview]

On Intel CoffeeLake it's observed tsc is always marked unstable after
turning off screen and let cpu enter idle state Package C10(PC10), and
then clock source is switched to hpet. Following messages are printed in
dmesg when this occurs:

  [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

  [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd mask: 

  [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
  [ 115.454675] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
  [ 115.455825] clocksource: Switched to clocksource hpet

[Step to reproduce]

1. use `powertop` to observe if CPU has ever enter PC10,
2. issue `xset dpms force off` to turn off screen and idle for some minutes,
3. check dmesg for above tsc marked unstable messages

[Actual Results]

TSC marked unstable and clock source switched to HPET.

[Expected Results]

TSC remains the clock source across the PC10 event.

[Build Date & Hardware]

This is reproducible on kernel version 4.14 through 5.1-rc2. Order
kernel versions are not tested.

[Additional Information]

This was first found on Ubuntu (all versions) that system doesn't go
suspend after stayed idle for 20 minutes. Clock source was switched to
HPET, the system time is no correctly synced with reality so that the
system doesn't consider it has stayed idle long enough to begin suspend
process.

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


** Tags: tsc-unstable

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

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in linux package in Ubuntu:
  New

Bug description:
  This is actually a duplicate to
  https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for
  internal tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

[ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

[ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
[ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
[ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
[ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
[ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

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

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

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

[You-Sheng Yang]

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

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

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is actually a duplicate to
  https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for
  internal tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

[ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

[ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
[ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
[ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
[ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
[ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

Proposed patch in addition to
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=396dd8143bdd94bd1c358a228a631c8c895a1126

** Bug watch added: freedesktop.org Bugzilla #111484
   https://bugs.freedesktop.org/show_bug.cgi?id=111484

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=111484
   Importance: Unknown
   Status: Unknown

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Patch added: 
"0001-drm-i915-fbc-disable-framebuffer-compression-on-IceL.patch"
   
https://bugs.launchpad.net/linux/+bug/1840236/+attachment/5284634/+files/0001-drm-i915-fbc-disable-framebuffer-compression-on-IceL.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/1840236

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1836993/disable-framebuffer-compression-on-IceLake/oem-osp1-bionic
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1836993/disable-framebuffer-compression-on-IceLake/oem-bionic
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1836993/disable-framebuffer-compression-on-IceLake/bionic
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1836993/disable-framebuffer-compression-on-IceLake/disco
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1836993/disable-framebuffer-compression-on-IceLake/eoan

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
   Status: In Progress

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

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

** Also affects: linux-oem-osp1 (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/1840236

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

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

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

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

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1840236] Re: Horizontal corrupted line at top of screen caused by framebuffer compression

[You-Sheng Yang]

https://lists.ubuntu.com/archives/kernel-team/2019-August/103419.html Eoan
https://lists.ubuntu.com/archives/kernel-team/2019-August/103421.html 
linux-oem-osp1/bionic

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

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ On IceLake platforms there might be a thin, horizon strap of corruption
+ image at the top of screen randomly after some series of window
+ operations and disappears within a second or so. This is found on
+ multiple platforms and is quite annonying that results in bad user
+ experience.
+ 
+ [Fix]
+ The upstream bug has been filed for previous platforms, e.g. GeminiLake
+ for an year or so, still working in progress, and so far this only known
+ work-around is to turn off framebuffer compression on affected platforms.
+ 
+ [Test Case]
+ The most easy way is to observe if such corruption appears during the
+ transition from GDM to gnome-shell.
+ 
+ [Regression Risk]
+ Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
+ and has been backported to B/D.
+ 
+ === Original Description ==
+ 
  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on IceLake
  platforms.
  
  Right after GDM is login screen is rendered, there might be a thin strap
  of corrupted image at top of the display for a short while. Like f-d-o
  bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times. Etc.
  
  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:41:01 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X14
  InstallationDate: Installed on 2019-08-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-signed-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Horizontal corrupted line at top of screen caused by framebuffer
  compression

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  New

Bug description:
  SRU Justification:

  [Impact]
  On IceLake platforms there might be a thin, horizon strap of corruption
  image at the top of screen randomly after some series of window
  operations and disappears within a second or so. This is found on
  multiple platforms and is quite annonying that results in bad user
  experience.

  [Fix]
  The upstream bug has been filed for previous platforms, e.g. GeminiLake
  for an year or so, still working in progress, and so far this only known
  work-around is to turn off framebuffer compression on affected platforms.

  [Test Case]
  The most easy way is to observe if such corruption appears during the
  transition from GDM to gnome-shell.

  [Regression Risk]
  Low. The work-around for GeminiLake was landed to Linux stable 4.14.125
  and has been backported to B/D.

  === Original Description ==

  This is an follow-up for
  https://bugs.freedesktop.org/show_bug.cgi?id-108085 but found on
  IceLake platforms.

  Right after GDM is login screen is rendered, there might be a thin
  strap of corrupted image at top of the display for a short while. Like
  f-d-o bug 108085, sometimes it can also be reproduced by clicking the
  date/time repeatedly to open and close the calendar several times.
  Etc.

  Known work-around so far is to append kernel boot param
  "i915.enable_fbc=0".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1018-oem-osp1 5.0.0-1018.20
  ProcVersionSignature: Ubuntu 5.0.0-1018.20-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1018-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GN

[Kernel-packages] [Bug 1841736] Re: Intel Killer 1650s [8086:34f0] subsystem [1a56:1651] not supported

[You-Sheng Yang]

** Attachment added: "dmesg when correctly initialized with patched kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1841736/+attachment/5285317/+files/dmesg

** Summary changed:

- Intel Killer 1650s [8086:34f0] subsystem [1a56:1651] not supported
+ Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) 
[8086:34f0] subsystem [1a56:1651] not supported

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

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

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

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1841736] Re: Intel Killer 1650s [8086:34f0] subsystem [1a56:1651] not supported

[You-Sheng Yang]

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1841736/+attachment/5285268/+files/lspci

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

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

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

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

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

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

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

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

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

** Also affects: linux-oem-osp1 (Ubuntu Bionic)
   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/1841736

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

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

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1841736] Re: Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

[You-Sheng Yang]

This would take backport-iwlwifi version 8039[1] or newer, or iwlwifi-
fixes/pending[2] to have full support.

When enabled, it will take "iwlwifi-Qu-c0-hr-b0-*.ucode" instead of
currently requested "iwlwifi-QuQnj-b0-hr-b0-*.ucode" as firmware.

[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/commit/?id=895fe853f8ad30d8ac8460c02cf2d2943360fda4
[2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git/log/?h=pending

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

Title:
  Intel Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter
  (201NGW) [8086:34f0] subsystem [1a56:1651] not supported

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

Bug description:
  iwlwifi cannot initialize this device and leave following error
  messages in dmesg:

iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-50.ucode failed with error -2
...
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39
iwlwifi :00:14.3: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-50

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1017.18
  ProcVersionSignature: Ubuntu 5.0.0-1017.19-oem-osp1 5.0.18
  Uname: Linux 5.0.0-1017-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 15:53:18 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  InstallationDate: Installed on 2019-08-14 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

[You-Sheng Yang]

verified:
* bionic-proposed 1.173.6
* cosmic-proposed 1.175.4
* disco-proposed 1.178.1

** Tags added: verification-done-disco

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

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

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

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

[Kernel-packages] [Bug 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

[You-Sheng Yang]

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

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

Title:
  Screen freeze after resume from S3 when HDMI monitor plugged on Dell
  Precision 7740

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Summary]
  Screen freeze after resume from S3 when HDMI monitor plugged.
  This bug can be reproduced in both AC/DC mode.
  This bug can be reproduced after disabled TLP.

  In kernel log,
  [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
  [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x08008001
  [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at 
page 81919507, read from 'TC2' (0x54433200) (8)
  [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.919343] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)

  [Reproduce Steps

[Kernel-packages] [Bug 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

[You-Sheng Yang]

This has been released in linux-oem. For generic kernel, this has been
landed to bionic/master-next but not yet released.

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

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

Title:
  Screen freeze after resume from S3 when HDMI monitor plugged on Dell
  Precision 7740

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Summary]
  Screen freeze after resume from S3 when HDMI monitor plugged.
  This bug can be reproduced in both AC/DC mode.
  This bug can be reproduced after disabled TLP.

  In kernel log,
  [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
  [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x08008001
  [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at 
page 81919507, read from 'TC2' (0x54433200) (8)
  [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.9

[Kernel-packages] [Bug 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

[You-Sheng Yang]

** Tags added: originate-from-1817304

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

Title:
  Screen freeze after resume from S3 when HDMI monitor plugged on Dell
  Precision 7740

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Summary]
  Screen freeze after resume from S3 when HDMI monitor plugged.
  This bug can be reproduced in both AC/DC mode.
  This bug can be reproduced after disabled TLP.

  In kernel log,
  [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
  [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x08008001
  [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at 
page 81919507, read from 'TC2' (0x54433200) (8)
  [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.919343] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)

  [Reproduce Steps]
  1. Plugged the HDMI monito

[Kernel-packages] [Bug 1827677] Re: Resume from suspend: nothing on display, unable to login

[You-Sheng Yang]

Is networking available when it resumes back? Is it possible to run
apport right after the resume? For example, install openssh-server and
login remotely after sysmtem resumes back. The dmesg log attached
previously seems to be captured after force reboot, so it doesn't
contain any information about the suspend/resume process.

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

Title:
  Resume from suspend: nothing on display, unable to login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is 4.15.0-47-generic on a Dell Latitude 5580.  Closing the laptop
  lid will suspend the system, and opening it will resume, and I
  normally get my xfce session or the xscreensaver unlock dialog.  I
  recently suspended in this manner, but upon opening the laptop lid,
  nothing came up on the display.  The power button was on, and the
  keyboard backlight responded to keypresses.  Ctrl-Alt-PrtScr-[REISUB]
  had no discernible effect (PrtScr because I don't have SysRq on this
  keyboard).  Neither did Ctrl-Alt-Del or Ctrl-Alt-F1 for a console.  I
  needed to poweroff and poweron the laptop which of course caused the
  suspended session state to be lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May  3 16:25:37 2019
  HibernationDevice: RESUME=UUID=e77712df-7257-41aa-8062-076791733f67
  InstallationDate: Installed on 2017-12-12 (507 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Dell Inc. Latitude 5580
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash nouveau.modeset=0 pci=nomsi 
iommu=soft resume=/dev/disk/by-uuid/e77712df-7257-41aa-8062-076791733f67 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-30 (185 days ago)
  dmi.bios.date: 09/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.4
  dmi.board.name: 0FH6CJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: L05248
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.4:bd09/12/2017:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5580
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1829737] [NEW] Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

Public bug reported:

For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
devices and leave error messages in syslog:

  Bluetooth: hci0: request failed to create LE connection: status 0x0c

Which can be detailed by btmon:

  < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
Filter policy: White list is not used (0x00)
Own address type: Public (0x00)
Peer address type: Random (0x01)
Peer address: DB:DD:51:2D:1C:CC (Static)
Initiating PHYs: 0x01
Entry 0: LE 1M
  Scan interval: 60.000 msec (0x0060)
  Scan window: 60.000 msec (0x0060)
  Min connection interval: 30.00 msec (0x0018)
  Max connection interval: 50.00 msec (0x0028)
  Connection latency: 0 (0x)
  Supervision timeout: 420 msec (0x002a)
  Min connection length: 0.000 msec (0x)
  Max connection length: 0.000 msec (0x)
  > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
  LE Extended Create Connection (0x08|0x0043) ncmd 1
Status: Command Disallowed (0x0c)

Indicating this is actually a firmware problem.

Verified this has been fixed at least in upstream linux-firmware commit
29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version
21.10.0.6. With that firmware blob placed under /lib/firmware/intel and
a cold boot, dmesg gives updated revision and device pairing works as
expected:

  Firmware revision 0.1 build 184 week 15 2019

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: New

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
  devices and leave error messages in syslog:

Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x)
Max connection length: 0.000 msec (0x)
> HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

** Tags added: originate-from-1828968 somerville

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
  devices and leave error messages in syslog:

Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x)
Max connection length: 0.000 msec (0x)
> HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

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

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
  devices and leave error messages in syslog:

Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x)
Max connection length: 0.000 msec (0x)
> HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

Affected linux-firmware package series:
* Trusty: N/A
* Xenial: REL0186
  * 4.4.0-1480generic (not supported)
  * 4.15.0-50-generic (not affected)
* Bionic: REL0201 20.30.0.1
  * 4.15.0-1038-oem (not affected)
  * 4.15.0-50-generic (not affected)
  * 4.18.0-20-generic (not affected)
  * 5.0.0-1004-oem-osp1 (affected)
* Cosmic: REL0329 20.70.0.4
  * 4.15.0-50-generic (not affected)
  * 4.18.0-20-generic (not affected)
* Disco: REL0420 21.0.0.4
  * 4.15.0-1038-oem (not affected)
  * 5.0.0.0-15-generic (not affected)
* Eoan: REL0420 21.0.0.4
  * 4.15.0-1038-oem (not affected)
  * 5.0.0.0-15-generic (not affected)

Only Bionic with 5.0.0-1004-oem-osp1 is affected.

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

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

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
  devices and leave error messages in syslog:

Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x)
Max connection length: 0.000 msec (0x)
> HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

** Description changed:

- For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
- devices and leave error messages in syslog:
+ For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and
+ leave error messages in syslog:
  
-   Bluetooth: hci0: request failed to create LE connection: status 0x0c
+   Bluetooth: hci0: request failed to create LE connection: status 0x0c
  
  Which can be detailed by btmon:
  
-   < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
- Filter policy: White list is not used (0x00)
- Own address type: Public (0x00)
- Peer address type: Random (0x01)
- Peer address: DB:DD:51:2D:1C:CC (Static)
- Initiating PHYs: 0x01
- Entry 0: LE 1M
-   Scan interval: 60.000 msec (0x0060)
-   Scan window: 60.000 msec (0x0060)
-   Min connection interval: 30.00 msec (0x0018)
-   Max connection interval: 50.00 msec (0x0028)
-   Connection latency: 0 (0x)
-   Supervision timeout: 420 msec (0x002a)
-   Min connection length: 0.000 msec (0x)
-   Max connection length: 0.000 msec (0x)
-   > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
-   LE Extended Create Connection (0x08|0x0043) ncmd 1
- Status: Command Disallowed (0x0c)
+   < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
+ Filter policy: White list is not used (0x00)
+ Own address type: Public (0x00)
+ Peer address type: Random (0x01)
+ Peer address: DB:DD:51:2D:1C:CC (Static)
+ Initiating PHYs: 0x01
+ Entry 0: LE 1M
+   Scan interval: 60.000 msec (0x0060)
+   Scan window: 60.000 msec (0x0060)
+   Min connection interval: 30.00 msec (0x0018)
+   Max connection interval: 50.00 msec (0x0028)
+   Connection latency: 0 (0x)
+   Supervision timeout: 420 msec (0x002a)
+   Min connection length: 0.000 msec (0x)
+   Max connection length: 0.000 msec (0x)
+   > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
+   LE Extended Create Connection (0x08|0x0043) ncmd 1
+ Status: Command Disallowed (0x0c)
  
  Indicating this is actually a firmware problem.
  
  Verified this has been fixed at least in upstream linux-firmware commit
  29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version
  21.10.0.6. With that firmware blob placed under /lib/firmware/intel and
  a cold boot, dmesg gives updated revision and device pairing works as
  expected:
  
-   Firmware revision 0.1 build 184 week 15 2019
+   Firmware revision 0.1 build 184 week 15 2019

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices
  and leave error messages in syslog:

    Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
    Scan interval: 60.000 msec (0x0060)
    Scan window: 60.000 msec (0x0060)
    Min connection interval: 30.00 msec (0x0018)
    Max connection interval: 50.00 msec (0x0028)
    Connection latency: 0 (0x)
    Supervision timeout: 420 msec (0x002a)
    Min connection length: 0.000 msec (0x)
    Max connection length: 0.000 msec (0x)
    > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
    LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

    Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

https://lists.ubuntu.com/archives/kernel-team/2019-May/100802.html

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices
  and leave error messages in syslog:

    Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
    Scan interval: 60.000 msec (0x0060)
    Scan window: 60.000 msec (0x0060)
    Min connection interval: 30.00 msec (0x0018)
    Max connection interval: 50.00 msec (0x0028)
    Connection latency: 0 (0x)
    Supervision timeout: 420 msec (0x002a)
    Min connection length: 0.000 msec (0x)
    Max connection length: 0.000 msec (0x)
    > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
    LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

    Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[You-Sheng Yang]

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

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

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices
  and leave error messages in syslog:

    Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
    Scan interval: 60.000 msec (0x0060)
    Scan window: 60.000 msec (0x0060)
    Min connection interval: 30.00 msec (0x0018)
    Max connection interval: 50.00 msec (0x0028)
    Connection latency: 0 (0x)
    Supervision timeout: 420 msec (0x002a)
    Min connection length: 0.000 msec (0x)
    Max connection length: 0.000 msec (0x)
    > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
    LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

    Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260 on kernel 4.15

[You-Sheng Yang]

** Tags added: originate-from-1820564 somerville

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

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

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

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Confirmed

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Summary changed:

- iwlwifi not working with Intel AC 9260 on kernel 4.15
+ iwlwifi not working with Intel AC 9260

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

Title:
  iwlwifi not working with Intel AC 9260

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Confirmed

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

[You-Sheng Yang]

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

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

Title:
  iwlwifi not working with Intel AC 9260

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   22.208689] RIP: 0033:0x7fb8c99ef839
  [   22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 
7fb8c99ef839
  [   22.208691] RDX:  RSI: 55c40c09cd2e RDI: 
0001
  [   22.208692] RBP: 000

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

[You-Sheng Yang]

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

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

Title:
  iwlwifi not working with Intel AC 9260

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   22.208689] RIP: 0033:0x7fb8c99ef839
  [   22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 
7fb8c99ef839
  [   22.208691] RDX:  RSI: 55c40c09cd2e RDI: 
0001
  [   22.2086

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

[You-Sheng Yang]

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

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

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

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

Title:
  iwlwifi not working with Intel AC 9260

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   22.208689] RIP: 0033:0x7fb8c99ef839
  [   22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 
7fb8c99ef

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

[You-Sheng Yang]

70:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
Subsystem: Intel Corporation Device [8086:0014]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

The reported device has subsystem id 0014, not 4018 that I was working
on. Will rollback all the changes later.

** No longer affects: linux (Ubuntu Trusty)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: hwe-next

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux (Ubuntu Disco)

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

Title:
  iwlwifi not working with Intel AC 9260

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]  entry_SYSCALL_64_aft

[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260

[You-Sheng Yang]

** Tags removed: originate-from-1820564 somerville

** Changed in: linux (Ubuntu)
 Assignee: You-Sheng Yang (vicamo) => (unassigned)

** Summary changed:

- iwlwifi not working with Intel AC 9260
+ iwlwifi not working with Intel AC 9260 on kernel 4.15

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

Title:
  iwlwifi not working with Intel AC 9260 on kernel 4.15

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [   22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
  [   22.208574] [ cut here ]
  [   22.208575] kernel BUG at 
/build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425!
  [   22.208578] invalid opcode:  [#1] SMP NOPTI
  [   22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek 
snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel 
snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi 
irqbypass uvcvideo mxm_wmi intel_wmi_thunderb
  olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb 
ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer 
intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore
   ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid 
sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) aesni_intel aes_x86_64 crypto_simd
  [   22.208598]  cryptd glue_helper drm_kms_helper syscopyarea sysfillrect 
input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci 
ipmi_msghandler video mac_hid
  [   22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P   OE
4.15.0-43-generic #46-Ubuntu
  [   22.208605] Hardware name: Notebook 
P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018
  [   22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  [   22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286
  [   22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: 
e4b2e1c6ab60
  [   22.208612] RDX: 99b9b38b61a8 RSI:  RDI: 
99b9b8280078
  [   22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 
007690c8
  [   22.208614] R10:  R11: 99b9b8280050 R12: 
99b9b828
  [   22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 
99b9b38b61d0
  [   22.208615] FS:  7fb8c9ec9540() GS:99b9be30() 
knlGS:
  [   22.208616] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 
003606e0
  [   22.208618] DR0:  DR1:  DR2: 

  [   22.208619] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   22.208619] Call Trace:
  [   22.208623]  _iwl_pcie_rx_init+0x252/0x710 [iwlwifi]
  [   22.208626]  iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi]
  [   22.208631]  ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm]
  [   22.208635]  iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi]
  [   22.208639]  iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm]
  [   22.208640]  ? 0xc198e000
  [   22.208644]  iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208647]  ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm]
  [   22.208650]  ? iwl_wait_init_complete+0x20/0x20 [iwlmvm]
  [   22.208654]  iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208657]  ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm]
  [   22.208660]  _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi]
  [   22.208663]  iwl_opmode_register+0x75/0xe0 [iwlwifi]
  [   22.208664]  ? 0xc19e8000
  [   22.208668]  iwl_mvm_init+0x38/0x1000 [iwlmvm]
  [   22.208671]  do_one_initcall+0x52/0x19f
  [   22.208672]  ? _cond_resched+0x19/0x40
  [   22.208674]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [   22.208676]  ? do_init_module+0x27/0x209
  [   22.208678]  do_init_module+0x5f/0x209
  [   22.208679]  load_module+0x191e/0x1f10
  [   22.208681]  ? ima_post_read_file+0x96/0xa0
  [   22.208682]  SYSC_finit_module+0xfc/0x120
  [   22.208683]  ? SYSC_finit_module+0xfc/0x120
  [   22.208685]  SyS_finit_module+0xe/0x10
  [   22.208686]  do_syscall_64+0x73/0x130
  [   22.208688]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   22.208689] RIP: 0033:0x7fb8c99ef839
  [   22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 
7fb8c99ef839
  [   22.208691] RDX:  RSI: 55c40c09cd2e RDI: 
0001
  [   22.208692] RBP: 55c40c09cd2e R08:  R09: 

  [   22.208693] R10: 0001 R11: 0246 R12: 
0

[Kernel-packages] [Bug 1821271] [NEW] New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

[You-Sheng Yang]

Public bug reported:

[Impact] 
New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

[Fix]
Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

[Test Case]
Verified on Intel 9260D2WL.

[Regression Risk]
Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress


** Tags: originate-from-1820564 somerville

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

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

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

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

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

[Kernel-packages] [Bug 1821271] Re: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

[You-Sheng Yang]

02:00.0 Network controller [0280]: Intel Corporation Device [8086:2526] (rev 29)
 Subsystem: Intel Corporation Device [8086:4018]

** Tags added: originate-from-1820564 somerville

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

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

[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

[You-Sheng Yang]

** Tags added: disco

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

Title:
  [nvidia] Screen frozen after switch to other tty  and do login &
  logout

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  New

Bug description:
  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.

  Some more findings:

  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).

  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging
  out doesn't trigger this bug. So this might(?) also involves systemd-
  logind as well;

  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.

  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.

  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.

   Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
 * 5.0.0-7-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 240-6ubuntu1
  * gdm3:
 * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623

  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every
  case.

   ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
 * 5.0.0-7-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 239-7ubuntu10
  * gdm3:
 * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623

  Summary: in Ubuntu Cosmic, same with Disco.

  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 237-3ubuntu10.12
  * gdm3:
 * 3.28.3-0ubuntu18.04.3
  ## Hardware
  * 201811-26623

  Summary: only 4.18 kernel with nouveau driver is immune from this
  issue, which follows some changes in user land should be necessary to
  stabilize all the (nouveau) cases. But even with that, from previous
  results of Cosmic/Disco, there should still some works to be done in
  the nvidia driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821194/+subscriptions

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

[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

[You-Sheng Yang]

This was previously discovered as an alternative way to trigger bug
1804607, but re-filed as a new one for the different behaviour.

By the way, bug 1817738 was once considered a potential root cause to
it. However the proposed change prevents gnome-shell from starting up
normally on systems with nvidia cards and installed nvidia-drivers.

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

Title:
  [nvidia] Screen frozen after switch to other tty  and do login &
  logout

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  New

Bug description:
  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.

  Some more findings:

  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).

  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging
  out doesn't trigger this bug. So this might(?) also involves systemd-
  logind as well;

  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.

  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.

  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.

   Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
 * 5.0.0-7-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 240-6ubuntu1
  * gdm3:
 * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623

  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every
  case.

   ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
 * 5.0.0-7-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 239-7ubuntu10
  * gdm3:
 * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623

  Summary: in Ubuntu Cosmic, same with Disco.

  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
 * 4.15.0-46-generic
 * 4.18.0-16-generic
 * 4.19.0-13-generic
  * nvidia-driver:
 * 390.116-0ubuntu0.18.04.1
 * 390.116-0ubuntu0.18.10.1
 * 410.104-0ubuntu1
  * systemd:
 * 237-3ubuntu10.12
  * gdm3:
 * 3.28.3-0ubuntu18.04.3
  ## Hardware
  * 201811-26623

  Summary: only 4.18 kernel with nouveau driver is immune from this
  issue, which follows some changes in user land should be necessary to
  stabilize all the (nouveau) cases. But even with that, from previous
  results of Cosmic/Disco, there sh

[Kernel-packages] [Bug 1798705] Re: Incomplete linking with boost_regex

[You-Sheng Yang]

** Also affects: gce-compute-image-packages (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gce-compute-image-packages (Ubuntu)
 Assignee: (unassigned) => Daniel Axtens (daxtens)

** No longer affects: 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/1798705

Title:
  Incomplete linking with boost_regex

Status in gce-compute-image-packages package in Ubuntu:
  New

Bug description:
  SRU Justification
  =

  [Impact]
  oslogin fails on Xenial and Trusty.

  In auth.log we see:

  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to 
dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: cannot open 
shared object file: No such file or directory
  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: 
pam_oslogin_login.so
  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to 
dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: cannot open 
shared object file: No such file or directory
  Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: 
pam_oslogin_admin.so

  The error message is a bit deceptive - PAM tries to load the module
  from the correct location, fails, and then tries the other location
  where it is missing. It then reports the missing error rather than the
  real error.

  symlink the module into both paths leads to a much more useful error
  message:

  Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to 
dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: undefined 
symbol: 
_ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE
  Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: 
pam_oslogin_login.so
  Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to 
dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: undefined 
symbol: 
_ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE

  [Test case]
   - set up GCE VM
   - turn on oslogin
   - attempt to log in

  [Fix]
  
debian/patches/0002-Set-LDFLAGS-at-the-end-of-the-c-command-line-right-b.patch 
re-orders the link flags to link boost_regex for oslogin. However, this didn't 
change the flags for PAM module linking. So fix that too.

  [Regression Potential]
  - fixes a regression
  - limited to oslogin, and how it is linked.

  [Other Notes]
  We still see a scary list of warnings when building, but they don't seem to 
have an impact on the common path:
  dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail13put_mem_blockEPv used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZN5boost9re_detail14verify_optionsEjNS_15regex_constants12_match_flagsE used 
by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZNK5boost9re_detail31cpp_regex_traits_implementationIcE17transform_primaryEPKcS4_
 used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZN5boost13match_resultsIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISB_12maybe_assignERKSF_
 used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE
 used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcE9do_assignEPKcS7_j
 used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZN5boost9re_detail19raise_runtime_errorERKSt13runtime_error used by 
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
 found in none of the libraries
  dpkg-shlibdeps: warning: symbol 
_ZNK5boost9re_detail31cpp_regex_traits_implementationIcE9transformEP

[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

[You-Sheng Yang]

I had a try on kernel 4.15.0-46 in Bionic with efi-pstore module loaded
as pstore backend, but I cannot reproduce that kernel panic. It really
takes more information before one can investigation more into this
issue, so apport runs, even before the panic taking place, is really
mandatory. Please give apport a chance to collect some more information
by executing `apport-collect 1821434`.

By the way, have you tried to enable efi-pstore _without_ that SATA card
installed. Maybe it's not related to efi-pstore at all?

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

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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

[Kernel-packages] [Bug 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid

[You-Sheng Yang]

Do you mean you can no longer login GUI after lid open? Do you still
have the access to the system after that? For example, is it possible to
login your laptop via ssh over Wi-Fi/ethernet? If it's not even
available, you may still paste /var/log/syslog of the last boot.

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

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"

[You-Sheng Yang]

https://bbs.archlinux.org/viewtopic.php?id=233230 is this related? It
seems it was fixed by "i915.enable_rc6=0" kernel parameter. Could you
have a try?

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

Title:
  Frequent system freezing with i915 error "*ERROR* Atomic update
  failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

[You-Sheng Yang]

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

Updates from bug 1804607, this is a known xorg issue and duplicates bug
1822184 that can be worked around by disable clear_console in the
$HOME/.bash_logout:

  $ cat $HOME/.bash_logout
  # ~/.bash_logout: executed by bash(1) when login shell exits.

  # when leaving the console clear the screen to increase privacy
  if [ "$SHLVL" = 1 ]; then
# [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
  fi

** This bug has been marked a duplicate of bug 1822184
   clear_console locks up video when X is running and you log out from a plain 
text console

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

Title:
  [nvidia] Screen frozen after switch to other tty  and do login &
  logout

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  New

Bug description:
  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.

  Some more findings:

  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).

  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging
  out doesn't trigger this bug. So this might(?) also involves systemd-
  logind as well;

  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.

  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.

  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.

   Packages:
  * kernel:
     * 4.15.0-46-generic
     * 4.18.0-16-generic
     * 4.19.0-13-generic
     * 5.0.0-7-generic
  * nvidia-driver:
     * 390.116-0ubuntu0.18.04.1
     * 390.116-0ubuntu0.18.10.1
     * 410.104-0ubuntu1
  * systemd:
     * 240-6ubuntu1
  * gdm3:
     * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623

  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every
  case.

   ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
     * 4.15.0-46-generic
     * 4.18.0-16-generic
     * 4.19.0-13-generic
     * 5.0.0-7-generic
  * nvidia-driver:
     * 390.116-0ubuntu0.18.04.1
     * 390.116-0ubuntu0.18.10.1
     * 410.104-0ubuntu1
  * systemd:
     * 239-7ubuntu10
  * gdm3:
     * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623

  Summary: in Ubuntu Cosmic, same with Disco.

  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
     * 4.15.0-46-generic
     * 4.18.0-16-generic
     * 4.19.0-13-generic
  * nvidia-driver:
     * 390.116-0ubuntu0.18.04.1
     * 390.116-0ubuntu0.18.10.1
     * 410.104-0ubuntu1
  * systemd:
     * 237-3ubuntu10.12
  

[Kernel-packages] [Bug 1830822] Re: Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware

[You-Sheng Yang]

** Tags added: originate-from-1828147 somerville

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

Title:
  Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware

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

Bug description:
  Killer series loadded IWL_22000_HR_B_FW_PRE prefixed firmware instead
  IWL_CC_A_FW_PRE prefixed firmware, and firmware named 
iwlwifi-QuQnj-b0-hr-b0-XX.ucode doesn't exist.

  [ 4.252701] iwlwifi :03:00.0: enabling device ( -> 0002)
  [ 4.263301] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-46.ucode failed with error -2
  [ 4.263372] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-45.ucode failed with error -2
  [ 4.263517] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-44.ucode failed with error -2
  [ 4.263589] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-43.ucode failed with error -2
  [ 4.263658] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-42.ucode failed with error -2
  [ 4.263663] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-41.ucode failed with error -2
  [ 4.263668] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-40.ucode failed with error -2
  [ 4.263673] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-39.ucode failed with error -2
  [ 4.263675] iwlwifi :03:00.0: no suitable firmware found!
  [ 4.263676] iwlwifi :03:00.0: minimum version required: 
iwlwifi-QuQnj-b0-hr-b0-39
  [ 4.263677] iwlwifi :03:00.0: maximum version supported: 
iwlwifi-QuQnj-b0-hr-b0-46
  [ 4.263678] iwlwifi :03:00.0: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

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

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

[Kernel-packages] [Bug 1830822] Re: Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware

[You-Sheng Yang]

** Merge proposal linked:
   
https://code.launchpad.net/~canonical-hwe-team/+git/iwlwifi-dkms/+merge/367972

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

Title:
  Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware

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

Bug description:
  Killer series loadded IWL_22000_HR_B_FW_PRE prefixed firmware instead
  IWL_CC_A_FW_PRE prefixed firmware, and firmware named 
iwlwifi-QuQnj-b0-hr-b0-XX.ucode doesn't exist.

  [ 4.252701] iwlwifi :03:00.0: enabling device ( -> 0002)
  [ 4.263301] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-46.ucode failed with error -2
  [ 4.263372] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-45.ucode failed with error -2
  [ 4.263517] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-44.ucode failed with error -2
  [ 4.263589] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-43.ucode failed with error -2
  [ 4.263658] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-42.ucode failed with error -2
  [ 4.263663] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-41.ucode failed with error -2
  [ 4.263668] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-40.ucode failed with error -2
  [ 4.263673] iwlwifi :03:00.0: Direct firmware load for 
iwlwifi-QuQnj-b0-hr-b0-39.ucode failed with error -2
  [ 4.263675] iwlwifi :03:00.0: no suitable firmware found!
  [ 4.263676] iwlwifi :03:00.0: minimum version required: 
iwlwifi-QuQnj-b0-hr-b0-39
  [ 4.263677] iwlwifi :03:00.0: maximum version supported: 
iwlwifi-QuQnj-b0-hr-b0-46
  [ 4.263678] iwlwifi :03:00.0: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

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

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

[Kernel-packages] [Bug 1833065] [NEW] Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

Public bug reported:

Wireless module not detected by the system with the following error
messages in the log:

00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
 Subsystem: Intel Corporation Device [8086:4030]
...
[ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
[ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 op_mode 
iwlmvm
[ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, 
REV=0x354
[ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
[ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping registers
[ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
[ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 0080 
c2218004   
[ 9.355761] iwlwifi :00:14.3: 0020:    40308086 
 00c8  01ff
[ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
[ 9.355792] iwlwifi :00:14.3: : 18489004 0040   
   
[ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 d5d5 
d5d5 d5d5 80008040 001f0040
[ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
[ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
[ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
[ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA channel 
8 [0x0bad1122]
[ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

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

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

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

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

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

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

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

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

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

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


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

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in linux-firmware source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-firmware source package in Eoan:
  New

Bug description:
  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: 

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

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

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in linux-firmware source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-firmware source package in Eoan:
  New

Bug description:
  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

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

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

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

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

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

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

** Also affects: linux-firmware (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/1833065

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in linux-firmware source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-firmware source package in Eoan:
  New

Bug description:
  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

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

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux (Ubuntu Disco)

** No longer affects: linux (Ubuntu Eoan)

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux-firmware source package in Disco:
  New
Status in linux-firmware source package in Eoan:
  New

Bug description:
  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

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

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Cosmic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Disco)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Eoan)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

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

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

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

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

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

Bug description:
  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

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

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

Mark linux-oem-osp1 series Cosmic/Disco/Eoan as WONTFIX due to the lack
of all the basis for Intel AX support in these series. One can still
enable these devices with unofficial DKMS package backport-iwlwifi-dkms
from https://code.launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-
oem-dkms .

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Bionic)

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

** No longer affects: linux-firmware (Ubuntu)

** No longer affects: linux-firmware (Ubuntu Bionic)

** No longer affects: linux-firmware (Ubuntu Cosmic)

** No longer affects: linux-firmware (Ubuntu Disco)

** No longer affects: linux-firmware (Ubuntu Eoan)

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux-firmware source package in Cosmic:
  New
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux-firmware source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

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

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[You-Sheng Yang]

** Description changed:

+ [Impact]
+ Intel Wireless-AC 9560 requires additional driver support as well as new 
firmware blobs to function. Without them iwlwifi cannot correctly recognize the 
device on systems with Comet Lake cpu.
+ 
+ [Fix]
+ These changes are cherry-picked from either mainline kernel or 
backport-iwlwifi. Firmware blob iwlwifi-QuZ-a0-jf-b0-*.ucode is also necessary.
+ 
+ [Test]
+ Verified on hardware 02f0:4234 with fw rev 48.
+ 
+ [Regression Potential]
+ Low. These changes includes only necessary changes to enable Intel 
Wireless-AC 9560.
+ 
+ == Original Bug Description ==
+ 
  Wireless module not detected by the system with the following error
  messages in the log:
  
  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
-  Subsystem: Intel Corporation Device [8086:4030]
+  Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux-firmware source package in Cosmic:
  New
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux-firmware source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Intel Wireless-AC 9560 requires additional driver support as well as new 
firmware blobs to function. Without them iwlwifi cannot correctly recognize the 
device on systems with Comet Lake cpu.

  [Fix]
  These changes are cherry-picked from either mainline kernel or 
backport-iwlwifi. Firmware blob iwlwifi-QuZ-a0-jf-b0-*.ucode is also necessary.

  [Test]
  Verified on hardware 02f0:4234 with fw rev 48.

  [Regression Potential]
  Low. These changes includes only necessary changes to enable Intel 
Wireless-AC 9560.

  == Original Bug Description ==

  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822]

[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

[You-Sheng Yang]

commit 97407b63ea60 drm/amdgpu: use 256 bit buffers for all wb allocations (v2)
commit 63ae07ca4fb4 drm/amdgpu:fix wb_clear

These two commits introduced buggy resource management and are latter
fixed in commit 73469585510d "drm/amdgpu: fix&cleanups for wb_clear".

[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97407b63ea60
[2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63ae07ca4fb4
[3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=73469585510d

** Also affects: linux (Ubuntu Bionic)
   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/1825074

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.

[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

[You-Sheng Yang]

** Tags added: originate-from-1824453 somerville

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

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

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!

  [Reproduce Steps]
  1. apt-get install -y fwts
  2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-

[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

[You-Sheng Yang]

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a1881c9b8a1ed

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

Title:
  mac80211_hwsim unable to handle kernel NULL pointer dereference
  at

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.

  Output:

  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not 
supported by the AP
  [  434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not 
supported by the AP
  [  434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3)
  [  434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 
status=0 aid=1)
  [  434.761761] wlan1: associated
  [  434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
  [  437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  [  437.133996] mac80211_hwsim: initializing netlink
  [  437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht'
  [  437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
  [  437.140661] BUG: unable to handle kernel NULL pointer dereference at 

  [  437.140668] IP: hrtimer_active+0xd/0x50
  [  437.140689] PGD 0 P4D 0 
  [  437.140692] Oops:  [#1] SMP PTI
  [  437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 
coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 
snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 
crypto_simd glue_helper cryptd intel_rapl_perf snd_seq_midi snd_seq_midi_event 
snd_rawmidi input_leds joydev serio_raw snd_seq vmwgfx

[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

[You-Sheng Yang]

Patch to dump amdgpu_wb usage. Confirmed amdgpu_wb_free() is called with
an offset returned from amdgpu_wb_get(), and yet it skips actual release
call because offset is larger than AMDGPU_MAX_WB.

** Patch added: "0001-drm-amdgpu-dump-amdgpu_wb-usage.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825074/+attachment/5256463/+files/0001-drm-amdgpu-dump-amdgpu_wb-usage.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/1825074

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.

  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!

  [Reproduce Steps]
  1. apt-

[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

[You-Sheng Yang]

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

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

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

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

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

Title:
  mac80211_hwsim unable to handle kernel NULL pointer dereference
  at

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

Bug description:
  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.

  Output:

  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not 
supported by the AP
  [  434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not 
supported by the AP
  [  434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3)
  [  434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 
status=0 aid=1)
  [  434.761761] wlan1: associated
  [  434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
  [  437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  [  437.133996] mac80211_hwsim: initializing netlink
  [  437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht'
  [  437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
  [  437.140661] BUG: unable to handle kernel NULL pointer dereference at 

  [  437.140668] IP: hrtimer_active+0xd/0x50
  [  437.140689] PGD 0 P4D 0 
  [  437.140692] Oops:  [#1] SMP PTI
  [  437.140693] Modules linked in:

[Kernel-packages] [Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

[You-Sheng Yang]

Set to INVALID per #10.

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

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

Title:
  Intel 8260 Bluetooth non-functioning, command timeouts

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When trying to use the Gigabyte Z170N-Gaming 5, with Intel 8260
  wifi+bluetooth, bluetooth does not function.

  Dmesg shows:
  [   13.051985] Bluetooth: Core ver 2.22
  [   13.051996] Bluetooth: HCI device and connection manager initialized
  [   13.051998] Bluetooth: HCI socket layer initialized
  [   13.051999] Bluetooth: L2CAP socket layer initialized
  [   13.052031] Bluetooth: SCO socket layer initialized
  [   15.100035] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   15.100036] Bluetooth: hci0: command 0xfc05 tx timeout
  [   15.100270] Bluetooth: hci0: Hardware error 0x08
  [   15.978374] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.978375] Bluetooth: BNEP filters: protocol multicast
  [   15.978377] Bluetooth: BNEP socket layer initialized
  [   17.116013] Bluetooth: hci0: command 0x0c03 tx timeout
  [   25.308049] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   27.324270] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   27.324275] Bluetooth: hci0: command 0xfc05 tx timeout
  [   27.324612] Bluetooth: hci0: Hardware error 0x08
  [   29.340020] Bluetooth: hci0: command 0x0c03 tx timeout
  [   37.340274] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   39.356059] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   39.356071] Bluetooth: hci0: command 0xfc05 tx timeout
  [   39.356499] Bluetooth: hci0: Hardware error 0x08

  
  I have tried the latest intel firmwares from mainline based on:
  https://bugzilla.kernel.org/show_bug.cgi?id=197147#c81
  and
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

  with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fmstrat2489 F pulseaudio
   /dev/snd/controlC0:  fmstrat2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 09:14:54 2019
  InstallationDate: Installed on 2019-01-20 (83 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Z170N-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=16462d84-0501-4b74-aeff-7765953b648f ro modprobe.blacklist=nouveau 
quiet splash intel_iommu=on hugepages=4096 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170N-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/25/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170N-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170N-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170N-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

[You-Sheng Yang]

** Description changed:

+ [Impact]
+ Systems with video cards using amdgpu driver may fail to resume due to 
resource leakage.
+ 
+ [Fix]
+ 73469585510d drm/amdgpu: fix&cleanups for wb_clear
+ 
+ [Test Case]
+ Verified with fwts for a thounsand runs.
+ 
+ [Regression Risk]
+ Low. This patch has been included in stable kernel v4.16.y and on, and
+ it's mostly a trivial bug fix.
+ 
+  Original Bug Report 
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.
  
  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  
  [Reproduce Steps]
  1. apt-get install -y fwts
  2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60
  
  [Results]
  Expected: pass the S3 stress test
  Actual: system hung at 112nd S3
  
  [Additional Information]
  Kernel Version: 4.15.0-1035-oem
  GPU: AMD RX550 (OPGA14) 1002:699f

-- 
You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1821271] Re: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

[You-Sheng Yang]

Verified bionic-proposed version 4.15.0-48.51 and cosmic-proposed
version 4.18.0-18.19, WiFi interface recognized and connected
automatically.

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

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

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

[Kernel-packages] [Bug 1824472] Re: Unable to set brightness on Dell G3 3579 with nomodeset

[You-Sheng Yang]

Mark INVALID per #5.

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

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

Title:
  Unable to set brightness on Dell G3 3579 with nomodeset

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have Dell inspiron G3.
  I am not able to change the screen brightness. I tried many solutions, but 
none worked.

  1. I tried changing acpi_backlight = vendor:
  Now this does solve but it creates another problem. Because for my laptop to 
shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset.

  2. I tried installing applications:
  But when I run these applications it show "No backlights were found on the 
system"

  Kindly address the issue and provide a solution. It is causing great
  trouble.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rishita1806 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 11:55:50 2019
  HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090
  InstallationDate: Installed on 2019-02-28 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G3 3579
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 05K0D2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

[You-Sheng Yang]

** Description changed:

+ [Impact]
+ Kernel NULL pointer dereference in mac80211_hwsim.
+ 
+ [Fix]
+ a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device 
registered
+ 
+ This fix has been included in 4.19.9 or above.
+ 
+ [Test Case]
+ $ git clone https://github.com/aircrack-ng/aircrack-ng
+ # Tested with 69a406c
+ $ cd aircrack-ng
+ $ grep 'sudo apt' README.md | bash
+ $ autoreconf -i
+ $ ./configure --with-experimental
+ $ make check
+ $ sudo bash scripts/airmon-ng.linux check kill
+ $ sudo make integration
+ 
+ # Run integration test again and check dmesg
+ $ sudo bash scripts/airmon-ng.linux check kill
+ $ sudo make integration
+ 
+ Verified with VMs setup locally.
+ 
+ [Regression Risk]
+ Low. Move forward data structure initialization only. This patch has
+ also been included in LTS stable kernel.
+ 
+  Original Bug Report 
+ 
  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.
  
  Output:
  
  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not 
supported by the AP
  [  434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not 
supported by the AP
  [  434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3)
  [  434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 
status=0 aid=1)
  [  434.761761] wlan1: associated
  [  434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
  [  437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  [  437.133996] mac80211_hwsim: initializing netlink
  [  437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht'
  [  437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
  [  437.140661] BUG: unable to handle kernel NULL pointer dereference at 

  [  437.140668] IP: hr

[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat

[You-Sheng Yang]

Seems there is already a discussion thread on Linux-CIFS:
https://lore.kernel.org/linux-
cifs/cadjhv_utw3yi1ujrvde_kkrf4gnjwnup1tuzuihcefzbo7h...@mail.gmail.com/T/

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

Title:
  cifs set_oplock buffer overflow in strcat

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.2 LTS
  Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM

  top - 12:39:53 up  3:41,  4 users,  load average: 66.19, 64.06, 76.90
  Tasks: 1076 total,   1 running, 675 sleeping,  12 stopped,   1 zombie
  %Cpu(s): 28.2 us,  0.3 sy,  0.0 ni, 71.5 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 
st
  KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache
  KiB Swap:   999420 total,   999420 free,0 used. 33477683+avail Mem


  We've seen the following bug many times since we introduced new
  machines running Ubuntu 18. Wasn't an issue older machines running
  Ubuntu 16. Three different machines are affected, so it's rather not a
  hardware issue.

  
  | detected buffer overflow in strcat
  | [ cut here ]
  | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052!
  | invalid opcode:  [#1] SMP PTI
  | Modules linked in: [...]
  | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018
  | RIP: 0010:fortify_panic+0x13/0x22
  |  [...]
  | Call Trace:
  |  smb21_set_oplock_level+0x147/0x1a0 [cifs]
  |  smb3_set_oplock_level+0x22/0x90 [cifs]
  |  smb2_set_fid+0x76/0xb0 [cifs]
  |  cifs_new_fileinfo+0x259/0x390 [cifs]
  |  ? smb2_get_lease_key+0x40/0x40 [cifs]
  |  ? cifs_new_fileinfo+0x259/0x390 [cifs]
  |  cifs_open+0x3db/0x8d0 [cifs]
  |  [...]

  (Full dmesg output attached)

  After hitting this bug there are many cifs related dmesg entries,
  processes lock up and eventually the systems freezes.

  
  The share is mounted using:
  //server/share  /mnt/server/ cifs 
defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks

  Currently we're testing the cifs mount options "cache=none" as the bug
  seems to be oplock related.

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

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

[Kernel-packages] [Bug 1825229] Re: request to supercede the interim changes for 1815268 with upstream commit 8065a779

[You-Sheng Yang]

** Description changed:

- The interm patch in LP# 1815268 was positioned as a way of mitigation to
+ The interm patch in LP#1815268 was positioned as a way of mitigation to
  the rename race condition as described in that bug. Now, the upstream
  patch has been accepted and it eliminates the need of the delay. The
  patch is now in staging tree and should be pulled into mainline soon:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97
  
  Hence we request to back out the delay patch for 1815268 and instead
  apply the upstream patch above.

** Description changed:

- The interm patch in LP#1815268 was positioned as a way of mitigation to
+ The interm patch in bug 1815268 was positioned as a way of mitigation to
  the rename race condition as described in that bug. Now, the upstream
  patch has been accepted and it eliminates the need of the delay. The
  patch is now in staging tree and should be pulled into mainline soon:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97
  
  Hence we request to back out the delay patch for 1815268 and instead
  apply the upstream patch above.

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

Title:
  request to supercede the interim changes for 1815268  with upstream
  commit 8065a779

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The interm patch in bug 1815268 was positioned as a way of mitigation
  to the rename race condition as described in that bug. Now, the
  upstream patch has been accepted and it eliminates the need of the
  delay. The patch is now in staging tree and should be pulled into
  mainline soon:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97

  Hence we request to back out the delay patch for 1815268 and instead
  apply the upstream patch above.

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

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

[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system

[You-Sheng Yang]

This is not a kernel bug. `lsusb` from usbutils package
(bionic/cosmic/disco) only read name strings from usb.ids [1] files.
Upstream has merged a PR [2] to fallback to kernel sysfs attributes, and
with that the names will be correctly shown.


[1]: http://www.linux-usb.org/usb.ids
[2]: https://github.com/gregkh/usbutils/pull/81

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

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

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

** No longer affects: linux (Ubuntu)

** Summary changed:

- Goodix GF3208 (fingerprint reader) not being recognised  by kernel/system
+ Goodix GF3208 (fingerprint reader) not being recognised  by lsusb(usbutils)

** Also affects: usbutils
   Importance: Undecided
   Status: New

** No longer affects: usbutils

** Project changed: linux => usbutils

** Tags added: cosmic disco

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

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  lsusb(usbutils)

Status in usbutils:
  New
Status in usbutils package in Ubuntu:
  Confirmed

Bug description:
  The Goodix GF3208 is not being recognised by the system (Dell Inspiron
  15 7577). What's worse is that it isn't even showing the manufacturer
  vendor id information when doing:

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5301
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Note that the vendor id 27c6 should at least say "Shenzhen Huiding
  Technology Co., Ltd." as per
  
https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings
  /vendor-prefixes.txt

  Will/has support been made for the Goodix GF3208 Fingerprint
  reader/scanner?

  Thanks in advance,
  Haz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  7 04:03:25 2017
  InstallationDate: Installed on 2017-10-01 (5 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1825958] [NEW] Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

[You-Sheng Yang]

Public bug reported:

[Summary]
Screen freeze after resume from S3 when HDMI monitor plugged.
This bug can be reproduced in both AC/DC mode.
This bug can be reproduced after disabled TLP.

In kernel log,
[ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
[ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x08008001
[ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at page 
81919507, read from 'TC2' (0x54433200) (8)
[ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)
[ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
[ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
[ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 73.919343] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 
0, read from 'TC0' (0x54433000) (72)

[Reproduce Steps]
1. Plugged the HDMI monitor and boot
2. Enter S3 and resume from S3
3. The screen is frozen during login screen

[Results]
Expected: The screen does not be frozen.
Actual: The screen is frozen

[Additional Information]
Hardware: Dell Precision 7740
BIOS Version: 0.7.43
Kernel Version: 4.15.0-1036-oem
GPU: 1002:6981

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: Incomplete

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: You-Shen

[Kernel-packages] [Bug 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

[You-Sheng Yang]

Need
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d3252ace0bc652a1a24446b6a549f969bf99
, which is included in Disco and has been SRU-ed to Cosmic in bug
1788874 (for linux v4.18.5 stable release).

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

Title:
  Screen freeze after resume from S3 when HDMI monitor plugged on Dell
  Precision 7740

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Summary]
  Screen freeze after resume from S3 when HDMI monitor plugged.
  This bug can be reproduced in both AC/DC mode.
  This bug can be reproduced after disabled TLP.

  In kernel log,
  [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
  [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x08008001
  [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at 
page 81919507, read from 'TC2' (0x54433200) (8)
  [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.919343] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)

  [Reproduce Steps]
  1. Plugged

[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected

[You-Sheng Yang]

Tried following kernel versions with system upgraded w/ or w/o nvidia-
driver-390 (version 390.116-0ubuntu0.18.04.1) installed. Booting with
HDMI cable connected doesn't have any problem for X, and I got dual
screen working as expected.

* 4.15.0-1035-oem
* 4.15.0-20-generic
* 4.15.0-36-generic
* 4.15.0-47-generic
* 4.18.0-15-generic
* 4.18.0-18-generic

I'm closing this as INVALID. Should there be any further finding, please
don't hesitate to reopen it.

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

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

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port, it usually shows only a blank screen after grub and I
  have to hard power off the laptop. The issue is present when the bios
  and grub are in mirror mode to both screens. I can see the following
  stack trace in journalctl:

  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  This occurs with both a Dell U2515H using an HDMI cord, and a HP
  Compaq LA2405wg connected via HDMI-to-DVI adapter.

  WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen
  shows up.

  WORKAROUND2: Remove "splash" from kernel command line parameters by
  editing /etc/default/grub file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see 
the same issue although the system now randomly crashes later on.
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

[You-Sheng Yang]

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

This has been fixed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1475af255e18f35dc46f8a7acc18354c73d45149
, which has been backported to Cosmic 4.18.0-16.17, Bionic 4.15.0-46.47,
Disco 4.19.0-13.14.

** This bug has been marked a duplicate of bug 1813733
   Ignore "incomplete report" from Elan touchpanels

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

Title:
  i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report
  (16/65535)

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

Bug description:
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  

  Lots of these things

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 2908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 17 20:07:13 2018
  InstallationDate: Installed on 2018-10-10 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1803474] Re: ELANTECH touchpad detected as PS/2 Logitech Wheel Mouse on Compaq Presario 21-N1F3AR

[You-Sheng Yang]

https://www.linuxquestions.org/questions/linux-newbie-8/ps-2-touchpad-
not-working-correctly-4175643961/ seem to point to a working dkms-based
solution already.

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

Title:
  ELANTECH touchpad detected as PS/2 Logitech Wheel Mouse on Compaq
  Presario 21-N1F3AR

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, I formerly had installed Ubuntu 18.04 with the same problem, my
  touchpad was detected as a generic PS2 mouse so I thought that if I
  upgraded my Ubuntu version (currently 18.10) my problem would be
  solved. I tried several fixes that I found on different forums with my
  previous version but they didn't work. I'm not an advanced user and I
  was looking forward to finally switch to linux but this is a big
  problem for me. I attached some files except cat /var/log/Xorg.0.log >
  Xorg.0.log

  cat: /var/log/Xorg.0.log: No existe el archivo o el directorio
  (missing file or directory)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  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-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  flor   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 22:27:10 2018
  InstallationDate: Installed on 2018-11-10 (4 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 003: ID 058f:3822 Alcor Micro Corp. 
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COMPAQ Presario 21 VerK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=39b22cde-4b65-4213-8812-e830a36afe55 ro 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.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-11-14 (0 days ago)
  dmi.bios.date: 02/27/2016
  dmi.bios.vendor: COMPAQ
  dmi.bios.version: fd
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: K21
  dmi.board.vendor: EA
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnCOMPAQ:bvrfd:bd02/27/2016:svnCOMPAQ:pnPresario21VerK:pvrTBDbyOEM:rvnEA:rnK21:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Presario 21 VerK
  dmi.product.sku: Type1Sku0
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: COMPAQ

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

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

[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

[You-Sheng Yang]

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

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

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

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

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

[Kernel-packages] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]

[You-Sheng Yang]

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

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

Title:
  Intel I210 Ethernet card not working after hotplug [8086:1533]

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Summary:
  Intel I210 Ethernet card not working after hotplug

  Steps to reproduce:
  1. Power on system with ethernet cable on Intel I210
  2. Check ethernet is workable
  3. Unplug then plug the ethernet cable

  Expected result:
  Intel I210 Ethernet card is working, e.g. IP address acquired automatically 
if configured as DHCP.

  Actual result:
  Intel I210 Ethernet card not working after hotplug. dmesg has following error 
messages instead:
  [ 16.464321] [ cut here ]
  [ 16.464326] PCI PM: State of device not saved by 
igb_runtime_suspend+0x0/0x90 [igb]
  [ 16.464334] WARNING: CPU: 2 PID: 49 at 
/build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 
pci_pm_runtime_suspend+0x175/0x180
  [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel 
irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep 
ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 
snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi 
intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas 
snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd 
sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci 
intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
  [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect 
i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi 
video
  [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem 
#37-Ubuntu
  [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 
01/14/2019
  [ 16.464369] Workqueue: pm pm_runtime_work
  [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180
  [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282
  [ 16.464372] RAX:  RBX: 8a2557aee0a0 RCX: 0006
  [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490
  [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373
  [ 16.464373] R10:  R11:  R12: 
  [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: 
  [ 16.464374] FS: () GS:8a257c48() 
knlGS:
  [ 16.464375] CS: 0010 DS:  ES:  CR0: 80050033
  [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0
  [ 16.464376] DR0:  DR1:  DR2: 
  [ 16.464376] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 16.464376] Call Trace:
  [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464380] __rpm_callback+0xca/0x210
  [ 16.464381] ? __switch_to_asm+0x40/0x70
  [ 16.464382] ? __switch_to_asm+0x34/0x70
  [ 16.464382] rpm_callback+0x59/0x80
  [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464384] rpm_suspend+0x137/0x640
  [ 16.464385] ? __switch_to_asm+0x40/0x70
  [ 16.464386] pm_runtime_work+0x81/0xa0
  [ 16.464388] process_one_work+0x1de/0x410
  [ 16.464389] worker_thread+0x32/0x410
  [ 16.464390] kthread+0x121/0x140
  [ 16.464391] ? process_one_work+0x410/0x410
  [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70
  [ 16.464392] ret_from_fork+0x35/0x40
  [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b 
b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b 
e9 fd fe ff ff 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53
  [ 16.464408] ---[ end trace 97e5f2cf651b62e6 ]---

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

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

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[You-Sheng Yang]

This is a small C program doing exactly the same thing as fwupd does to
trigger this issue. Usage: `sudo ./read-dpcd /dev/drm_dp_aux`.

To find out what  is, replace ExecStart property in
`/lib/systemd/system/fwupd.service` from `/usr/lib/fwupd/fwupd` to
`/usr/bin/strace -D -tt -y -f -o /var/lib/fwupd/strace.log
/usr/lib/fwupd/fwupd`. Find the last open /dev/drm_dp_aux*.

This was first reported on a premature hardware platform. It was fixed
automatically with a second DVT release and without additional effort
being done in the kernel space.

** Attachment added: "read-dpcd.c"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1826691/+attachment/5260188/+files/read-dpcd.c

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

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal t