[Kernel-packages] [Bug 1809993] Re: Lenovo X1C6 trackpad functions broken

[Andy Whitcroft]

That implies either the test is false triggering, or the driver was
fixed by the bug this papers over.  Could we do some testing to confirm
if this is triggering.

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

[kao]

Cannot see such text. Should I enable some debug flags?

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
- phase: Uploaded
- phase-changed: Monday, 07. January 2019 10:00 UTC
+ phase: Promoted to proposed
+ phase-changed: Tuesday, 08. January 2019 09:00 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Pending -- Ready

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

Title:
  linux-oem: 4.15.0-1031.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Tuesday, 08. January 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Pending -- Ready

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+subscriptions

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

[Kai-Heng Feng]

No it means somehow it's fixed by the new firmware.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic

[Aaron Whitehouse]

Using the firmware from Comment #5 above stopped the wireless and my my
Bluetooth mouse from working, so I have reverted it to the standard
Ubuntu version.

sudo lspci -vvv -s 02:00.0 gives:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1807974

Title:
  Wireless regularly breaking (ath10k firmware crashed!) after upgrade
  to Cosmic

Status in linux package in Ubuntu:
  Confirmed

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

  dmesg output is as follows:

  $ dmesg | grep ath10k

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

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

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

  Bug #1730331 - ath10k_pci: firmware crashed!
  Bug #1627474 - ath10k_pci

[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Tuesday, 08. January 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   verification-testing: Pending -- Ready

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

Title:
  linux-oem: 4.15.0-1031.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Tuesday, 08. January 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+subscriptions

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

[Kernel-packages] [Bug 1794836] Re: Update from 16.04 to 18.04 and serious screen lagging problems

[Yulay]

It solved the problem!!! Million thanks

Sorry for not having figuring it out by myself, in previous versions of
Ubuntu I needed to have it set it that way. Removing nomodeset from the
kernel parameter worked. I only made it from grub editor when booting,
but I'll introdce the change permanently.

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

Title:
  Update from 16.04 to 18.04 and serious screen lagging problems

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded from Ubuntu 16.04 to ubuntu 18.04, and the refreshing of the 
screen in browsers, videos, etc... is really annoying. I would like to solve 
this problem since this is provoking me constant headache
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   julia  3959 F...m pulseaudio
   /dev/snd/pcmC1D0p:   julia  3959 F...m pulseaudio
   /dev/snd/controlC1:  julia  3959 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=3bf717b5-f3c2-45da-9ec8-5926c846f3ea
  InstallationDate: Installed on 2014-09-30 (1458 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D2V
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=34beca2c-8810-4dea-81c4-ea789864bd2f ro nomodeset quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-D2V
  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: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB:bd06/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-D2V
  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/1794836/+subscriptions

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

[Kernel-packages] [Bug 1801490] Re: Unable fix Brightness level directly by pressing F3 key

[punyabrat kumar]

following logs are seen when i execute that command

== ApportVersion =
2.20.9-0ubuntu7.5

== Architecture =
amd64

== CurrentDesktop =
Unity:Unity7:ubuntu

== DistroRelease =
Ubuntu 18.04

== InstallationDate =
Installed on 2016-11-07 (791 days ago)

== InstallationMedia =


== Package =
linux (not installed)

== ProblemType =
Bug

== ProcCpuinfoMinimal =
processor   : 3
vendor_id   : AuthenticAMD
cpu family  : 22
model   : 48
model name  : AMD A6-7310 APU with AMD Radeon R4 Graphics
stepping: 1
microcode   : 0x7030105
cpu MHz : 1094.809
cache size  : 2048 KB
physical id : 0
siblings: 4
core id : 3
cpu cores   : 4
apicid  : 3
initial apicid  : 3
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt topoext perfctr_nb bpext ptsc 
perfctr_llc cpb hw_pstate ssbd vmmcall bmi1 xsaveopt arat npt lbrv svm_lock 
nrip_save tsc_scale flushbyasid decodeassists pausefilter pfthreshold 
overflow_recov
bugs: fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 3992.55
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb acc_power [13]

== ProcEnviron =
LANGUAGE=en
LC_TIME=en_IN.UTF-8
LC_MONETARY=en_IN.UTF-8
TERM=xterm-256color
PATH=(custom, no user)
LC_ADDRESS=en_IN.UTF-8
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
LC_TELEPHONE=en_IN.UTF-8
LD_PRELOAD=
LC_NAME=en_IN.UTF-8
SHELL=/bin/bash
LC_MEASUREMENT=en_IN.UTF-8
LC_IDENTIFICATION=en_IN.UTF-8
LC_NUMERIC=en_IN.UTF-8
LC_PAPER=en_IN.UTF-8

== Tags =
 bionic

== Uname =
Linux 4.18.0-041800rc6-generic x86_64

== UnreportableReason =
The running kernel is not an Ubuntu kernel

== UpgradeStatus =
Upgraded to bionic on 2018-11-08 (60 days ago)

== UserGroups =
adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev 
pulse pulse-access sambashare scanner sudo tape video

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

Title:
  Unable fix Brightness level directly by pressing F3 key

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS
  version,unable to control brightness level by pressing f3 key

  MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 
4.18.0-041800rc6-generic, LLVM 6.0.0)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-11-07 (791 days ago)
  InstallationMedia:
   
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv 
nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Tuesday, 08. January 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

Title:
  linux-oem: 4.15.0-1031.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Tuesday, 08. January 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+subscriptions

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

[Kernel-packages] [Bug 1809699] Re: cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial

[Kleber Sacilotto de Souza]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1809699

Title:
  cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  == SRU Justification ==
  This cpu-hotplug test will always return PASSED even if there are some 
failures there:

  $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  for TARGET in cpu-hotplug; do \
   make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  for TARGET in cpu-hotplug; do \
   make -C $TARGET run_tests; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  pid 25001's current affinity mask: 3
  pid 25001's new affinity mask: 1
  CPU online/offline summary:
    Cpus in online state: 0-1
    Cpus in offline state: 2
  Limited scope test: one hotplug cpu
    (leaves cpu in the original state):
    online to offline to online: cpu 1
    offline to online to offline: cpu 2
  ./cpu-on-off-test.sh: line 78: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  online_cpu_expect_success 2: unexpected fail
  ./cpu-on-off-test.sh: line 83: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  offline_cpu_expect_success 2: unexpected fail
  selftests: cpu-on-off-test.sh [PASS]
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'

  == Fixes ==
  8fe6e53a8ed5f0 (selftests/cpu-hotplug: exit with failure when test occured 
unexpected behaviors)

  For newer releases, they already have this patch.
  For Trusty and older release, they will need more work to get this patch.

  == Regression Potential ==
  None, fix for testing tools.

  For Trusty, it's missing another 20 commits to reach 8fe6e53:
  4813d2e736 (tools: memory-hotplug fix unexpected operator error)
  da9bc4 (tools: selftests - create a separate hotplug target for full 
range test)
  a88cc108f6 (lib: Export interval_tree)
  93e9ef83f4 (test: add minimal module for verification testing)
  3e2a4c183a (test: check copy_to/from_user boundary validation)
  64a8946b44 (net: filter: BPF testsuite)
  7069a97a14 (selftests/net: move test out of Makefile into a shell script)
  3c25fa14f0 (selftests/user: move test out of Makefile into a shell script)
  24fe831c17 (tools/testing/selftests/sysctl: validate sysctl_writes_strict)
  0a8adf5847 (test: add firmware_class loader test)
  6e68e6c5e4 (ftracetest: Initial commit for ftracetest)
  4f5ce5e8d7 (selftests: add memfd_create() + sealing tests)
  c9b26b81af (syscalls: add selftest for execveat(2))
  3ce51050fa (selftest: size: Add size test for Linux kernel) backport with 
context arrangement
  87b2d44026 (selftests: add memfd/sealing page-pinning tests)
  498b473af9 (tools: selftests: fix build issue with make kselftests target)
  ce6a144a0d (selftests/memfd: Run test on all architectures)
  5e29a9105b (selftests: Introduce minimal shared logic for running tests)
  cc16782169 (selftests: change cpu on-off-test.sh name to be unique)
  8c749ce93e (selftests: create test-specific kconfig fragments)
  8fe6e53a8e (selftests/cpu-hotplug: exit with failure when test occured 
unexpected behaviors)

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

Re: [Kernel-packages] [Bug 1810097] Re: HDMI is not recognized

[Heinz Köhler]

Hello!
Many thanks for your help. The cable I have changed and connected 
another monitor. Always the same result.
Best regards

Heinz Köhler
Feldkamp 6 b, Ofen
26160 Bad Zwischenahn
Telefon:  +49 441 69241
Fax:  +49 441 30449608
Mobile:   +49 160 952 134 77
E-Mail:   he...@hkzwahn.de

Am 08.01.19 um 04:30 schrieb Daniel van Vugt:
> Thanks. This means the kernel can't detect anything plugged into HDMI:
>
> /sys/class/drm/card0-HDMI-A-1/enabled:disabled
>
> So if not a kernel bug then most likely the cable isn't plugged in
> properly, or the cable needs replacing. Please try a different HDMI
> cable.
>
> ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)
>

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

Title:
  HDMI is not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 598mm x 336mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8159.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)

  with friendly greetings from Germany
  Heinz Köhler

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Dec 30 17:27:38 2018
  DistUpgraded: 2018-08-21 18:00:51,886 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2014-12-09 (1482 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97-HD3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=79c3b9e1-5aa7-47b0-8673-5fc4a350c917 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (131 days ago)
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-HD3
  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: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97-HD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 21 14:19:34 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Kernel-packages] [Bug 1809847] Re: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

[Kleber Sacilotto de Souza]

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

** Also affects: linux (Ubuntu Cosmic)
   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/1809847

Title:
  Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel 
4.15.0.43.64.
  There is no interrupt while plug/unplug Ethernet cable after S3, so it looks 
like a regression after 4.15.0-33.36.

  [Fix]
  Check changelog and found there are 2 commits introduced from 4.15.0-35.38 
might be suspicious
    * r8169 no internet after suspending (LP: #1779817)
  - r8169: don't use MSI-X on RTL8168g
  - r8169: don't use MSI-X on RTL8106e
  And check the upstream log and found the 2 MSI-X commits had been all 
reverted, since below commit claims it fixes the MSI-X interrupt issue which is 
already in Bionic kernel.
     083874549fdf PCI: Reprogram bridge prefetch registers on resume
  So, I reverted the 2 MSI-X commits and found the Ethernet works again after 
S3.

  [Regression Potential]
  Low, the 2 disable MSI-X commits are workarounds, and now we have proper way 
to fix the issue, so it should be fine to revert them.

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

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

[Kernel-packages] [Bug 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle

[Stefan Bader]

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

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

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => 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/1805775

Title:
  PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long
  idle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Western Digital PC SN720 
NVMe SSD SDAPNTW-256G.

  Short idle: 5.3
  Long idle: 3.0
  S2I: 5.07

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the WD NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 1.66W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1805775

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

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

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

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

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

Title:
  PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long
  idle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Western Digital PC SN720 
NVMe SSD SDAPNTW-256G.

  Short idle: 5.3
  Long idle: 3.0
  S2I: 5.07

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the WD NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 1.66W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

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

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

[Kernel-packages] [Bug 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Xenial)
   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/1810328

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

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

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
  [36.734830] DMAR:[fault reason 06] PTE Read access is not set

  In our case, the rootfs couldn't be initialized since the SCSI adapter
  wasn't initialized due to the DMAR failures (hpsa driver). Also,
  Solarflare NIC (sfc driver) couldn't get initialized too.

  The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
  Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.

  
  [Regression Potential]

  * iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
  and then boot a kernel with this component disabled is inherently a "danger" 
operation from
  drivers (or any users of such mappings) point-of-view. That said, I don't see 
a potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
  once enabled, and this simple patch fixes it

  * Care should be taken of course to not confuse regressions with problems 
induced by disabling the
  iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

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

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

[Kernel-packages] [Bug 1810930] [NEW] ath10k_pci reports error - WiFi stops working

[Arno N. Uehm]

Public bug reported:

After upgrading Ubuntu 16.04.5 LTS from linux 4.4.0-140 to 4.4.0-141 I
noticed that when issuing larger (several GB) downloads over the WiFi
the wireless network hangs and cannot be brought to live again (e. g.
with systemctl restart networking). Rebooting (with and without powering
off) helps, but the problem reappears as soon as you start downloading
within minutes.

So I fear there might be a problem with the latest changes in
ath10k_pci. When booting 4.4.0-140 again (which is still available from
the boot-menu) the problem does not appear. Booting 4.4.0.141 again
let's the problem re-appear. Between boots I powered off the notebook
(Dell XPS13).

Please be kind . this is my first bug report. If I did something wrong
or leave something out please tell me, I'll try to get better.

In parallel I see messages in syslog like this:
Jan  8 11:32:39 ubuntu kernel: [ 8719.011791] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
Jan  8 11:32:39 ubuntu kernel: [ 8719.011805] ath10k_pci :3a:00.0: failed 
to stop scan: -110
Jan  8 11:32:39 ubuntu kernel: [ 8719.011812] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
Jan  8 11:32:39 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-110 retry=1
Jan  8 11:32:43 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
Jan  8 11:32:43 ubuntu kernel: [ 8723.011899] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:32:47 ubuntu kernel: [ 8727.011988] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:32:51 ubuntu kernel: [ 8731.012052] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:32:55 ubuntu kernel: [ 8735.012256] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:32:59 ubuntu kernel: [ 8739.012328] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:03 ubuntu kernel: [ 8743.012433] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:07 ubuntu kernel: [ 8747.012702] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:11 ubuntu kernel: [ 8751.012744] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:15 ubuntu kernel: [ 8755.012917] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:19 ubuntu kernel: [ 8759.013002] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:23 ubuntu kernel: [ 8763.013066] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:27 ubuntu kernel: [ 8767.013085] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:31 ubuntu kernel: [ 8771.013103] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:35 ubuntu kernel: [ 8775.013401] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:39 ubuntu kernel: [ 8779.013286] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:43 ubuntu kernel: [ 8783.013625] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:43 ubuntu wpa_supplicant[2317]: message repeated 15 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
Jan  8 11:33:46 ubuntu gnome-session[2834]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
Jan  8 11:33:47 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
Jan  8 11:33:47 ubuntu kernel: [ 8787.013715] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:51 ubuntu kernel: [ 8791.013592] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:55 ubuntu kernel: [ 8795.013699] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:33:55 ubuntu wpa_supplicant[2317]: message repeated 2 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
Jan  8 11:33:59 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
Jan  8 11:33:59 ubuntu kernel: [ 8799.014036] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:34:03 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
Jan  8 11:34:03 ubuntu kernel: [ 8803.014115] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:34:07 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
Jan  8 11:34:07 ubuntu kernel: [ 8807.014142] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:34:11 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
Jan  8 11:34:11 ubuntu kernel: [ 8811.014251] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
Jan  8 11:34:15 ubuntu kernel: [ 8815.014233] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
a.s.o.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-141-generic 4.4.0-141.167
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  user   2640 F pul

[Kernel-packages] [Bug 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  iommu - need to effectively disable iommu if "intel_iommu=off" is
  passed as a kernel parameter

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

  * If the parameter "intel_iommu=off" is passed for the kernel in a
  boot instance coming from a previously iommu-enabled kernel (like a
  kexec/kdump scenario), currently Xenial kernel (4.4 version) is
  missing a patch to effectively disable the iommu. As a result, the
  previous DMA mappings remain and the new kernel will try to use them,
  which is wrong since we don't have iommu initialized to translate the
  addresses.

  * The upstream patch proposed to SRU here, 161b28aae165 ("iommu/vt-d:
  Make sure IOMMUs are off when intel_iommu=off") fixes the issue by
  effectively disabling the iommu in case it was requested.

  * One important use case is in a scenario of iommu bug that is leading to a 
kernel crash; kdump naturally will have the iommu tables copied from previous 
kernel in kdump boot time, so if iommu
  tables are bogus, we could inherit the bug in the kdump kernel preventing a 
successful dump.
  Have the ability to disable iommu (given that the functionality is there) is 
essential.

  
  [Test Case]

  * Boot a kernel with "intel_iommu=on", and then kexec a new kernel with 
"intel_iommu=off"
  parameter. A kdump test is also possible, by changing the kdump command-line 
to disable
  iommu (after booting a kernel with iommu enabled) - then, induce a crash and 
the issue
  will show.

  * Attached to this Launchpad are 2 files with the kdump test case: 
"iommu-missing" shows
  the issue in a Trusty HWE kernel - without the fix patch, we can see messages 
like

  [36.489918] DMAR: DRHD: handling fault status reg 202
  [36.734830] DMAR: DMAR:[DMA Read] Request device [03:00.0] fault addr 3179a000
  [36.734830] DMAR:[fault reason 06] PTE Read access is not set

  In our case, the rootfs couldn't be initialized since the SCSI adapter
  wasn't initialized due to the DMAR failures (hpsa driver). Also,
  Solarflare NIC (sfc driver) couldn't get initialized too.

  The patch fixed those error messages and the rootfs was mounted (see file 
"iommu-patched").
  Notice the succeeding case couldn't kdump for other reasons, not strictly 
related to the proposed patch here.

  
  [Regression Potential]

  * iommu operations are complex and subject to HW issues eventually. Having 
iommu enabled
  and then boot a kernel with this component disabled is inherently a "danger" 
operation from
  drivers (or any users of such mappings) point-of-view. That said, I don't see 
a potential regression for this patch, in a way currently an user can't disable 
iommu properly if it was
  once enabled, and this simple patch fixes it

  * Care should be taken of course to not confuse regressions with problems 
induced by disabling the
  iommu after it was enabled before (which would show that the patch works fine 
indeed, by allowing iommu to get disabled) - some drivers/devices may require 
iommu to be enabled in order to work, in such case disabling it would prevent 
the device to work.

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

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

[Kernel-packages] [Bug 1810930] Re: ath10k_pci reports error - WiFi stops working

[Arno N. Uehm]

Sorry, the logs do probably not contain the errors, since I actually
rebooted from 4.4.0-140 (to which I previously rebooted to have the WiFi
working) to 4.4.0-141 to submit the bug-report with ubuntu-bug (to have
all versions correct).

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

Title:
  ath10k_pci reports error - WiFi stops working

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading Ubuntu 16.04.5 LTS from linux 4.4.0-140 to 4.4.0-141 I
  noticed that when issuing larger (several GB) downloads over the WiFi
  the wireless network hangs and cannot be brought to live again (e. g.
  with systemctl restart networking). Rebooting (with and without
  powering off) helps, but the problem reappears as soon as you start
  downloading within minutes.

  So I fear there might be a problem with the latest changes in
  ath10k_pci. When booting 4.4.0-140 again (which is still available
  from the boot-menu) the problem does not appear. Booting 4.4.0.141
  again let's the problem re-appear. Between boots I powered off the
  notebook (Dell XPS13).

  Please be kind . this is my first bug report. If I did something wrong
  or leave something out please tell me, I'll try to get better.

  In parallel I see messages in syslog like this:
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011791] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011805] ath10k_pci :3a:00.0: failed 
to stop scan: -110
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011812] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
  Jan  8 11:32:39 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-110 retry=1
  Jan  8 11:32:43 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:32:43 ubuntu kernel: [ 8723.011899] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:47 ubuntu kernel: [ 8727.011988] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:51 ubuntu kernel: [ 8731.012052] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:55 ubuntu kernel: [ 8735.012256] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:59 ubuntu kernel: [ 8739.012328] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:03 ubuntu kernel: [ 8743.012433] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:07 ubuntu kernel: [ 8747.012702] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:11 ubuntu kernel: [ 8751.012744] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:15 ubuntu kernel: [ 8755.012917] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:19 ubuntu kernel: [ 8759.013002] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:23 ubuntu kernel: [ 8763.013066] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:27 ubuntu kernel: [ 8767.013085] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:31 ubuntu kernel: [ 8771.013103] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:35 ubuntu kernel: [ 8775.013401] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:39 ubuntu kernel: [ 8779.013286] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu kernel: [ 8783.013625] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu wpa_supplicant[2317]: message repeated 15 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:46 ubuntu gnome-session[2834]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Jan  8 11:33:47 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:47 ubuntu kernel: [ 8787.013715] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:51 ubuntu kernel: [ 8791.013592] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu kernel: [ 8795.013699] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu wpa_supplicant[2317]: message repeated 2 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:59 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:59 ubuntu kernel: [ 8799.014036] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:03 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:03 ubuntu kernel: [ 8803.014115] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:07 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:07 ubuntu kernel: [ 8807.014142] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:11 ubuntu wpa_supplicant[2317]: wlp58s0: CTR

[Kernel-packages] [Bug 1801102] Re: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => 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/1801102

Title:
  Please include this patch in bionic kernel
  https://www.spinics.net/lists/linux-wireless/msg169994.html

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

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

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

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

[Kernel-packages] [Bug 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle

[Stefan Bader]

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1805775

Title:
  PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long
  idle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Western Digital PC SN720 
NVMe SSD SDAPNTW-256G.

  Short idle: 5.3
  Long idle: 3.0
  S2I: 5.07

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the WD NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 1.66W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

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

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

[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Stefan Bader]

And what about cosmic, too.

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

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

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

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

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

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

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

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Krister]

The 4.15.0-34-generic downloaded from https://launchpad.net/~canonical-
kernel-team/+archive/ubuntu/ppa/+build/15307305 works.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Krister]

The 4.15.18-041518-generic kernel works.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Krister]

The 4.16.0-041600-generic kernel works.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Krister]

The 4.15.0-34-generic downloaded from https://launchpad.net/~canonical-
kernel-team/+archive/ubuntu/ppa/+build/15307305 works.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

[Krister]

The 4.15.18-041518-generic kernel works.

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

Title:
  Boot hangs at "loading initial ramdisk..."

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

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1810930] Re: ath10k_pci reports error - WiFi stops working

[Arno N. Uehm]

Hhhmmm, currently it does not re-occur. May be it was something else.

Before someone really stops working on it, we should wait a day or two.
I'll keep you informed.

Sorry

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

Title:
  ath10k_pci reports error - WiFi stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 16.04.5 LTS from linux 4.4.0-140 to 4.4.0-141 I
  noticed that when issuing larger (several GB) downloads over the WiFi
  the wireless network hangs and cannot be brought to live again (e. g.
  with systemctl restart networking). Rebooting (with and without
  powering off) helps, but the problem reappears as soon as you start
  downloading within minutes.

  So I fear there might be a problem with the latest changes in
  ath10k_pci. When booting 4.4.0-140 again (which is still available
  from the boot-menu) the problem does not appear. Booting 4.4.0.141
  again let's the problem re-appear. Between boots I powered off the
  notebook (Dell XPS13).

  Please be kind . this is my first bug report. If I did something wrong
  or leave something out please tell me, I'll try to get better.

  In parallel I see messages in syslog like this:
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011791] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011805] ath10k_pci :3a:00.0: failed 
to stop scan: -110
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011812] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
  Jan  8 11:32:39 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-110 retry=1
  Jan  8 11:32:43 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:32:43 ubuntu kernel: [ 8723.011899] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:47 ubuntu kernel: [ 8727.011988] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:51 ubuntu kernel: [ 8731.012052] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:55 ubuntu kernel: [ 8735.012256] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:59 ubuntu kernel: [ 8739.012328] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:03 ubuntu kernel: [ 8743.012433] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:07 ubuntu kernel: [ 8747.012702] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:11 ubuntu kernel: [ 8751.012744] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:15 ubuntu kernel: [ 8755.012917] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:19 ubuntu kernel: [ 8759.013002] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:23 ubuntu kernel: [ 8763.013066] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:27 ubuntu kernel: [ 8767.013085] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:31 ubuntu kernel: [ 8771.013103] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:35 ubuntu kernel: [ 8775.013401] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:39 ubuntu kernel: [ 8779.013286] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu kernel: [ 8783.013625] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu wpa_supplicant[2317]: message repeated 15 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:46 ubuntu gnome-session[2834]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Jan  8 11:33:47 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:47 ubuntu kernel: [ 8787.013715] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:51 ubuntu kernel: [ 8791.013592] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu kernel: [ 8795.013699] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu wpa_supplicant[2317]: message repeated 2 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:59 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:59 ubuntu kernel: [ 8799.014036] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:03 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:03 ubuntu kernel: [ 8803.014115] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:07 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:07 ubuntu kernel: [ 8807.014142] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:11 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:11 ub

[Kernel-packages] [Bug 1810930] Re: ath10k_pci reports error - WiFi stops working

[Arno N. Uehm]

Last comment should have read "before someone STARTS working on it" off
course.

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

Title:
  ath10k_pci reports error - WiFi stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 16.04.5 LTS from linux 4.4.0-140 to 4.4.0-141 I
  noticed that when issuing larger (several GB) downloads over the WiFi
  the wireless network hangs and cannot be brought to live again (e. g.
  with systemctl restart networking). Rebooting (with and without
  powering off) helps, but the problem reappears as soon as you start
  downloading within minutes.

  So I fear there might be a problem with the latest changes in
  ath10k_pci. When booting 4.4.0-140 again (which is still available
  from the boot-menu) the problem does not appear. Booting 4.4.0.141
  again let's the problem re-appear. Between boots I powered off the
  notebook (Dell XPS13).

  Please be kind . this is my first bug report. If I did something wrong
  or leave something out please tell me, I'll try to get better.

  In parallel I see messages in syslog like this:
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011791] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011805] ath10k_pci :3a:00.0: failed 
to stop scan: -110
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011812] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
  Jan  8 11:32:39 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-110 retry=1
  Jan  8 11:32:43 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:32:43 ubuntu kernel: [ 8723.011899] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:47 ubuntu kernel: [ 8727.011988] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:51 ubuntu kernel: [ 8731.012052] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:55 ubuntu kernel: [ 8735.012256] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:59 ubuntu kernel: [ 8739.012328] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:03 ubuntu kernel: [ 8743.012433] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:07 ubuntu kernel: [ 8747.012702] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:11 ubuntu kernel: [ 8751.012744] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:15 ubuntu kernel: [ 8755.012917] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:19 ubuntu kernel: [ 8759.013002] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:23 ubuntu kernel: [ 8763.013066] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:27 ubuntu kernel: [ 8767.013085] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:31 ubuntu kernel: [ 8771.013103] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:35 ubuntu kernel: [ 8775.013401] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:39 ubuntu kernel: [ 8779.013286] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu kernel: [ 8783.013625] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu wpa_supplicant[2317]: message repeated 15 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:46 ubuntu gnome-session[2834]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Jan  8 11:33:47 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:47 ubuntu kernel: [ 8787.013715] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:51 ubuntu kernel: [ 8791.013592] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu kernel: [ 8795.013699] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu wpa_supplicant[2317]: message repeated 2 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:59 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:59 ubuntu kernel: [ 8799.014036] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:03 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:03 ubuntu kernel: [ 8803.014115] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:07 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:07 ubuntu kernel: [ 8807.014142] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:11 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:11 ubuntu kernel: [ 8811.014251] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  ath10k_pci reports error - WiFi stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 16.04.5 LTS from linux 4.4.0-140 to 4.4.0-141 I
  noticed that when issuing larger (several GB) downloads over the WiFi
  the wireless network hangs and cannot be brought to live again (e. g.
  with systemctl restart networking). Rebooting (with and without
  powering off) helps, but the problem reappears as soon as you start
  downloading within minutes.

  So I fear there might be a problem with the latest changes in
  ath10k_pci. When booting 4.4.0-140 again (which is still available
  from the boot-menu) the problem does not appear. Booting 4.4.0.141
  again let's the problem re-appear. Between boots I powered off the
  notebook (Dell XPS13).

  Please be kind . this is my first bug report. If I did something wrong
  or leave something out please tell me, I'll try to get better.

  In parallel I see messages in syslog like this:
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011791] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011805] ath10k_pci :3a:00.0: failed 
to stop scan: -110
  Jan  8 11:32:39 ubuntu kernel: [ 8719.011812] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
  Jan  8 11:32:39 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-110 retry=1
  Jan  8 11:32:43 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:32:43 ubuntu kernel: [ 8723.011899] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:47 ubuntu kernel: [ 8727.011988] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:51 ubuntu kernel: [ 8731.012052] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:55 ubuntu kernel: [ 8735.012256] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:32:59 ubuntu kernel: [ 8739.012328] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:03 ubuntu kernel: [ 8743.012433] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:07 ubuntu kernel: [ 8747.012702] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:11 ubuntu kernel: [ 8751.012744] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:15 ubuntu kernel: [ 8755.012917] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:19 ubuntu kernel: [ 8759.013002] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:23 ubuntu kernel: [ 8763.013066] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:27 ubuntu kernel: [ 8767.013085] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:31 ubuntu kernel: [ 8771.013103] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:35 ubuntu kernel: [ 8775.013401] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:39 ubuntu kernel: [ 8779.013286] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu kernel: [ 8783.013625] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:43 ubuntu wpa_supplicant[2317]: message repeated 15 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:46 ubuntu gnome-session[2834]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Jan  8 11:33:47 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:47 ubuntu kernel: [ 8787.013715] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:51 ubuntu kernel: [ 8791.013592] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu kernel: [ 8795.013699] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:33:55 ubuntu wpa_supplicant[2317]: message repeated 2 times: [ 
wlp58s0: CTRL-EVENT-SCAN-FAILED ret=-11 retry=1]
  Jan  8 11:33:59 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:33:59 ubuntu kernel: [ 8799.014036] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:03 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:03 ubuntu kernel: [ 8803.014115] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:07 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:07 ubuntu kernel: [ 8807.014142] ath10k_pci :3a:00.0: failed 
to start hw scan: -11
  Jan  8 11:34:11 ubuntu wpa_supplicant[2317]: wlp58s0: CTRL-EVENT-SCAN-FAILED 
ret=-11 retry=1
  Jan  8 11:34:11 ubuntu kernel: [ 8811.014251] ath10k_pci :3a:00.0: failed 
to start hw scan: -

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

[Ubuntu Kernel Bot]

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

apport-collect 1810702

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

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

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

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

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

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

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T

[Kleber Sacilotto de Souza]

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1809868

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on T

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  In Progress

Bug description:
  == Justification ==
  When doing an incremental send on a Btrfs filesystem, if we delete a 
directory that has N > 1 hardlinks for the same file and that file has the 
highest inode number inside the directory contents, an incremental send would 
send N times rmdir operation against the directory. This made the btrfs receive 
command fail on the second rmdir instruction, as the target directory didn't 
exist anymore.

  This issue can be triggered with 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
  test in ubuntu_btrfs_kernel_fixes test suite.

  The test will fail with:
    "ERROR: rmdir o259-6-0 failed. No such file or directory" with Trusty 
kernel.

  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
   nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  At subvol /tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2
  Performing full device TRIM (1.00GiB) ...
  Turning ON incompat feature 'extref': increased hardlink limit per file to 
65536

  WARNING! - Btrfs v3.12 IS EXPERIMENTAL
  WARNING! - see http://btrfs.wiki.kernel.org before using

  fs created label (null) on /dev/loop0
   nodesize 16384 leafsize 16384 sectorsize 4096 size 1.00GiB
  Btrfs v3.12
  At subvol snap1
  At snapshot snap2
  ERROR: rmdir o259-6-0 failed. No such file or directory
  incremental receive failed

  == Fix ==
  29d6d30f5 (Btrfs: send, don't send rmdir for same target multiple times)
  This patch needs to be backported for a variable difference in the 
process_recorded_refs function.

  In the Trusty tree:
  static int process_recorded_refs(struct send_ctx *sctx)

  In the patch:
  static int process_recorded_refs(struct send_ctx *sctx, int *pending_move)

  As the new *pending_move is unrelated here, we can just backport the
  patch with the same logic in this function.

  A test kernel could be found here:
  http://people.canonical.com/~phlin/kernel/lp-1809868-btrfs-2nd-rmdir/
  This test will pass with this kernel.

  == Regression potential ==
  Low,
  this patch just adds an extra check to skip unnecessary rmdir operations.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 03:14 seq
   crw-rw 1 root audio 116, 33 Dec 27 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [13958.095408] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.102670] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.105901] btrfs: device fsid da34075a-4eaa-4e50-aeea-02206e8c8e44 devid 
1 transid 4 /dev/loop0
   [13958.106099] btrfs: disk space caching is enabled
   [13958.107771] btrfs: creating UUID tree
  Date: Thu Dec 27 07:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-ge

[Kernel-packages] [Bug 1801102] Re: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html

[Kleber Sacilotto de Souza]

Hi Konstantin,

The fix for this issue has been submitted as a kernel SRU request and
will be considered for the next SRU cycle. If it's accepted, a kernel
build with the fix will be available in -proposed on the week between
14-Jan - 18-Jan, and released on -updated by 31-Jan.

More details about the schedule of kernel SRU can be found at
https://kernel.ubuntu.com/.

Thanks.

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

Title:
  Please include this patch in bionic kernel
  https://www.spinics.net/lists/linux-wireless/msg169994.html

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

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

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

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

[Kernel-packages] [Bug 1801102] Re: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html

[Konstantin Petrov]

Great - thanks all for the help.

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

Title:
  Please include this patch in bionic kernel
  https://www.spinics.net/lists/linux-wireless/msg169994.html

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

Bug description:
  ===SRU Justification===
  [Impact]
  iwlwifi spews "Too many chunks: 20" in dmesg.

  [Fix] 
  From the patch description:
  "
  When we free the TFD, we check its number of valid pointers
  and make sure it doesn't exceed the number of pointers the
  hardware support.
  This check had an off by one bug: it is perfectly valid to
  free the 20 pointers if the TFD has 20 pointers.
  "

  [Test]
  User confirms the patch solves the problem.

  [Regression Potential]
  Low. The fix is limited to iwlwifi, and the patch is in mainline for a
  while.

  ===Original Bug Report===
  Hi:

  I am having the same issue i.e. when downloading torrent with
  KTorrent. Please include this fix https://www.spinics.net/lists/linux-
  wireless/msg169994.html in the release kernel.

  Thanks

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

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

[Kernel-packages] [Bug 1283589]

[odi]

ping... what else is required to get this merged?

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable > /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable > /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1810807] Re: Xenial update: 4.4.163 upstream stable release

[Juerg Haefliger]

List of previously applied patches:
  * gro: Allow tunnel stacking in the case of FOU/GUE
  * tpm: fix: return rc when devm_add_action() fails
  * ixgbe: Correct X550EM_x revision check
  * ixgbe: fix RSS limit for X550
  * ixgbevf: Fix handling of NAPI budget when multiple queues are enabled per 
vector

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

Title:
  Xenial update: 4.4.163 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

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

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

  Linux 4.4.163
  x86/time: Correct the attribute on jiffies' definition
  l2tp: hold tunnel socket when handling control frames in l2tp_ip and l2tp_ip6
  cpuidle: Do not access cpuidle_devices when !CONFIG_CPU_IDLE
  x86/percpu: Fix this_cpu_read()
  sched/fair: Fix throttle_list starvation with low CFS quota
  Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15IGM
  USB: fix the usbfs flag sanitization for control transfers
  usb: gadget: storage: Fix Spectre v1 vulnerability
  cdc-acm: correct counting of UART states in serial state notification
  IB/ucm: Fix Spectre v1 vulnerability
  RDMA/ucma: Fix Spectre v1 vulnerability
  ptp: fix Spectre v1 vulnerability
  cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)
  ahci: don't ignore result code of ahci_reset_controller()
  crypto: shash - Fix a sleep-in-atomic bug in shash_setkey_unaligned
  mremap: properly flush TLB before releasing the page
  rtnetlink: Disallow FDB configuration for non-Ethernet device
  vhost: Fix Spectre V1 vulnerability
  net: drop skb on failure in ip_check_defrag()
  sctp: fix race on sctp_id2asoc
  r8169: fix NAPI handling under high load
  net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules
  net: socket: fix a missing-check bug
  net: sched: gred: pass the right attribute to gred_change_table_def()
  net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs
  ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called
  ipv6: mcast: fix a use-after-free in inet6_mc_check
  net: bridge: remove ipv6 zero address check in mcast queries
  bridge: do not add port to router list when receives query with source 0.0.0.0
  perf tools: Disable parallelism for 'make clean'
  mtd: spi-nor: Add support for is25wp series chips
  fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()
  ARM: dts: imx53-qsb: disable 1.2GHz OPP
  MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
  igb: Remove superfluous reset to PHY and page 0 selection
  MIPS: microMIPS: Fix decoding of swsp16 instruction
  scsi: aacraid: Fix typo in blink status
  bonding: avoid defaulting hard_header_len to ETH_HLEN on slave removal
  PM / devfreq: tegra: fix error return code in tegra_devfreq_probe()
  ASoC: spear: fix error return code in spdif_in_probe()
  spi: xlp: fix error return code in xlp_spi_probe()
  spi/bcm63xx: fix error return code in bcm63xx_spi_probe()
  MIPS: Handle non word sized instructions when examining frame
  spi/bcm63xx-hspi: fix error return code in bcm63xx_hsspi_probe()
  usb: dwc3: omap: fix error return code in dwc3_omap_probe()
  usb: ehci-omap: fix error return code in ehci_hcd_omap_probe()
  usb: imx21-hcd: fix error return code in imx21_probe()
  gpio: msic: fix error return code in platform_msic_gpio_probe()
  sparc64: Fix exception handling in UltraSPARC-III memcpy.
  gpu: host1x: fix error return code in host1x_probe()
  sparc64 mm: Fix more TSB sizing issues
  video: fbdev: pxa3xx_gcu: fix error return code in pxa3xx_gcu_probe()
  tty: serial: sprd: fix error return code in sprd_probe()
  l2tp: hold socket before dropping lock in l2tp_ip{, 6}_recv()
  brcmfmac: Fix glom_skb leak in brcmf_sdiod_recv_chain
  gro: Allow tunnel stacking in the case of FOU/GUE
  vti6: flush x-netns xfrm cache when vti interface is removed
  ALSA: timer: Fix zero-division by continue of uninitialized instance
  ixgbe: Correct X550EM_x revision check
  ixgbe: fix RSS limit for X550
  net/mlx5e: Correctly handle RSS indirection table when changing number of 
channels
  net/mlx5e: Fix LRO modify
  ixgbevf: Fix handling of NAPI budget when multiple queues are enabled per 
vector
  fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio
  drm/nouveau/fbcon: fix oops without fbdev emulation
  bpf: generally move prog destruction to RCU deferral

[Kernel-packages] [Bug 1809219] Re: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported

[Kleber Sacilotto de Souza]

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

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

Title:
  Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not
  supported

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Killer Wireless-1550 is not supported by Bionic kernel.

  [Fix]
  This card can be supported by adding its structs and IDs into table by below 
commit.
  0a5257bc6d89 iwlwifi: add more card IDs for 9000 series

  [Test]
  Verified wifi works after applied the commit.

  [Regression Potential]
  Low. It adds its own structs and IDs to support killer cards.

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

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

[Kernel-packages] [Bug 1808912] Re: scsi: libsas: fix a race condition when smp task timeout

[Seth Forshee]

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

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

Title:
  scsi: libsas: fix a race condition when smp task timeout

Status in linux package in Ubuntu:
  Fix Committed
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:
  Fix Committed

Bug description:
  [Impact]
  When the lldd is processing the complete sas task in interrupt and set the
  task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be
  triggered at the same time. And smp_task_timedout() will complete the task
  wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed
  before lldd end the interrupt process. Thus a use-after-free will happen.

  [Test Case]
  This is hard to reproduce, so regression test only.

  [Fix]
  b90cd6f2b9 scsi: libsas: fix a race condition when smp task timeout

  [Regression Risk]
  Only 2 line moved in libsas and maintainer has reviewed/approved. I will say 
it's low.

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

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

[Kernel-packages] [Bug 1805414] Re: [Ubuntu] kernel: zcrypt: reinit ap queue state machine

[Seth Forshee]

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

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

Title:
  [Ubuntu] kernel: zcrypt: reinit ap queue state machine

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  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:
  == SRU Justification ==
  The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.

  This commit has also been cc'd to upstream stable.

  == Fix ==
  104f708fd ("s390/zcrypt: reinit ap queue state machine during device probe")

  == Regression Potential ==
  Low.  Limited to s390.

  
  == Original Bug Description ==
  Description:  kernel: zcrypt: reinit ap queue state machine

  Symptom:  Zcrypt ap queue device not operational at host level after a
    kvm guest used it.

  Problem:  The vfio device driver when receiving an ap queue device does
    additional resets thereby removing the registration for
    interrupts for  the ap device done by the ap bus core
    code. So when later the vfio driver releases the device and
    one of the default zcrypt drivers takes care of the device
    the interrupt registration needs to get renewed. The current
    code does no renew and result is that requests send into such
    a queue will never see a reply processed - the application
    hangs.

  Solution: This patch adds a function which resets the aq queue state
    machine for the ap queue device and triggers the walk through
    the initial states (which are reset and registration for
    interrupts). This function is now called before the driver's
    probe function is invoked.
    When the association between driver and device is released,
    the driver's remove function is called. The current
    implementation calls a ap queue function
    ap_queue_remove(). This invokation has been moved to the ap
    bus function to make the probe / remove pair for ap bus and
    drivers more symmetric.

  Reproduction: Set up an kvm guest to use one or more ap queues in
    pass-through mode. Start the guest. Stop the guest. Reassign
    the ap resources back to the host system. Run an application
    which uses exactly this ap resources. Without the fix, the
    application hangs; with the fix the application should run
    fine.

  Upstream commit(s):
  104f708fd1241b22f808bdf066ab67dc5a051de5
  Available on kernel.org

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

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

[Kernel-packages] [Bug 1810892] Re: lineout jack can't work on a Dell machine

[Kleber Sacilotto de Souza]

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

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

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

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

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

Title:
  lineout jack can't work on a Dell machine

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]
  The rear lineout jack can't work. If users plug a headphone or audio
  cable into the lineout jack, nothing happens, the audio still output
  from internal speaker. The expected behaviour is the lineout is
  active and the sound is routed to lineout jack from internal speaker.

  [Fix]
  apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the
  lineout pin to be a correct configuration value.

  
  [Test Case]
  plug headphone into the rear lineout jack, system can detect lineout
  jack is plugged and the audio output is routed to lineout jack from
  internal speaker.

  
  [Regression Potential]
  Very low, this patch is specific to one Dell machine model.

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

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

[Kernel-packages] [Bug 1810891] Re: audio output has constant noise on a Dell machine

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  audio output has constant noise on a Dell machine

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]
  the audio output (headpohne, lineout and internal speaker) has constant
  noise when playing sound.

  [Fix]
  Set the pin configuration and some secret coeff registers, the noise
  disappears. This patch is written by Realtek engineer and is upstreamd
  already.

  
  [Test Case]
  play sound via internal speaker, lineout and headphone, no noise anymore.

  
  [Regression Potential]
  Very low, this patch is upstreamd for a while, no regression is reported.

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

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

[Kernel-packages] [Bug 1809046] Re: Cannot initialize ATA disk if IDENTIFY command fails

[Seth Forshee]

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

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

Title:
  Cannot initialize ATA disk if IDENTIFY command fails

Status in linux package in Ubuntu:
  Fix Committed
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:
  Fix Committed

Bug description:
  [Impact]
  ATA disks attached to a SAS controller may not initialize if the initial 
IDENTIFY command fails.

  [Test Case]
  The positive test case would require a disk that fails to respond correctly 
to an IDENTIFY command. I don't have one of those, so can only regression test 
on a system w/ SAS connected disks.

  [Fix]
  437207d3697f5 scsi: libsas: check the ata device status by ata_dev_enabled()

  [Regression Risk]
  Clean cherry pick from upstream - any regressions will have upstream support.

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

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

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

Title:
  ldisc crash on reopened tty

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:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
  [684766.669194] Oops:  [#1] SMP
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  [Test Case]

  * Deploy a Trusty KVM instance with a LTS Xenial kernel (v4.4 series)
  * SSH in frequently while system is under load, send commands before the 
prompt has returned.
  

  Check comment #5 for a summary about the upstream proposals to resolve
  this issue.

To manage notifications about this

[Kernel-packages] [Bug 1810947] [NEW] Xenial update: 4.4.164 upstream stable release

[Juerg Haefliger]

Public bug reported:

SRU Justification

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

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

Linux 4.4.164
drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values
drm/dp_mst: Check if primary mstb is null
drm/rockchip: Allow driver to be shutdown on reboot/kexec
mm: migration: fix migration of huge PMD shared pages
hugetlbfs: fix kernel BUG at fs/hugetlbfs/inode.c:444!
configfs: replace strncpy with memcpy
fuse: fix leaked notify reply
rtc: hctosys: Add missing range error reporting
sunrpc: correct the computation for page_ptr when truncating
mount: Prevent MNT_DETACH from disconnecting locked mounts
mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
mount: Retest MNT_LOCKED in do_umount
ext4: fix buffer leak in __ext4_read_dirblock() on error path
ext4: fix buffer leak in ext4_xattr_move_to_block() on error path
ext4: release bs.bh before re-using in ext4_xattr_block_find()
ext4: fix possible leak of sbi->s_group_desc_leak in error path
ext4: avoid possible double brelse() in add_new_gdb() on error path
ext4: fix missing cleanup if ext4_alloc_flex_bg_array() fails while resizing
ext4: avoid buffer leak in ext4_orphan_add() after prior errors
ext4: fix possible inode leak in the retry loop of ext4_resize_fs()
ext4: avoid potential extra brelse in setup_new_flex_group_blocks()
ext4: add missing brelse() add_new_gdb_meta_bg()'s error path
ext4: add missing brelse() in set_flexbg_block_bitmap()'s error path
ext4: add missing brelse() update_backups()'s error path
clockevents/drivers/i8253: Add support for PIT shutdown quirk
Btrfs: fix data corruption due to cloning of eof block
arch/alpha, termios: implement BOTHER, IBSHIFT and termios2
termios, tty/tty_baudrate.c: fix buffer overrun
mtd: docg3: don't set conflicting BCH_CONST_PARAMS option
mm: thp: relax __GFP_THISNODE for MADV_HUGEPAGE mappings
ocfs2: fix a misuse a of brelse after failing ocfs2_check_dir_entry
vhost/scsi: truncate T10 PI iov_iter to prot_bytes
mach64: fix image corruption due to reading accelerator registers
mach64: fix display corruption on big endian machines
libceph: bump CEPH_MSG_MAX_DATA_LEN
clk: s2mps11: Fix matching when built as module and DT node contains compatible
xtensa: fix boot parameters address translation
xtensa: make sure bFLT stack is 16 byte aligned
xtensa: add NOTES section to the linker script
MIPS: Loongson-3: Fix BRIDGE irq delivery problem
MIPS: Loongson-3: Fix CPU UART irq delivery problem
bna: ethtool: Avoid reading past end of buffer
e1000: fix race condition between e1000_down() and e1000_watchdog
e1000: avoid null pointer dereference on invalid stat type
mm: do not bug_on on incorrect length in __mm_populate()
fs, elf: make sure to page align bss in load_elf_library
mm: refuse wrapped vm_brk requests
binfmt_elf: fix calculations for bss padding
mm, elf: handle vm_brk error
fuse: set FR_SENT while locked
fuse: fix blocked_waitq wakeup
fuse: Fix use-after-free in fuse_dev_do_write()
fuse: Fix use-after-free in fuse_dev_do_read()
scsi: qla2xxx: Fix incorrect port speed being set for FC adapters
cdrom: fix improper type cast, which can leat to information leak.
9p: clear dangling pointers in p9stat_free
9p locks: fix glock.client_id leak in do_lock
media: tvp5150: fix width alignment during set_selection()
sc16is7xx: Fix for multi-channel stall
powerpc/boot: Ensure _zimage_start is a weak symbol
MIPS: kexec: Mark CPU offline before disabling local IRQ
media: pci: cx23885: handle adding to list failure
drm/omap: fix memory barrier bug in DMM driver
powerpc/nohash: fix undefined behaviour when testing page size support
tty: check name length in tty_find_polling_driver()
MD: fix invalid stored role for a disk - try2
btrfs: set max_extent_size properly
Btrfs: fix null pointer dereference on compressed write path error
btrfs: qgroup: Dirty all qgroups before rescan
Btrfs: fix wrong dentries after fsync of file that got its parent replaced
btrfs: make sure we create all new block groups
btrfs: reset max_extent_size on clear in a bitmap
btrfs: wait on caching when putting the bg cache
btrfs: don't attempt to trim devices that don't support it
btrfs: iterate all devices during trim, instead of fs_devices::alloc_list
btrfs: locking: Add extra check in btrfs_init_new_buffer() to avoid deadlock
btrfs: Handle owner mismatch gracefully when walking up tree
soc/tegra: pmc: Fix child-node lookup
arm64: dts: stratix10: Correct System Manager register size
Cramfs: fix abad comparison when wrap-arounds occur
ext4: avoid running out of journal credits when appending to an inline f

[Kernel-packages] [Bug 1810947] Re: Xenial update: 4.4.164 upstream stable release

[Juerg Haefliger]

List of previously applied patches:
  * cdrom: fix improper type cast, which can leat to information leak.
  * mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
  * mount: Retest MNT_LOCKED in do_umount
  * HID: hiddev: fix potential Spectre v1

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

Title:
  Xenial update: 4.4.164 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

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

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

  Linux 4.4.164
  drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values
  drm/dp_mst: Check if primary mstb is null
  drm/rockchip: Allow driver to be shutdown on reboot/kexec
  mm: migration: fix migration of huge PMD shared pages
  hugetlbfs: fix kernel BUG at fs/hugetlbfs/inode.c:444!
  configfs: replace strncpy with memcpy
  fuse: fix leaked notify reply
  rtc: hctosys: Add missing range error reporting
  sunrpc: correct the computation for page_ptr when truncating
  mount: Prevent MNT_DETACH from disconnecting locked mounts
  mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
  mount: Retest MNT_LOCKED in do_umount
  ext4: fix buffer leak in __ext4_read_dirblock() on error path
  ext4: fix buffer leak in ext4_xattr_move_to_block() on error path
  ext4: release bs.bh before re-using in ext4_xattr_block_find()
  ext4: fix possible leak of sbi->s_group_desc_leak in error path
  ext4: avoid possible double brelse() in add_new_gdb() on error path
  ext4: fix missing cleanup if ext4_alloc_flex_bg_array() fails while resizing
  ext4: avoid buffer leak in ext4_orphan_add() after prior errors
  ext4: fix possible inode leak in the retry loop of ext4_resize_fs()
  ext4: avoid potential extra brelse in setup_new_flex_group_blocks()
  ext4: add missing brelse() add_new_gdb_meta_bg()'s error path
  ext4: add missing brelse() in set_flexbg_block_bitmap()'s error path
  ext4: add missing brelse() update_backups()'s error path
  clockevents/drivers/i8253: Add support for PIT shutdown quirk
  Btrfs: fix data corruption due to cloning of eof block
  arch/alpha, termios: implement BOTHER, IBSHIFT and termios2
  termios, tty/tty_baudrate.c: fix buffer overrun
  mtd: docg3: don't set conflicting BCH_CONST_PARAMS option
  mm: thp: relax __GFP_THISNODE for MADV_HUGEPAGE mappings
  ocfs2: fix a misuse a of brelse after failing ocfs2_check_dir_entry
  vhost/scsi: truncate T10 PI iov_iter to prot_bytes
  mach64: fix image corruption due to reading accelerator registers
  mach64: fix display corruption on big endian machines
  libceph: bump CEPH_MSG_MAX_DATA_LEN
  clk: s2mps11: Fix matching when built as module and DT node contains 
compatible
  xtensa: fix boot parameters address translation
  xtensa: make sure bFLT stack is 16 byte aligned
  xtensa: add NOTES section to the linker script
  MIPS: Loongson-3: Fix BRIDGE irq delivery problem
  MIPS: Loongson-3: Fix CPU UART irq delivery problem
  bna: ethtool: Avoid reading past end of buffer
  e1000: fix race condition between e1000_down() and e1000_watchdog
  e1000: avoid null pointer dereference on invalid stat type
  mm: do not bug_on on incorrect length in __mm_populate()
  fs, elf: make sure to page align bss in load_elf_library
  mm: refuse wrapped vm_brk requests
  binfmt_elf: fix calculations for bss padding
  mm, elf: handle vm_brk error
  fuse: set FR_SENT while locked
  fuse: fix blocked_waitq wakeup
  fuse: Fix use-after-free in fuse_dev_do_write()
  fuse: Fix use-after-free in fuse_dev_do_read()
  scsi: qla2xxx: Fix incorrect port speed being set for FC adapters
  cdrom: fix improper type cast, which can leat to information leak.
  9p: clear dangling pointers in p9stat_free
  9p locks: fix glock.client_id leak in do_lock
  media: tvp5150: fix width alignment during set_selection()
  sc16is7xx: Fix for multi-channel stall
  powerpc/boot: Ensure _zimage_start is a weak symbol
  MIPS: kexec: Mark CPU offline before disabling local IRQ
  media: pci: cx23885: handle adding to list failure
  drm/omap: fix memory barrier bug in DMM driver
  powerpc/nohash: fix undefined behaviour when testing page size support
  tty: check name length in tty_find_polling_driver()
  MD: fix invalid stored role for a disk - try2
  btrfs: set max_extent_size properly
  Btrfs: fix null pointer dereference on compressed write path error
  btrfs: qgroup: Dirty all qgroups before rescan
  Btrfs: fix wrong dentries after f

Re: [Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU

[Alex Hung]

On Tue, Jan 8, 2019 at 4:20 AM Stefan Bader  wrote:
>
> And what about cosmic, too.

Thanks for the reminder. This should also apply to cosmic too.

>
> ** Also affects: linux (Ubuntu Bionic)
>Importance: Undecided
>Status: New
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Fix Committed => New
>
> ** Changed in: linux (Ubuntu Bionic)
>Status: New => Fix Committed
>
> ** Changed in: linux (Ubuntu Bionic)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1810702
>
> Title:
>   HP mobile workstations with hybrid graphics support, can not directly
>   output to external monitors by dGPU
>
> Status in linux package in Ubuntu:
>   New
> Status in linux source package in Bionic:
>   Fix Committed
>
> Bug description:
>   For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
> directly output to external monitors; however, Nvidia and AMD's Linux drivers 
> aren't able to support this feature.
>
>   The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to 
> implement dGPU direct output to external monitors.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810702/+subscriptions


-- 
Cheers,
Alex Hung

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

Title:
  HP mobile workstations with hybrid graphics support, can not directly
  output to external monitors by dGPU

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

Bug description:
  For HP Inc. mobile workstation with hybrid graphics support, dGPU can 
directly output to external monitors; however, Nvidia and AMD's Linux drivers 
aren't able to support this feature.
  
  The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement 
dGPU direct output to external monitors.

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

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

[Kernel-packages] [Bug 1810947] Re: Xenial update: 4.4.164 upstream stable release

[Juerg Haefliger]

Correction, the following patch has not been applied previously:
  * HID: hiddev: fix potential Spectre v1

There is an older commit with the same subject but different content,
hence the confusion.

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

Title:
  Xenial update: 4.4.164 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

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

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

  Linux 4.4.164
  drm/i915/hdmi: Add HDMI 2.0 audio clock recovery N values
  drm/dp_mst: Check if primary mstb is null
  drm/rockchip: Allow driver to be shutdown on reboot/kexec
  mm: migration: fix migration of huge PMD shared pages
  hugetlbfs: fix kernel BUG at fs/hugetlbfs/inode.c:444!
  configfs: replace strncpy with memcpy
  fuse: fix leaked notify reply
  rtc: hctosys: Add missing range error reporting
  sunrpc: correct the computation for page_ptr when truncating
  mount: Prevent MNT_DETACH from disconnecting locked mounts
  mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
  mount: Retest MNT_LOCKED in do_umount
  ext4: fix buffer leak in __ext4_read_dirblock() on error path
  ext4: fix buffer leak in ext4_xattr_move_to_block() on error path
  ext4: release bs.bh before re-using in ext4_xattr_block_find()
  ext4: fix possible leak of sbi->s_group_desc_leak in error path
  ext4: avoid possible double brelse() in add_new_gdb() on error path
  ext4: fix missing cleanup if ext4_alloc_flex_bg_array() fails while resizing
  ext4: avoid buffer leak in ext4_orphan_add() after prior errors
  ext4: fix possible inode leak in the retry loop of ext4_resize_fs()
  ext4: avoid potential extra brelse in setup_new_flex_group_blocks()
  ext4: add missing brelse() add_new_gdb_meta_bg()'s error path
  ext4: add missing brelse() in set_flexbg_block_bitmap()'s error path
  ext4: add missing brelse() update_backups()'s error path
  clockevents/drivers/i8253: Add support for PIT shutdown quirk
  Btrfs: fix data corruption due to cloning of eof block
  arch/alpha, termios: implement BOTHER, IBSHIFT and termios2
  termios, tty/tty_baudrate.c: fix buffer overrun
  mtd: docg3: don't set conflicting BCH_CONST_PARAMS option
  mm: thp: relax __GFP_THISNODE for MADV_HUGEPAGE mappings
  ocfs2: fix a misuse a of brelse after failing ocfs2_check_dir_entry
  vhost/scsi: truncate T10 PI iov_iter to prot_bytes
  mach64: fix image corruption due to reading accelerator registers
  mach64: fix display corruption on big endian machines
  libceph: bump CEPH_MSG_MAX_DATA_LEN
  clk: s2mps11: Fix matching when built as module and DT node contains 
compatible
  xtensa: fix boot parameters address translation
  xtensa: make sure bFLT stack is 16 byte aligned
  xtensa: add NOTES section to the linker script
  MIPS: Loongson-3: Fix BRIDGE irq delivery problem
  MIPS: Loongson-3: Fix CPU UART irq delivery problem
  bna: ethtool: Avoid reading past end of buffer
  e1000: fix race condition between e1000_down() and e1000_watchdog
  e1000: avoid null pointer dereference on invalid stat type
  mm: do not bug_on on incorrect length in __mm_populate()
  fs, elf: make sure to page align bss in load_elf_library
  mm: refuse wrapped vm_brk requests
  binfmt_elf: fix calculations for bss padding
  mm, elf: handle vm_brk error
  fuse: set FR_SENT while locked
  fuse: fix blocked_waitq wakeup
  fuse: Fix use-after-free in fuse_dev_do_write()
  fuse: Fix use-after-free in fuse_dev_do_read()
  scsi: qla2xxx: Fix incorrect port speed being set for FC adapters
  cdrom: fix improper type cast, which can leat to information leak.
  9p: clear dangling pointers in p9stat_free
  9p locks: fix glock.client_id leak in do_lock
  media: tvp5150: fix width alignment during set_selection()
  sc16is7xx: Fix for multi-channel stall
  powerpc/boot: Ensure _zimage_start is a weak symbol
  MIPS: kexec: Mark CPU offline before disabling local IRQ
  media: pci: cx23885: handle adding to list failure
  drm/omap: fix memory barrier bug in DMM driver
  powerpc/nohash: fix undefined behaviour when testing page size support
  tty: check name length in tty_find_polling_driver()
  MD: fix invalid stored role for a disk - try2
  btrfs: set max_extent_size properly
  Btrfs: fix null pointer dereference on compressed write path error
  btrfs: qgroup: Dirty all qgroups before rescan
  Btrfs: fix wrong dentries after fsync of file that got its parent replaced
  btrfs: make 

[Kernel-packages] [Bug 1810958] [NEW] Xenial update: 4.4.165 upstream stable release

[Juerg Haefliger]

Public bug reported:


SRU Justification

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

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


Linux 4.4.165
xhci: Fix USB3 NULL pointer dereference at logical disconnect.
HID: uhid: forbid UHID_CREATE under KERNEL_DS or elevated privileges
new helper: uaccess_kernel()
ACPI / platform: Add SMB0001 HID to forbidden_id_list
drivers/misc/sgi-gru: fix Spectre v1 vulnerability
USB: misc: appledisplay: add 20" Apple Cinema Display
misc: atmel-ssc: Fix section annotation on atmel_ssc_get_driver_data
usb: quirks: Add delay-init quirk for Corsair K70 LUX RGB
USB: quirks: Add no-lpm quirk for Raydium touchscreens
usb: cdc-acm: add entry for Hiro (Conexant) modem
uio: Fix an Oops on load
media: v4l: event: Add subscription to list before calling "add" operation
Revert "Bluetooth: h5: Fix missing dependency on BT_HCIUART_SERDEV"
Revert "media: videobuf2-core: don't call memop 'finish' when queueing"
btrfs: fix pinned underflow after transaction aborted
gfs2: Put bitmap buffers in put_super
SUNRPC: drop pointless static qualifier in xdr_get_next_encode_buffer()
zram: close udev startup race condition as default groups
lib/raid6: Fix arm64 test build
hwmon: (ibmpowernv) Remove bogus __init annotations
netfilter: xt_IDLETIMER: add sysfs filename checking routine
netfilter: ipset: Correct rcu_dereference() call in ip_set_put_comment()
s390/mm: Fix ERROR: "__node_distance" undefined!
netfilter: ipset: actually allow allowable CIDR 0 in hash:net,port,net
s390/vdso: add missing FORCE to build targets
arm64: percpu: Initialize ret in the default case
platform/x86: acerhdf: Add BIOS entry for Gateway LT31 v1.3307
clk: samsung: exynos5420: Enable PERIS clocks for suspend
fs/exofs: fix potential memory leak in mount option parsing
um: Give start_idle_thread() a return code
hfsplus: prevent btree data loss on root split
hfs: prevent btree data loss on root split
reiserfs: propagate errors from fill_with_dentries() properly
x86/build: Use cc-option to validate stack alignment parameter
x86/build: Fix stack alignment for CLang
x86/boot: #undef memcpy() et al in string.c
x86/build: Specify stack alignment for clang
x86/build: Use __cc-option for boot code compiler options
kbuild: Add __cc-option macro
x86/mm/kaslr: Use the _ASM_MUL macro for multiplication to work around Clang 
incompatibility
crypto, x86: aesni - fix token pasting for clang
x86/kbuild: Use cc-option to enable -falign-{jumps/loops}
arm64: Disable asm-operand-width warning for clang
kbuild: allow to use GCC toolchain not in Clang search path
kbuild: set no-integrated-as before incl. arch Makefile
kbuild: clang: disable unused variable warnings only when constant
kbuild: clang: remove crufty HOSTCFLAGS
kbuild: clang: fix build failures with sparse check
kbuild: move cc-option and cc-disable-warning after incl. arch Makefile
kbuild: Set KBUILD_CFLAGS before incl. arch Makefile
kbuild: fix linker feature test macros when cross compiling with Clang
efi/libstub/arm64: Set -fpie when building the EFI stub
efi/libstub/arm64: Force 'hidden' visibility for section markers
crypto: arm64/sha - avoid non-standard inline asm tricks
kbuild: clang: Disable 'address-of-packed-member' warning
modules: mark __inittest/__exittest as __maybe_unused
kbuild: Add support to generate LLVM assembly files
kbuild: use -Oz instead of -Os when using clang
kbuild, LLVMLinux: Add -Werror to cc-option to support clang
kbuild: drop -Wno-unknown-warning-option from clang options
kbuild: fix asm-offset generation to work with clang
kbuild: consolidate redundant sed script ASM offset generation
kbuild: Consolidate header generation from ASM offset information
kbuild: clang: add -no-integrated-as to KBUILD_[AC]FLAGS
kbuild: Add better clang cross build support
ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF
tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths
net-gro: reset skb->pkt_type in napi_reuse_skb()
ip_tunnel: don't force DF when MTU is locked
flow_dissector: do not dissect l4 ports for fragments

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update: 4.4.165 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  

[Kernel-packages] [Bug 1810548] Re: Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel 4.15

[Jeff Lane]

** Tags added: blocks-hwcert-server

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

Title:
  Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel
  4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug Description:
  This problem seems related to the following reported bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737934
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  System Configuration:
  The server is populated with hot swappable 1.9TB 7mm U.2 NVMe and 1.9TB 2.5” 
SSD SATA – either drives can serve as system boot drive. In addition, there’re 
twelve (12) 7TB 3.5” HDD SAS drives for data raid storage. Currently, the SSD 
SATA drive is used as file system boot device. Below is the lsb_release and cat 
/proc/cmdline output.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
  root=UUID=20881db9-36c3-4d83-9688-da36477e62e3 ro

  
  Problem:
  For both Xenial and Bionic running with kernel 4.15, the NVMe drive is having 
severe problems – the drive is intermittently disappearing with lsblk and nvme 
list commands, while spewing a lot of Buffer I/O errors on screen. The lspci 
output shows that the controller is disconnecting intermittently on the PCIe 
bus. 

  Symptom:
  At initial system’s boot up from fresh install, the NVMe drive will be 
recognized by lsblk, lspci and nvme list commands. Then the drive will go 
missing for no obvious reason then will appear again randomly, and this restart 
events will cycle continuously even the drive is at idle state. The output of 
dmesg, syslog and journal are all the same – it displays the unexpected 
shutdown of the drive. See below output. (for detailed text, see the attached 
dmesg, syslog and journalctl files)
  -
  [  485.296413] nvme nvme1: pci function :18:00.0
  [  485.296516] nvme :18:00.0: enabling device (0100 -> 0102)
  [  485.406992] nvme nvme1: Shutdown timeout set to 8 seconds
  [  485.409433] nvme nvme1: failed to mark controller state 1
  [  485.409435] nvme nvme1: Removing after probe failure status: 0
  -
  This symptom is present on both distro 16.04LTS and 18.04LTS running at 
kernel 4.15. The same symptom was evident at upstream kernels - 4.18.3 and 
4.18.19 as well.  

  Work-around:
  With kernel 4.19, this symptom does not manifest. It has fixed the random 
disconnection of NVMe controller over the PCIe bus. In addition, all the 
commands - i.e. lspci, lsblk, and nvme list will consistently display the drive 
without the occurrence of a missing NVMe drive during scan. 

  How to reproduce:
  1.Use Samsung U.2 NVME SM961/PM961 drive
  2.Install either Ubuntu 16.04.5 or 18.04.1 running at kernel 4.15
  3.Boot and wait until the file system recognized all the installed drives in 
the system. 
  4.Execute lsblk, lspci and nvme list command repeatedly. You will see, the 
NVMe drive will randomly go missing and will spew-out a lot of buffer IO 
errors. With 16.04.5LTS, the symptom is more severe. After fresh install, the 
drive will appear once, but once it goes missing, it will never come back again.

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Kai-Heng Feng]

Bas,

Please test this patch, thanks!

** Patch added: "0001-patch-for-LP-1790454.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5227688/+files/0001-patch-for-LP-1790454.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/1790454

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice:
   RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
   #RESUME=/dev/dm-2
   #RESUME=/dev/mapper/regan-swap
  InstallationDate: Installed on 2016-12-22 (619 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety 

[Kernel-packages] [Bug 1810548] Re: Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel 4.15

[Jeff Lane]

Hi Alec,

1: Please recreate this failure and then run 'apport-collect 1810548' as
requested, it will provide much more in the way of logs for this bug.

2: Is this applicable to ONLY this particular model NVMe or have you
seen this or can you recreate this on other models from this IHV, or
other NVMes in general? (knowing if this is limited to a single model or
is more widespread will help a lot).

3: Is the firmware on the NVMe at the latest version?  Just wondering if
a firmware update on the device would also address this (having no idea
why it's happening, that's really just a basic shot in the dark, I
realize it appears to be fixed in 4.19, which is great news, I'm just
covering all the bases here).


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

Title:
  Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel
  4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug Description:
  This problem seems related to the following reported bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737934
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  System Configuration:
  The server is populated with hot swappable 1.9TB 7mm U.2 NVMe and 1.9TB 2.5” 
SSD SATA – either drives can serve as system boot drive. In addition, there’re 
twelve (12) 7TB 3.5” HDD SAS drives for data raid storage. Currently, the SSD 
SATA drive is used as file system boot device. Below is the lsb_release and cat 
/proc/cmdline output.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
  root=UUID=20881db9-36c3-4d83-9688-da36477e62e3 ro

  
  Problem:
  For both Xenial and Bionic running with kernel 4.15, the NVMe drive is having 
severe problems – the drive is intermittently disappearing with lsblk and nvme 
list commands, while spewing a lot of Buffer I/O errors on screen. The lspci 
output shows that the controller is disconnecting intermittently on the PCIe 
bus. 

  Symptom:
  At initial system’s boot up from fresh install, the NVMe drive will be 
recognized by lsblk, lspci and nvme list commands. Then the drive will go 
missing for no obvious reason then will appear again randomly, and this restart 
events will cycle continuously even the drive is at idle state. The output of 
dmesg, syslog and journal are all the same – it displays the unexpected 
shutdown of the drive. See below output. (for detailed text, see the attached 
dmesg, syslog and journalctl files)
  -
  [  485.296413] nvme nvme1: pci function :18:00.0
  [  485.296516] nvme :18:00.0: enabling device (0100 -> 0102)
  [  485.406992] nvme nvme1: Shutdown timeout set to 8 seconds
  [  485.409433] nvme nvme1: failed to mark controller state 1
  [  485.409435] nvme nvme1: Removing after probe failure status: 0
  -
  This symptom is present on both distro 16.04LTS and 18.04LTS running at 
kernel 4.15. The same symptom was evident at upstream kernels - 4.18.3 and 
4.18.19 as well.  

  Work-around:
  With kernel 4.19, this symptom does not manifest. It has fixed the random 
disconnection of NVMe controller over the PCIe bus. In addition, all the 
commands - i.e. lspci, lsblk, and nvme list will consistently display the drive 
without the occurrence of a missing NVMe drive during scan. 

  How to reproduce:
  1.Use Samsung U.2 NVME SM961/PM961 drive
  2.Install either Ubuntu 16.04.5 or 18.04.1 running at kernel 4.15
  3.Boot and wait until the file system recognized all the installed drives in 
the system. 
  4.Execute lsblk, lspci and nvme list command repeatedly. You will see, the 
NVMe drive will randomly go missing and will spew-out a lot of buffer IO 
errors. With 16.04.5LTS, the symptom is more severe. After fresh install, the 
drive will appear once, but once it goes missing, it will never come back again.

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

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

[Kernel-packages] [Bug 1810548] Re: Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel 4.15

[Jeff Lane]

Ahhh, I just now realized you added a note to the certificate that ANY
NVMe drive will cause this failure...

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

Title:
  Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel
  4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug Description:
  This problem seems related to the following reported bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737934
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  System Configuration:
  The server is populated with hot swappable 1.9TB 7mm U.2 NVMe and 1.9TB 2.5” 
SSD SATA – either drives can serve as system boot drive. In addition, there’re 
twelve (12) 7TB 3.5” HDD SAS drives for data raid storage. Currently, the SSD 
SATA drive is used as file system boot device. Below is the lsb_release and cat 
/proc/cmdline output.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
  root=UUID=20881db9-36c3-4d83-9688-da36477e62e3 ro

  
  Problem:
  For both Xenial and Bionic running with kernel 4.15, the NVMe drive is having 
severe problems – the drive is intermittently disappearing with lsblk and nvme 
list commands, while spewing a lot of Buffer I/O errors on screen. The lspci 
output shows that the controller is disconnecting intermittently on the PCIe 
bus. 

  Symptom:
  At initial system’s boot up from fresh install, the NVMe drive will be 
recognized by lsblk, lspci and nvme list commands. Then the drive will go 
missing for no obvious reason then will appear again randomly, and this restart 
events will cycle continuously even the drive is at idle state. The output of 
dmesg, syslog and journal are all the same – it displays the unexpected 
shutdown of the drive. See below output. (for detailed text, see the attached 
dmesg, syslog and journalctl files)
  -
  [  485.296413] nvme nvme1: pci function :18:00.0
  [  485.296516] nvme :18:00.0: enabling device (0100 -> 0102)
  [  485.406992] nvme nvme1: Shutdown timeout set to 8 seconds
  [  485.409433] nvme nvme1: failed to mark controller state 1
  [  485.409435] nvme nvme1: Removing after probe failure status: 0
  -
  This symptom is present on both distro 16.04LTS and 18.04LTS running at 
kernel 4.15. The same symptom was evident at upstream kernels - 4.18.3 and 
4.18.19 as well.  

  Work-around:
  With kernel 4.19, this symptom does not manifest. It has fixed the random 
disconnection of NVMe controller over the PCIe bus. In addition, all the 
commands - i.e. lspci, lsblk, and nvme list will consistently display the drive 
without the occurrence of a missing NVMe drive during scan. 

  How to reproduce:
  1.Use Samsung U.2 NVME SM961/PM961 drive
  2.Install either Ubuntu 16.04.5 or 18.04.1 running at kernel 4.15
  3.Boot and wait until the file system recognized all the installed drives in 
the system. 
  4.Execute lsblk, lspci and nvme list command repeatedly. You will see, the 
NVMe drive will randomly go missing and will spew-out a lot of buffer IO 
errors. With 16.04.5LTS, the symptom is more severe. After fresh install, the 
drive will appear once, but once it goes missing, it will never come back again.

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

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

[Kernel-packages] [Bug 1810958] Re: Xenial update: 4.4.165 upstream stable release

[Juerg Haefliger]

Skipped the following commit:
  * Revert "Bluetooth: h5: Fix missing dependency on BT_HCIUART_SERDEV"

The commit that is reverted was never added to Xenial 4.4.

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

Title:
  Xenial update: 4.4.165 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

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

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

  
  Linux 4.4.165
  xhci: Fix USB3 NULL pointer dereference at logical disconnect.
  HID: uhid: forbid UHID_CREATE under KERNEL_DS or elevated privileges
  new helper: uaccess_kernel()
  ACPI / platform: Add SMB0001 HID to forbidden_id_list
  drivers/misc/sgi-gru: fix Spectre v1 vulnerability
  USB: misc: appledisplay: add 20" Apple Cinema Display
  misc: atmel-ssc: Fix section annotation on atmel_ssc_get_driver_data
  usb: quirks: Add delay-init quirk for Corsair K70 LUX RGB
  USB: quirks: Add no-lpm quirk for Raydium touchscreens
  usb: cdc-acm: add entry for Hiro (Conexant) modem
  uio: Fix an Oops on load
  media: v4l: event: Add subscription to list before calling "add" operation
  Revert "Bluetooth: h5: Fix missing dependency on BT_HCIUART_SERDEV"
  Revert "media: videobuf2-core: don't call memop 'finish' when queueing"
  btrfs: fix pinned underflow after transaction aborted
  gfs2: Put bitmap buffers in put_super
  SUNRPC: drop pointless static qualifier in xdr_get_next_encode_buffer()
  zram: close udev startup race condition as default groups
  lib/raid6: Fix arm64 test build
  hwmon: (ibmpowernv) Remove bogus __init annotations
  netfilter: xt_IDLETIMER: add sysfs filename checking routine
  netfilter: ipset: Correct rcu_dereference() call in ip_set_put_comment()
  s390/mm: Fix ERROR: "__node_distance" undefined!
  netfilter: ipset: actually allow allowable CIDR 0 in hash:net,port,net
  s390/vdso: add missing FORCE to build targets
  arm64: percpu: Initialize ret in the default case
  platform/x86: acerhdf: Add BIOS entry for Gateway LT31 v1.3307
  clk: samsung: exynos5420: Enable PERIS clocks for suspend
  fs/exofs: fix potential memory leak in mount option parsing
  um: Give start_idle_thread() a return code
  hfsplus: prevent btree data loss on root split
  hfs: prevent btree data loss on root split
  reiserfs: propagate errors from fill_with_dentries() properly
  x86/build: Use cc-option to validate stack alignment parameter
  x86/build: Fix stack alignment for CLang
  x86/boot: #undef memcpy() et al in string.c
  x86/build: Specify stack alignment for clang
  x86/build: Use __cc-option for boot code compiler options
  kbuild: Add __cc-option macro
  x86/mm/kaslr: Use the _ASM_MUL macro for multiplication to work around Clang 
incompatibility
  crypto, x86: aesni - fix token pasting for clang
  x86/kbuild: Use cc-option to enable -falign-{jumps/loops}
  arm64: Disable asm-operand-width warning for clang
  kbuild: allow to use GCC toolchain not in Clang search path
  kbuild: set no-integrated-as before incl. arch Makefile
  kbuild: clang: disable unused variable warnings only when constant
  kbuild: clang: remove crufty HOSTCFLAGS
  kbuild: clang: fix build failures with sparse check
  kbuild: move cc-option and cc-disable-warning after incl. arch Makefile
  kbuild: Set KBUILD_CFLAGS before incl. arch Makefile
  kbuild: fix linker feature test macros when cross compiling with Clang
  efi/libstub/arm64: Set -fpie when building the EFI stub
  efi/libstub/arm64: Force 'hidden' visibility for section markers
  crypto: arm64/sha - avoid non-standard inline asm tricks
  kbuild: clang: Disable 'address-of-packed-member' warning
  modules: mark __inittest/__exittest as __maybe_unused
  kbuild: Add support to generate LLVM assembly files
  kbuild: use -Oz instead of -Os when using clang
  kbuild, LLVMLinux: Add -Werror to cc-option to support clang
  kbuild: drop -Wno-unknown-warning-option from clang options
  kbuild: fix asm-offset generation to work with clang
  kbuild: consolidate redundant sed script ASM offset generation
  kbuild: Consolidate header generation from ASM offset information
  kbuild: clang: add -no-integrated-as to KBUILD_[AC]FLAGS
  kbuild: Add better clang cross build support
  ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF
  tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths
  net-gro: reset skb->pkt_type in napi_reuse_skb()
  ip_tunnel: don't force D

[Kernel-packages] [Bug 1810548] Re: Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel 4.15

[Jeff Lane]

Following that, this sounds like the "Cant use NVMes as the Root File-
system" issue.

So does this only affect this model Samsung NVMe, or all Samsung NVMes
or ALL NVMes (including other makes)?

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

Title:
  Samsung U.2 NVMe SM961/PM961 randomly will go missing under kernel
  4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug Description:
  This problem seems related to the following reported bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737934
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748

  System Configuration:
  The server is populated with hot swappable 1.9TB 7mm U.2 NVMe and 1.9TB 2.5” 
SSD SATA – either drives can serve as system boot drive. In addition, there’re 
twelve (12) 7TB 3.5” HDD SAS drives for data raid storage. Currently, the SSD 
SATA drive is used as file system boot device. Below is the lsb_release and cat 
/proc/cmdline output.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
  root=UUID=20881db9-36c3-4d83-9688-da36477e62e3 ro

  
  Problem:
  For both Xenial and Bionic running with kernel 4.15, the NVMe drive is having 
severe problems – the drive is intermittently disappearing with lsblk and nvme 
list commands, while spewing a lot of Buffer I/O errors on screen. The lspci 
output shows that the controller is disconnecting intermittently on the PCIe 
bus. 

  Symptom:
  At initial system’s boot up from fresh install, the NVMe drive will be 
recognized by lsblk, lspci and nvme list commands. Then the drive will go 
missing for no obvious reason then will appear again randomly, and this restart 
events will cycle continuously even the drive is at idle state. The output of 
dmesg, syslog and journal are all the same – it displays the unexpected 
shutdown of the drive. See below output. (for detailed text, see the attached 
dmesg, syslog and journalctl files)
  -
  [  485.296413] nvme nvme1: pci function :18:00.0
  [  485.296516] nvme :18:00.0: enabling device (0100 -> 0102)
  [  485.406992] nvme nvme1: Shutdown timeout set to 8 seconds
  [  485.409433] nvme nvme1: failed to mark controller state 1
  [  485.409435] nvme nvme1: Removing after probe failure status: 0
  -
  This symptom is present on both distro 16.04LTS and 18.04LTS running at 
kernel 4.15. The same symptom was evident at upstream kernels - 4.18.3 and 
4.18.19 as well.  

  Work-around:
  With kernel 4.19, this symptom does not manifest. It has fixed the random 
disconnection of NVMe controller over the PCIe bus. In addition, all the 
commands - i.e. lspci, lsblk, and nvme list will consistently display the drive 
without the occurrence of a missing NVMe drive during scan. 

  How to reproduce:
  1.Use Samsung U.2 NVME SM961/PM961 drive
  2.Install either Ubuntu 16.04.5 or 18.04.1 running at kernel 4.15
  3.Boot and wait until the file system recognized all the installed drives in 
the system. 
  4.Execute lsblk, lspci and nvme list command repeatedly. You will see, the 
NVMe drive will randomly go missing and will spew-out a lot of buffer IO 
errors. With 16.04.5LTS, the symptom is more severe. After fresh install, the 
drive will appear once, but once it goes missing, it will never come back again.

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

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

[Kernel-packages] [Bug 1810967] [NEW] Xenial update: 4.4.166 upstream stable release

[Juerg Haefliger]

Public bug reported:


SRU Justification

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

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


Linux 4.4.166
drm/ast: Remove existing framebuffers before loading driver
s390/mm: Check for valid vma before zapping in gmap_discard
namei: allow restricted O_CREAT of FIFOs and regular files
sched/core: Allow __sched_setscheduler() in interrupts when PI is not used
btrfs: Ensure btrfs_trim_fs can trim the whole filesystem
usb: xhci: fix uninitialized completion when USB3 port got wrong status
tty: wipe buffer if not echoing data
tty: wipe buffer.
iwlwifi: mvm: fix regulatory domain update when the firmware starts
scsi: qla2xxx: do not queue commands when unloading
scsi: ufshcd: release resources if probe fails
scsi: ufs: fix race between clock gating and devfreq scaling work
scsi: ufshcd: Fix race between clk scaling and ungate work
scsi: ufs: fix bugs related to null pointer access and array size
netfilter: nf_tables: fix oops when inserting an element into a verdict map
mwifiex: fix p2p device doesn't find in scan problem
mwifiex: Fix NULL pointer dereference in skb_dequeue()
cw1200: Don't leak memory if krealloc failes
Input: xpad - add support for Xbox1 PDP Camo series gamepad
Input: xpad - fix GPD Win 2 controller name
Input: xpad - add GPD Win 2 Controller USB IDs
Input: xpad - avoid using __set_bit() for capabilities
Input: xpad - fix some coding style issues
Input: xpad - add PDP device id 0x02a4
Input: xpad - add support for PDP Xbox One controllers
Input: xpad - validate USB endpoint type during probe
Input: xpad - fix PowerA init quirk for some gamepad models
Input: xpad - constify usb_device_id
Input: xpad - sync supported devices with XBCD
Input: xpad - sync supported devices with 360Controller
Input: xpad - add USB IDs for Mad Catz Brawlstick and Razer Sabertooth
Input: xpad - sync supported devices with xboxdrv
Input: xpad - sort supported devices by USB ID
Input: xpad - support some quirky Xbox One pads
Input: xpad - restore LED state after device resume
Input: xpad - fix stuck mode button on Xbox One S pad
Input: xpad - don't depend on endpoint order
Input: xpad - simplify error condition in init_output
Input: xpad - move reporting xbox one home button to common function
Input: xpad - correctly sort vendor id's
Input: xpad - fix Xbox One rumble stopping after 2.5 secs
Input: xpad - add product ID for Xbox One S pad
Input: xpad - power off wireless 360 controllers on suspend
Input: xpad - fix rumble on Xbox One controllers with 2015 firmware
Input: xpad - xbox one elite controller support
Input: xpad - add more third-party controllers
Input: xpad - prevent spurious input from wired Xbox 360 controllers
Input: xpad - add Mad Catz FightStick TE 2 VID/PID
Input: xpad - remove unused function
Input: xpad - correct xbox one pad device name
Input: xpad - use LED API when identifying wireless controllers
Input: xpad - workaround dead irq_out after suspend/ resume
Input: xpad - update Xbox One Force Feedback Support
Input: xpad - handle "present" and "gone" correctly
Input: xpad - remove spurious events of wireless xpad 360 controller
ath10k: fix kernel panic due to race in accessing arvif list
arm64: remove no-op -p linker flag
x86/entry/64: Remove %ebx handling from error_entry/exit
x86/entry: spell EBX register correctly in documentation
net: bcmgenet: fix OF child-node lookup
NFC: nfcmrvl_uart: fix OF child-node lookup
of: add helper to lookup compatible child node
tmpfs: make lseek(SEEK_DATA/SEK_HOLE) return ENXIO with a negative offset
powerpc/numa: Suppress "VPHN is not supported" messages
kdb: Use strscpy with destination buffer size
SUNRPC: Fix a bogus get/put in generic_key_to_expire()
cpufreq: imx6q: add return value check for voltage scale
KVM: PPC: Move and undef TRACE_INCLUDE_PATH/FILE
usb: xhci: Prevent bus suspend if a port connect change or polling state is 
detected
can: dev: __can_get_echo_skb(): print error message, if trying to echo non 
existing skb
can: dev: __can_get_echo_skb(): Don't crash the kernel if can_priv::echo_skb is 
accessed out of bounds
can: dev: __can_get_echo_skb(): replace struct can_frame by canfd_frame to 
access frame length
can: dev: can_get_echo_skb(): factor out non sending code to 
__can_get_echo_skb()
drm/ast: fixed cursor may disappear sometimes
drm/ast: change resolution may cause screen blurred
llc: do not use sk_eat_skb()
gfs2: Don't leave s_fs_info pointing to freed memory in init_sbd
sctp: clear the transport of some out_chunk_list chunks in sctp_assoc_rm_peer
bfs: add sanity check at bfs_fill

[Kernel-packages] [Bug 1809993] Re: Lenovo X1C6 trackpad functions broken

[Joshua Powers]

Let me know what to try or what I can provide

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice:
   RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
   #RESUME=/dev/dm-2
   #RESUME=/dev/mapper/regan-swap
  InstallationDate: Installed on 2016-12-22 (619 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.17.0-7-generic 
roo

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

[Łukasz Zemczak]

Hello Yoshee, or anyone else affected,

Accepted ubuntu-release-upgrader into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:18.10.11.3 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  Users who have manually configured and xorg.conf file with nvidia enabled as 
a driver will be surprised to have disabled on upgrade to a new release of 
Ubuntu and won't have a graphical display.

  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.

  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf

  When testing the release-upgrader from -proposed you'll need to use
  the -p switch to get the right tarball. Additionally, you'll want to
  add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia
  defaults to True instead of False (line 106) this'll simulate the
  nvidia driver being loaded.

  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.

  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py

[Kernel-packages] [Bug 1810821] Re: Cosmic update: 4.18.20 upstream stable release

[Kamal Mostafa]

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

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

Title:
  Cosmic update: 4.18.20 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification

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

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

  powerpc/traps: restore recoverability of machine_check interrupts
  powerpc/64/module: REL32 relocation range check
  powerpc/mm: Fix page table dump to work on Radix
  powerpc/mm: fix always true/false warning in slice.c
  drm/amd/display: fix bug of accessing invalid memory
  Input: wm97xx-ts - fix exit path
  powerpc/Makefile: Fix PPC_BOOK3S_64 ASFLAGS
  powerpc/eeh: Fix possible null deref in eeh_dump_dev_log()
  tty: check name length in tty_find_polling_driver()
  tracing/kprobes: Check the probe on unloaded module correctly
  drm/amdgpu/powerplay: fix missing break in switch statements
  ARM: imx_v6_v7_defconfig: Select CONFIG_TMPFS_POSIX_ACL
  powerpc/nohash: fix undefined behaviour when testing page size support
  powerpc/mm: Don't report hugepage tables as memory leaks when using kmemleak
  drm/omap: fix memory barrier bug in DMM driver
  drm/amd/display: fix gamma not being applied
  drm/hisilicon: hibmc: Do not carry error code in HiBMC framebuffer pointer
  media: pci: cx23885: handle adding to list failure
  media: coda: don't overwrite h.264 profile_idc on decoder instance
  MIPS: kexec: Mark CPU offline before disabling local IRQ
  powerpc/boot: Ensure _zimage_start is a weak symbol
  powerpc/memtrace: Remove memory in chunks
  MIPS/PCI: Call pcie_bus_configure_settings() to set MPS/MRRS
  sc16is7xx: Fix for multi-channel stall
  media: tvp5150: fix width alignment during set_selection()
  powerpc/selftests: Wait all threads to join
  staging:iio:ad7606: fix voltage scales
  drm: rcar-du: Update Gen3 output limitations
  drm/amdgpu: Fix SDMA TO after GPU reset v3
  staging: most: video: fix registration of an empty comp core_component
  9p locks: fix glock.client_id leak in do_lock
  udf: Prevent write-unsupported filesystem to be remounted read-write
  ARM: dts: imx6ull: keep IMX6UL_ prefix for signals on both i.MX6UL and 
i.MX6ULL
  9p: clear dangling pointers in p9stat_free
  ovl: fix error handling in ovl_verify_set_fh()
  ovl: check whiteout in ovl_create_over_whiteout()
  serial: sh-sci: Fix could not remove dev_attr_rx_fifo_timeout
  scsi: qla2xxx: Fix incorrect port speed being set for FC adapters
  scsi: qla2xxx: Fix process response queue for ISP26XX and above
  scsi: qla2xxx: Remove stale debug trace message from tcm_qla2xxx
  scsi: qla2xxx: shutdown chip if reset fail
  scsi: qla2xxx: Fix duplicate switch database entries
  scsi: qla2xxx: Fix driver hang when FC-NVMe LUNs are configured
  fuse: Fix use-after-free in fuse_dev_do_read()
  fuse: Fix use-after-free in fuse_dev_do_write()
  fuse: fix blocked_waitq wakeup
  fuse: set FR_SENT while locked
  ovl: fix recursive oi->lock in ovl_link()
  scsi: qla2xxx: Fix re-using LoopID when handle is in use
  scsi: qla2xxx: Fix NVMe session hang on unload
  arm64: dts: stratix10: Support Ethernet Jumbo frame
  arm64: dts: stratix10: fix multicast filtering
  clk: meson-gxbb: set fclk_div3 as CLK_IS_CRITICAL
  clk: meson: axg: mark fdiv2 and fdiv3 as critical
  zram: close udev startup race condition as default groups
  MIPS: Loongson-3: Fix CPU UART irq delivery problem
  MIPS: Loongson-3: Fix BRIDGE irq delivery problem
  xtensa: add NOTES section to the linker script
  xtensa: make sure bFLT stack is 16 byte aligned
  xtensa: fix boot parameters address translation
  um: Drop own definition of PTRACE_SYSEMU/_SINGLESTEP
  clk: s2mps11: Fix matching when built as module and DT node contains 
compatible
  clk: at91: Fix division by zero in PLL recalc_rate()
  clk: sunxi-ng: h6: fix bus clocks' divider position
  clk: rockchip: fix wrong mmc sample phase shift for rk3328
  clk: rockchip: Fix static checker warning in rockchip_ddrclk_get_parent call
  libceph: bump CEPH_MSG_MAX_DATA_LEN
  Revert "ceph: fix dentry leak in splice_dentry()"
  thermal: core: Fix use-after-free in thermal_cooling_device_destroy_sysfs
  mach64: fix display corruption on big endian machines
  mach64: fix image corruption due to reading accelerator registers
  acpi/nfit, x86/mce: Handle only uncorrectable machine checks
  acpi/nfit, x86/

[Kernel-packages] [Bug 1810818] Re: Cosmic update: 4.18.18 upstream stable release

[Kamal Mostafa]

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

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

Title:
  Cosmic update: 4.18.18 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification

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

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

  eeprom: at24: Add support for address-width property
  vfs: swap names of {do,vfs}_clone_file_range()
  bpf: fix partial copy of map_ptr when dst is scalar
  gpio: mxs: Get rid of external API call
  clk: sunxi-ng: sun4i: Set VCO and PLL bias current to lowest setting
  fscache: Fix incomplete initialisation of inline key space
  cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)
  fscache: Fix out of bound read in long cookie keys
  ptp: fix Spectre v1 vulnerability
  drm/edid: Add 6 bpc quirk for BOE panel in HP Pavilion 15-n233sl
  drm/edid: VSDB yCBCr420 Deep Color mode bit definitions
  drm: fb-helper: Reject all pixel format changing requests
  RDMA/ucma: Fix Spectre v1 vulnerability
  IB/ucm: Fix Spectre v1 vulnerability
  cdc-acm: do not reset notification buffer index upon urb unlinking
  cdc-acm: correct counting of UART states in serial state notification
  cdc-acm: fix race between reset and control messaging
  usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in vhci_hub_control()
  usb: gadget: storage: Fix Spectre v1 vulnerability
  usb: roles: intel_xhci: Fix Unbalanced pm_runtime_enable
  usb: xhci: pci: Enable Intel USB role mux on Apollo Lake platforms
  USB: fix the usbfs flag sanitization for control transfers
  tracing: Fix synthetic event to accept unsigned modifier
  tracing: Fix synthetic event to allow semicolon at end
  Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15IGM
  drm/sun4i: Fix an ulong overflow in the dotclock driver
  sched/fair: Fix throttle_list starvation with low CFS quota
  x86/tsc: Force inlining of cyc2ns bits
  x86, hibernate: Fix nosave_regions setup for hibernation
  x86/percpu: Fix this_cpu_read()
  x86/time: Correct the attribute on jiffies' definition
  x86/swiotlb: Enable swiotlb for > 4GiG RAM on 32-bit kernels
  x86/fpu: Fix i486 + no387 boot crash by only saving FPU registers on context 
switch if there is an FPU
  Linux 4.18.18

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

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

[Kernel-packages] [Bug 1810820] Re: Cosmic update: 4.18.19 upstream stable release

[Kamal Mostafa]

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

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

Title:
  Cosmic update: 4.18.19 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification

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

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

  mtd: rawnand: marvell: fix the IRQ handler complete() condition
  mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB
  mtd: spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash
  mtd: spi-nor: fsl-quadspi: Don't let -EINVAL on the bus
  spi: spi-mem: Adjust op len based on message/transfer size limitations
  spi: bcm-qspi: switch back to reading flash using smaller chunks
  spi: bcm-qspi: fix calculation of address length
  bcache: trace missed reading by cache_missed
  bcache: correct dirty data statistics
  bcache: fix miss key refill->end in writeback
  hwmon: (pmbus) Fix page count auto-detection.
  jffs2: free jffs2_sb_info through jffs2_kill_sb()
  block: setup bounce bio_sets properly
  block: don't deal with discard limit in blkdev_issue_discard()
  block: make sure discard bio is aligned with logical block size
  block: make sure writesame bio is aligned with logical block size
  cpufreq: conservative: Take limits changes into account properly
  dma-mapping: fix panic caused by passing empty cma command line argument
  pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges
  ACPI / OSL: Use 'jiffies' as the time bassis for acpi_os_get_timer()
  ACPICA: AML Parser: fix parse loop to correctly skip erroneous extended 
opcodes
  kprobes/x86: Use preempt_enable() in optimized_callback()
  mailbox: PCC: handle parse error
  acpi, nfit: Fix Address Range Scrub completion tracking
  parisc: Fix address in HPMC IVA
  parisc: Fix map_pages() to not overwrite existing pte entries
  parisc: Fix exported address of os_hpmc handler
  ALSA: hda - Add quirk for ASUS G751 laptop
  ALSA: hda - Fix headphone pin config for ASUS G751
  ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)
  ALSA: hda: Add 2 more models to the power_save blacklist
  ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
  x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
  x86/xen: Fix boot loader version reported for PVH guests
  x86/corruption-check: Fix panic in memory_corruption_check() when boot option 
without value is provided
  x86/mm/pat: Disable preemption around __flush_tlb_all()
  ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen
  drm: fix use of freed memory in drm_mode_setcrtc
  bpf: do not blindly change rlimit in reuseport net selftest
  nvme: remove ns sibling before clearing path
  Revert "perf tools: Fix PMU term format max value calculation"
  selftests: usbip: add wait after attach and before checking port status
  xsk: do not call synchronize_net() under RCU read lock
  xfrm: policy: use hlist rcu variants on insert
  perf vendor events intel: Fix wrong filter_band* values for uncore events
  r8169: Enable MSI-X on RTL8106e
  nfp: flower: fix pedit set actions for multiple partial masks
  nfp: flower: use offsets provided by pedit instead of index for ipv6
  sched/fair: Fix the min_vruntime update logic in dequeue_entity()
  perf evsel: Store ids for events with their own cpus 
perf_event__synthesize_event_update_cpus
  perf tools: Fix use of alternatives to find JDIR
  perf cpu_map: Align cpu map synthesized events properly.
  perf report: Don't crash on invalid inline debug information
  x86/fpu: Remove second definition of fpu in __fpu__restore_sig()
  net: qla3xxx: Remove overflowing shift statement
  r8169: re-enable MSI-X on RTL8168g
  drm: Get ref on CRTC commit object when waiting for flip_done
  selftests: ftrace: Add synthetic event syntax testcase
  i2c: rcar: cleanup DMA for all kinds of failure
  net: socionext: Reset tx queue in ndo_stop
  locking/lockdep: Fix debug_locks off performance problem
  netfilter: xt_nat: fix DNAT target for shifted portmap ranges
  ataflop: fix error handling during setup
  swim: fix cleanup on setup error
  arm64: cpufeature: ctr: Fix cpu capability check for late CPUs
  nfp: devlink port split support for 1x100G CXP NIC
  tun: Consistently configure generic netdev params via rtnetlink
  s390/sthyi: Fix machine name validity indication
  hwmon: (p

[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package update-notifier - 3.168.10

---
update-notifier (3.168.10) xenial; urgency=medium

  [ Julian Andres Klode ]
  * Do not notify-reboot-required on linux-image-extra removal (LP: #1458204)

 -- Balint Reczey   Fri, 07 Dec 2018 11:14:24 +0100

** Changed in: update-notifier (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

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

[Kernel-packages] [Bug 1458204] Update Released

[Brian Murray]

The verification of the Stable Release Update for update-notifier has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

[kao]

As soon as it seems that the issue has been resolved, something bad occurs 
again.
Right now my laptop woke up without bluetooth (but with wifi). No 
dpm_run_callback trail though.

Could it be related to bug #1766825 (bluetooth missing after suspend)

** Attachment added: "dmesg.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988/+attachment/5227702/+files/dmesg.log.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/1799988

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1810238] Re: 4.15.0-43 back screen of death :)

[Joseph Salisbury]

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS440
  dmi.product.version: 70AQ0009UX
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892

[Luca Mastromatteo]

Seems to be the same problem as 
https://bugzilla.kernel.org/show_bug.cgi?id=195303
With ALC1220 codecs

The last comment was


 "I might have found the source of this problem at least for me. A while
ago I set my Pulseaudio sample rate to 44100 to reduce crackling in my
virtual machine audio but the sound card on my board runs at 48000.

What I did:
arecord --list-devices
arecord -f dat -r 6 -D hw:CARDIDHERE,DEVICEIDHERE -d 5 test.wav

arecord told me that it could not record of a rate of 6 and instead
got 48000. This means my card has a sample rate of 48000

So I ran:
arecord -f dat -r 48000 -D hw:1,0 -d 5 test.wav

And suddenly I had a clear recording! The only problem is I have changed
my sampling rate and alternate sample rate in /etc/pulse/daemon.conf
back to 48000 but it still seems to be defaulting to 44100 in all
programs.

If I run:
arecord -f cd -d 10 test-mic.wav
I observe it defaulting to 44100 and playing it back sounds awful again. Same 
with any other recording software, they are all still using 44100 for some 
reason which is causing the crackling."


This also applies to me, is there a temporary workaround for that I can
apply to ALSA or Pulseaudio?

** Bug watch added: Linux Kernel Bug Tracker #195303
   https://bugzilla.kernel.org/show_bug.cgi?id=195303

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

Title:
  Microphone distorted sound on ALC892

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

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Kernel-packages] [Bug 1810210] Re: Kernel 4.15.0-43 crashes laptop on boot

[Joseph Salisbury]

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 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 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-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/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  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.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1809993] Re: Lenovo X1C6 trackpad functions broken

[Joseph Salisbury]

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

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

Title:
  Lenovo X1C6 trackpad functions broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Summary:
  After kernel update the trackpad advanced functions, like two finger 
scrolling and mouse acceleration have stopped working.

  Expected Result:
  Two finer scroll works and the mouse has acceleration features work

  Actual Result:
  Two finer scroll works and the mouse has acceleration features do not work

  Steps to reproduce:
  1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 
11/08/2018)
  2. Install 18.04 LTS
  3. config-4.15.0-42-generic acceleration works, while 
config-4.15.0-43-generic does not

  This appears to be some sort of regression or change in behavior between 
kernel versions.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  powersj1597 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7
  InstallationDate: Installed on 2018-12-06 (22 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KHCTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1810108] Re: Failure to boot as QEMU guest when using -device virtio-vga, virgl=true

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/


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

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

Title:
  Failure to boot as QEMU guest when using -device virtio-vga,virgl=true

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed Xubuntu 18.04 in a QEMU virtual machine using -device
  virtio-vga,virgl=true fails to boot. Even setting to output boot
  messages to a serial console no messages appear as if it never tried
  to boot at all.

  What makes this strange is that the live media works correctly using
  -device virtio-vga,virgl=true, but then, on reboot, the installed
  system fails to boot.

  To make the guest work it's required to remove the option ,virgl=true
  from the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Dec 30 17:33:21 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230)
  IwConfig:
   ens2  no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1809841] Re: Touchpad showing as PS/2 Generic Mouse

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/

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

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

Title:
  Touchpad showing as PS/2 Generic Mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad on my HP 1011 Elite X2 G1 is showing as a PS/2 mouse
  after installation in xinput. Multitouch gestures do not work and
  installing xserver-xorg-input-synaptics did not resolve the issue. The
  touch pad uses the Synaptics driver in Windows 10.

  Other functionalities of the keyboard do work such as
  enabling/disabling wireless and volume up/down.

  The touchpad should be able to use multitouch for two-finger scrolling
  and two-finger tap for right click but instead only single touch
  inputs are accepted for left and right click. No multitouch gestures
  are recognized.

  Current version is Ubuntu 4.15.0-43.46-generic 4.15.18 on Ubuntu
  18.04.1 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   johnny 1379 F...m pulseaudio
   /dev/snd/controlC0:  johnny 1379 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 19:31:50 2018
  InstallationDate: Installed on 2018-12-21 (5 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP Elite x2 1011 G1 Tablet
  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=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=0d10c1f2-6c44-4717-a4df-73b592d11fe3 ro i8042.reset quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M72 Ver. 01.25
  dmi.board.name: 2009
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 79.61
  dmi.chassis.asset.tag: 5CG5465MYV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM72Ver.01.25:bd10/30/2018:svnHewlett-Packard:pnHPElitex21011G1Tablet:pvrA3009FD10303:rvnHewlett-Packard:rn2009:rvrKBCVersion79.61:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP Elite x2 1011 G1 Tablet
  dmi.product.version: A3009FD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

** Tags removed: 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/1791758

Title:
  ldisc crash on reopened tty

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:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
  [684766.669194] Oops:  [#1] SMP
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  [Test Case]

  * Deploy a Trusty KVM instance with a LTS Xenial kernel (v4.4 series)
  * SSH in frequently while system is under load, send commands before the 
prompt has returned.
  

  Check comment #5 for a summary about the upstream proposals to resolve
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu

Re: [Kernel-packages] [Bug 1810238] Re: 4.15.0-43 back screen of death :)

[rpetrusevski]

Hi Joseph,

I looked at the link to enableProposed but the info seems to be for
16.04, I am on Mint 19.1 (18.04). Also, after I submitted the issue, I
tested different versions on nvidia drivers, as I did experienced the
chrash again with 4.15.0-42 while using nvidia 415 driver. I rolled to
410 and that worked little bit and crashed again. Then I rolled on
396.54 and it seems more stable.

Sincerly
Robert
On Jan 8 2019, at 9:54 am, Joseph Salisbury  
wrote:
Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed.

Thank you in advance!

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

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

Title:
4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
Incomplete

Bug description:
crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: rp 4614 F pulseaudio
/dev/snd/controlC1: rp 4614 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19.1
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
InstallationDate: Installed on 2018-07-03 (183 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
MachineType: LENOVO ThinkServer TS440
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-42-generic N/A
linux-backports-modules-4.15.0-42-generic N/A
linux-firmware 1.173.2
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: tessa
Uname: Linux 4.15.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo ubridge
_MarkForUpload: True
dmi.bios.date: 04/10/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKTCEAUS
dmi.board.name: ThinkServer TS440
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.type: 7
dmi.chassis.vendor: LENOVO
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTCEAUS:bd04/10/2017:svnLENOVO:pnThinkServerTS440:pvr70AQ0009UX:rvnLENOVO:rnThinkServerTS440:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: ThinkServer TS440
dmi.product.version: 70AQ0009UX
dmi.sys.vendor: LENOVO

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

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

Title:
  4.15.0-43 back screen of death :)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  crashes the whole system when playing a game (I have nvidia). Rolled back to 
4.15.0-42 everything works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rp 4614 F pulseaudio
   /dev/snd/controlC1:  rp 4614 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3ee4cc45-4d22-42ae-abe7-692ff96391c3
  InstallationDate: Installed on 2018-07-03 (183 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO ThinkServer TS440
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=8dee5144-332c-4f2b-9dee-4cdd173451f9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev roccat sambashare sudo 
ubridge
  _MarkForUpload: True
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTCEAUS
  dmi.board.name: ThinkServer TS440
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.vers

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

** Description changed:

  [Impact]
  
- The following Oops was discovered by user:
+ * Line discipline code is racy when we have buffer being flush while the
+ tty is being initialized or reinitialized. For the first problem, we
+ have an upstream patch since January 2018: b027e2298bd5 ("tty: fix data
+ race between tty_init_dev and flush of buf") - although it is not in
+ Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.
  
- [684766.39] BUG: unable to handle kernel paging request at 
2268
- [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
- [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
- [684766.669194] Oops:  [#1] SMP
- [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
- [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
- [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
- [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
- [684766.686062] Workqueue: events_unbound flush_to_ldisc
- [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
- [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
- [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
- [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
- [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
- [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
- [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
- [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
- [684766.694390] FS:  () GS:8819d73c() 
knlGS:
- [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
- [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
- [684766.697141] DR0:  DR1:  DR2: 

- [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
- [684766.699079] Stack:
- [684766.699412]   8819c2d3d4d8  
8819c2d3d648
- [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
- [684766.701501]  88170dc2fd78 0001  
88162c895020
- [684766.702534] Call Trace:
- [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
- [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
- [684766.704505]  [] flush_to_ldisc+0xd5/0x120
- [684766.705269]  [] process_one_work+0x156/0x400
- [684766.706008]  [] worker_thread+0x11a/0x480
- [684766.706686]  [] ? rescuer_thread+0x310/0x310
- [684766.707386]  [] kthread+0xd8/0xf0
- [684766.707993]  [] ? kthread_park+0x60/0x60
- [684766.708664]  [] ret_from_fork+0x55/0x80
- [684766.709335]  [] ? kthread_park+0x60/0x60
- [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00
- [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
- [684766.714105]  RSP 
- [684766.714609] CR2: 2268
+ * For the race between the buffer flush while tty is being reopened, we
+ have a patch that addresses this issue recently merged for 5.0-rc1:
+ 83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
+ Ubuntu kernel currently contains this patch, hence we're hereby
+ submitting the SRU request. The upstream complete patch series for this
+ is in [0].
  
- The issue happened in a VM
- KDUMP was configured, so a full Kernel crashdump was created
+ * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
+ necessary to prevent correlated issu

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

** Description changed:

  [Impact]
  
  * Line discipline code is racy when we have buffer being flush while the
  tty is being initialized or reinitialized. For the first problem, we
  have an upstream patch since January 2018: b027e2298bd5 ("tty: fix data
  race between tty_init_dev and flush of buf") - although it is not in
  Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.
  
  * For the race between the buffer flush while tty is being reopened, we
  have a patch that addresses this issue recently merged for 5.0-rc1:
  83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
  Ubuntu kernel currently contains this patch, hence we're hereby
  submitting the SRU request. The upstream complete patch series for this
  is in [0].
  
  * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
  necessary to prevent correlated issues, like preventing a potential deadlock 
due to bad prioritization in servicing I/O over releasing
  tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc 
change is pending"). All the necessary fixes are grouped here in this SRU 
request.
  
  * The symptom of the race condition between the buffer flush and the tty
  reopen routine is a kernel crash with the following trace:
  
  BUG: unable to handle kernel paging request at 2268
  IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [...]
  Call Trace:
  [] ? kvm_sched_clock_read+0x1e/0x30
  [] n_tty_receive_buf2+0x14/0x20
  [] flush_to_ldisc+0xd5/0x120
  [] process_one_work+0x156/0x400
  [] worker_thread+0x11a/0x480
  [...]
  
  * A kernel crash was collected from an user, analysis is present in
  comment #4 in this LP.
  
- 
  [Test Case]
  
  * It is not trivial to trigger this fault, but the usual recipe is to
- keep accessing a machine through SSH (or IPMI serial console) and in
- some way run commands before the terminal is ready in that machine (like
- hacking some echo into ttySx or pts in an infinite loop).
+ keep accessing a machine through SSH (or keep killing getty when in IPMI
+ serial console) and in some way run commands before the terminal is
+ ready in that machine (like hacking some echo into ttySx or pts in an
+ infinite loop).
  
  * We have reports of users that could reproduce this issue in their
  production environment, and with the patches present in this SRU request
  the problem was fixed.
- 
  
  [Regression Potential]
  
  * tty subsystem is highly central and patches in that area are always
  delicate. For example, the upstream series [0] is a re-spin (V6) due to
  a hard to reproduce issue reported in the PA-RISC architecture, which
  was found in the V5 iteration [1] but was fixed by the patch
  c96cf923a98d, present in this SRU request.
  
  * The patchset [0] is present in tty-next tree since mid-November, and
  the patch b027e2298bd5 is available upstream since January/2018 (it's
  available in both Ubuntu kernels 4.15 and 4.18), so the overall
  likelihood of regressions is low.
  
  * These patches were sniff-tested for the 3 versions (4.4, 4.15 and
  4.18) and didn't show any issues.
  
- 
  [0] https://marc.info/?l=linux-kernel&m=154103190111795
  [1] https://marc.info/?l=linux-kernel&m=153737852618183

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

Title:
  ldisc crash on reopened tty

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:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  * Line discipline code is racy when we have buffer being flush while
  the tty is being initialized or reinitialized. For the first problem,
  we have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
  data race between tty_init_dev and flush of buf") - although it is not
  in Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.

  * For the race between the buffer flush while tty is being reopened,
  we have a patch that addresses this issue recently merged for 5.0-rc1:
  83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
  Ubuntu kernel currently contains this patch, hence we're hereby
  submitting the SRU request. The upstream complete patch series for
  this is in [0].

  * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
  necessary to prevent correlated issues, like preventing a potential deadlock 
due to bad prioritization in servicing I/O over releasing
  tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc 
change is pending"). All the necessary fixes are grouped here in this SRU 
request.

  * The symptom of the race condition

[Kernel-packages] [Bug 1690085]

[brauliobo]

(In reply to Another User from comment #463)
> I have random freezes with Ryzen 2200u laptop. Display image just freezes
> and system stops responding. Only way to get out from this state is to
> holding power button (even magic SysRq key does not work). No any clues in
> logs.
> 
> With Ubuntu 18.04 it was happen nearly once per week (not intense use).
> After installing 18.10 things become more stable - I've got first lockup
> after 6 weeks and another after 3. Hangs are completely random and on
> different cpu load - once I've got this while gaming (and ambient noise
> continue playing...)
> 
> I've tried idle=nomwait but this did not help on 18.04 - and line
> "monitor-mwait will be used for idle loop" was still present in dmesg with
> this parameter!
> 
> idle=halt parameter completely disables mwait instruction in kernel and also
> forces use of only C1 state. In my laptop it does not cause higher battery
> drain or any suspend-resume issues. But I've not tested it completely an
> used it for few days... So this may be even not the solution for my problem.

You freeze seems GPU related, try a new kernel/firmware

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Brian Murray]

Hello Hui, or anyone else affected,

Accepted alsa-lib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.3-5ubuntu0.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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

[Kernel-packages] [Bug 1690085]

[ricki]

Have these lockups with Fedora 29 default kernel and AMD Ryzen 7 1700X
Eight-Core Processor.

Kernel parameter "idle=nomwait" does not help, but the disable C6 script
does...

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about thi

[Kernel-packages] [Bug 1690085]

[to_load]

(In reply to Bráulio Bhavamitra from comment #464)
> You freeze seems GPU related, try a new kernel/firmware

I also have got amdgpu crash with same screen freeze, but magic key had
worked that time and error left in kernel log. And I was able reproduce
that with certain game in dolphin emulator.

My random freezes happened without any special program running,
sometimes in clear gnome-shell desktop. But this never happens just
after power on - only after some working time.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=

[Kernel-packages] [Bug 1690085]

[to_load]

I have random freezes with Ryzen 2200u laptop. Display image just
freezes and system stops responding. Only way to get out from this state
is to holding power button (even magic SysRq key does not work). No any
clues in logs.

With Ubuntu 18.04 it was happen nearly once per week (not intense use).
After installing 18.10 things become more stable - I've got first lockup
after 6 weeks and another after 3. Hangs are completely random and on
different cpu load - once I've got this while gaming (and ambient noise
continue playing...)

I've tried idle=nomwait but this did not help on 18.04 - and line
"monitor-mwait will be used for idle loop" was still present in dmesg
with this parameter!

idle=halt parameter completely disables mwait instruction in kernel and
also forces use of only C1 state. In my laptop it does not cause higher
battery drain or any suspend-resume issues. But I've not tested it
completely an used it for few days... So this may be even not the
solution for my problem.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed

[Kernel-packages] [Bug 1797587] Re: Intel NVMe drives timeout when nvme format is attempted

[Joseph Salisbury]

** Description changed:

+ == SRU Justification ==
+ Dell reports that every time they run a nvme format on an Intel
+ NVMe drive (whether specifying the secure/crypto erase options or not), the
+ format apparently works (drive is wiped clean). The drive's admin queue
+ (queue 0) times out, making the nvme device driver flag an error and reset 
the controller.
+ 
+ This bug is fixed by commit 62843c2e4226, which is in mainline as of
+ v4.17-rc1.
+ 
+ == Fix ==
+ 62843c2e4226 ("nvme: Use admin command effects for admin commands")
+ 
+ == Regression Potential ==
+ Low.  Limited to nvme driver.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
  Every time you run an nvme format on a Intel NVMe drive (whether
  specifying the secure/crypto erase options or not), the format
  apparently works (drive is wiped clean) but the drive's admin queue
  (queue 0) times out, making the nvme device driver flag an error and
  reset the controller.
  
  Here's an example:
-  
+ 
  nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1
  NVME Admin command error:ABORT_REQ(7)
  nvme-cli-1.5 # dmesg|tail -1
  [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller
  
  Patch required:
  
https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331
  
  Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04

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

Title:
  Intel NVMe drives timeout when nvme format is attempted

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  Dell reports that every time they run a nvme format on an Intel
  NVMe drive (whether specifying the secure/crypto erase options or not), the
  format apparently works (drive is wiped clean). The drive's admin queue
  (queue 0) times out, making the nvme device driver flag an error and reset 
the controller.

  This bug is fixed by commit 62843c2e4226, which is in mainline as of
  v4.17-rc1.

  == Fix ==
  62843c2e4226 ("nvme: Use admin command effects for admin commands")

  == Regression Potential ==
  Low.  Limited to nvme driver.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  Every time you run an nvme format on a Intel NVMe drive (whether
  specifying the secure/crypto erase options or not), the format
  apparently works (drive is wiped clean) but the drive's admin queue
  (queue 0) times out, making the nvme device driver flag an error and
  reset the controller.

  Here's an example:

  nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1
  NVME Admin command error:ABORT_REQ(7)
  nvme-cli-1.5 # dmesg|tail -1
  [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller

  Patch required:
  
https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331

  Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1797587/+subscriptions

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

[Joseph Salisbury]

** Changed in: linux-azure (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev&id=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1797587] Re: Intel NVMe drives timeout when nvme format is attempted

[Joseph Salisbury]

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-January/097553.html

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

Title:
  Intel NVMe drives timeout when nvme format is attempted

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  Dell reports that every time they run a nvme format on an Intel
  NVMe drive (whether specifying the secure/crypto erase options or not), the
  format apparently works (drive is wiped clean). The drive's admin queue
  (queue 0) times out, making the nvme device driver flag an error and reset 
the controller.

  This bug is fixed by commit 62843c2e4226, which is in mainline as of
  v4.17-rc1.

  == Fix ==
  62843c2e4226 ("nvme: Use admin command effects for admin commands")

  == Regression Potential ==
  Low.  Limited to nvme driver.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  Every time you run an nvme format on a Intel NVMe drive (whether
  specifying the secure/crypto erase options or not), the format
  apparently works (drive is wiped clean) but the drive's admin queue
  (queue 0) times out, making the nvme device driver flag an error and
  reset the controller.

  Here's an example:

  nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1
  NVME Admin command error:ABORT_REQ(7)
  nvme-cli-1.5 # dmesg|tail -1
  [79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller

  Patch required:
  
https://github.com/torvalds/linux/commit/62843c2e4226057c83f520c74fe9c81a1891c331

  Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1797587/+subscriptions

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

[Kernel-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

[Nicholas Johnson]

apport information

** Tags added: apport-collected cosmic

** Description changed:

- I use a logitech z200 that works fine, i use it with a usb type c
- adapter that came with my pixel 3, my speakers arent shown at all in the
- settings or make sound, its not the usb c adapter because it works fine
- on my windows dual boot and has worked at one point on ubuntu,
- regardless of the fact that ubuntu has never recognized my thunderbolt
- port, i use ubuntu 18.10 by the way when i use lsusb, one of the results
- is google inc., which is my headphone adapter, i can tell because when i
- unplug it it goes away, even when i plug it into the 3.5 mm headphone
- jack it doesn't work, i don't know if im forgetting something or not,
- this is the second time im typing this because i accidentally closed the
- first tab of this, whats interesting, is now that i go to alsamixer, and
- press f6 i see option 1.Headphone Adapter, i select it and set the
- volume all the way up and go to something that makes audio and nothing
- happens, then i unplug it and see if it disappears, surely enough it
- does
+ I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-10-21 (78 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp37s0   no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: pulseaudio 1:12.2-0ubuntu4
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-13-generic N/A
+  linux-backports-modules-4.18.0-13-generic  N/A
+  linux-firmware 1.175.1
+ RfKill:
+  
+ Tags:  cosmic
+ Uname: Linux 4.18.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 07/05/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P5.00
+ dmi.board.name: AB350 Gaming K4
+ dmi.board.vendor: ASRock
+ 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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227724/+files/AlsaInfo.txt

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

Title:
  USB

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

[Nicholas Johnson]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227725/+files/CRDA.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicholas Johnson]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227730/+files/ProcCpuinfoMinimal.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1810861] Dependencies.txt

[Nicholas Johnson]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227727/+files/Dependencies.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicholas Johnson]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227726/+files/CurrentDmesg.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicholas Johnson]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227729/+files/Lsusb.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicholas Johnson]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227728/+files/Lspci.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicholas Johnson]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1810861/+attachment/5227733/+files/UdevDb.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1799388] Re: TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  TM (Hardware Transactional Memory) instructions halt application on
  baremetal POWER9 DD2.1

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-10-15 
08:55:55 ==
  +++ This bug was initially created as a clone of Bug #167756 +++

  ---Problem Description---
  TM (Hardware Transactional Memory) instructions halt application on baremetal 
POWER9 DD2.1
   
  Contact Information = grom...@br.ibm.com 
   
  ---Additional Hardware Info---
  POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon. 

   
  Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr 
004e 1201) with the latest firmware [1] (Firmware level [2] was also tested 
with the same result) and running Linux from Linus' upstream tree [3] or 
powerpc/next branch [4] is not working as expected. Once a TM instruction is 
executed in a process (any instruction), the process halts completely and has 
to be killed.

  A simple test case is to execute a 'tend.' which accordingly to POWER8
  behaviour and the ISA v3.00 if executed "in Non-transactional state is
  treated as a no-op." [5]. It means that the instruction in the test
  case below should be treated simply as a 'nop' instruction and the
  process would terminate normally but instead it halts and the process
  never terminates:

  root@io83:~/gromero# cat t.c
  int main() { asm ("tend.;"); }
  root@io83:~/gromero# make t
  make: 't' is up to date.
  root@io83:~/gromero# ./t
  ^C
  

  Ubuntu stock kernel 4.15.0-20-generic was also tested with the same
  result.

  I confirmed with Erich Hauptli (FW team) that FW stack levels [1]
  contain all the TM fixes we have at the moment.

  Thus, that issue affects any application that uses TM on a baremetal
  POWER9 DD2.1 (pvr 004e 1201).

  
  [1] 
  IBM-witherspoon-ibm-OP9_v1.19_1.160
  op-build-v1.21.2-255-g6ad1636-dirty
  buildroot-2017.11-5-g65679be
  skiboot-v5.10.5-op910-1
  hostboot-ed53939
  linux-4.14.24-openpower1-paed97e8
  petitboot-v1.6.6-p41a158a
  machine-xml-4af
  occ-ef5d466
  hostboot-binaries-6a92b6d
  capp-ucode-p9-dd2-v3
  sbe-7e02c23

  [2]
  open-power-witherspoon-v1.22-82-gebe1295-dirty
buildroot-2018.02.1-6-ga8d11267c2
skiboot-v6.0-rc1
hostboot-d9bf361-p6755b85
occ-f741c41
linux-4.16.7-openpower1-p945838d
petitboot-v1.7.1-pd695626
machine-xml-7cd20a6
hostboot-binaries-53aece6
capp-ucode-p9-dd2-v4
sbe-8e0105e
hcode-hw050318a.op920

  [3] https://github.com/torvalds/linux.git (master)
  [4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next) 
  [5] Power ISA - Book II, p. 894
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: any tool using TM instruction set 

  Userspace rpm: not relevant 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for grom...@br.ibm.com: 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  The following patch fixes this issue:

  http://patchwork.ozlabs.org/patch/968375/

  Author: Michael Neuling 
  Date:   Tue Sep 11 13:07:56 2018 +1000

  powerpc/tm: Fix HFSCR bit for no suspend case
  
  Currently on P9N DD2.1 we end up taking infinite TM facility
  unavailable exceptions on the first TM usage by userspace.
  
  In the special case of TM no suspend (P9N DD2.1), Linux is told TM is
  off via CPU dt-ftrs but told to (partially) use it via
  OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED. So HFSCR[TM] will be off from
  dt-ftrs but we need to turn it on for the no suspend case.
  
  This patch fixes this by enabling HFSCR TM in this case.
  
  Cc: sta...@vger.kernel.org # 4.15+
  Signed-off-by: Michael Neuling 

  == Comment: #2 - Michael Ranweiler  - 2018-10-15 
13:52:13 ==
  This is in the powerpc 

[Kernel-packages] [Bug 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  powerpc/powernv/pci: Work around races in PCI bridge enabling

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-08-21 
13:52:03 ==
  +++ This bug was initially created as a clone of Bug #170766 +++

  Please apply the following kernel patch:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=db2173198b9513f7add8009f225afa1f1c79bcc6

  powerpc/powernv/pci: Work around races in PCI bridge enabling

  The generic code is racy when multiple children of a PCI bridge try to
  enable it simultaneously.

  This leads to drivers trying to access a device through a
  not-yet-enabled bridge, and this EEH errors under various
  circumstances when using parallel driver probing.

  There is work going on to fix that properly in the PCI core but it
  will take some time.

  x86 gets away with it because (outside of hotplug), the BIOS enables
  all the bridges at boot time.

  This patch does the same thing on powernv by enabling all bridges that
  have child devices at boot time, thus avoiding subsequent races. It's
  suitable for backporting to stable and distros, while the proper PCI
  fix will probably be significantly more invasive.

  Signed-off-by: Benjamin Herrenschmidt 
  Cc: sta...@vger.kernel.org
  Signed-off-by: Michael Ellerman 

  == Comment: #2 - Michael Ranweiler  - 2018-08-21 
18:23:35 ==
  This has some fuzz and also move it back from the pci macro to dev_err so 
we'll attach the backported patch.

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

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

[Kernel-packages] [Bug 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop
  Idle_Stats

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The first stop -> stop0_lite stats
  and
  The second stop -> stop1_lite stats.

  cpupower monitor header prints the header list by getting the na

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

[Nicholas Johnson]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227732/+files/ProcModules.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicholas Johnson]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227731/+files/ProcInterrupts.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1788782] Re: Ubuntu 16.04.03(P8/Tuleta): SEGV-panic in smp_send_reschedule(). Machine keeps rebooting with oops message even after reboot.

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Ubuntu 16.04.03(P8/Tuleta): SEGV-panic in smp_send_reschedule().
  Machine keeps rebooting with oops message even after reboot.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-07-25 
06:18:00 ==
  ---Problem Description---

  Ubuntu 16.04.03: Fadump fails when dump is triggered after dlpar
  operation. Machine keeps rebooting with oops message even after
  reboot.

  ---Environment--
  Kernel Build:  Ubuntu 16.04.03
  System Name :  Tuleta
  Model/Type  :  P8
  Platform:  LPAR

  ---Uname output---

  root@tuleta4u-lp9:/home/ubuntu# uname -a
  Linux tuleta4u-lp9 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 
10:17:50 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  
  ---Steps to reproduce--
  1. Configure fadump.
  2. Add memory with dlpar operation.
  3. Remove memory with dlpar operation.
  4. Check fadump service is up.
  5. Trigger crash

  ---Logs

  Attaching full console log.

  
  [  OK  ] Reached target Remote File Systems.
   Starting LSB: automatic crash report generation...
   Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
   Starting LSB: Load kernel image with kexec...
   Starting LSB: daemon to balance interrupts for SMP systems...
   Starting Permit User Sessions...
  [   10.997932] Unable to handle kernel paging request for data at address 
0xa000
  [   10.997948] Faulting instruction address: 0xc00459f4
  [   10.997956] Oops: Kernel access of bad area, sig: 11 [#1]
  [   10.997960] SMP NR_CPUS=2048 
  [   10.997961] NUMA 
  [   10.997965] pSeries
  [   10.997971] Modules linked in: binfmt_misc vmx_crypto pseries_rng ib_iser 
rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid1 raid0 multipath linear raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c ibmvscsi crc32c_vpmsum
  [   10.998013] CPU: 5 PID: 2212 Comm: kdump-config Not tainted 
4.10.0-28-generic #32~16.04.2-Ubuntu
  [   10.998020] task: c000fd8b8c00 task.stack: c000fc364000
  [   10.998026] NIP: c00459f4 LR: c0127628 CTR: 
c0141390
  [   10.998031] REGS: c000fc367a60 TRAP: 0300   Not tainted  
(4.10.0-28-generic)
  [   10.998037] MSR: 8280b033 
  [   10.998046]   CR: 28222824  XER: 
  [   10.998053] CFAR: c0008860 DAR: a000 DSISR: 4000 
SOFTE: 0 
  [   10.998053] GPR00: c0127628 c000fc367ce0 c14ad100 
0007 
  [   10.998053] GPR04: c01fd47e5800 0002 0001 
0800 
  [   10.998053] GPR08: 0804 a000  
 
  [   10.998053] GPR12: 2842 cfb82d00 2200 
0100012ab908 
  [   10.998053] GPR16:  0001  
 
  [   10.998053] GPR20: 0060   
 
  [   10.998053] GPR24:  c01fd489d980 c01fd47e5880 
c000fd934b00 
  [   10.998053] GPR28: c01fd47e6044 c01f4fee3280 0007 
c01f4fee3280 
  [   10.998127] NIP [c00459f4] smp_send_reschedule+0x24/0x80
  [   10.998135] LR [c0127628] resched_curr+0x168/0x190
  [   10.998139] Call Trace:
  [   10.998143] [c000fc367ce0] [c0127628] resched_curr+0x168/0x190 
(unreliable)
  [   10.998152] [c000fc367d10] [c0128728] 
check_preempt_curr+0xc8/0xf0
  [   10.998159] [c000fc367d40] [c012b3bc] 
wake_up_new_task+0x16c/0x2d0
  [   10.998167] [c000fc367da0] [c00e7304] _do_fork+0x174/0x520
  [   10.998175] [c000fc367e30] [c000b410] ppc_clone+0x8/0xc
  [   10.998180] Instruction dump:
  [   10.998185] 6000 6000 6042 3c4c0146 38427730 7c0802a6 f8010010 
6000 
  [   10.998196] 3d220006 e9297bc0 2fa9 4d9e0020  2fa9 
419e0044 7c0802a6 
  [   10.998210] ---[ end trace 7ad373050ad8891c ]---
  [   11.003011]

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-07-25 06:24:46 ==

  
  == Comment: #8 - PAVITHRA R. PRAKASH  - 2017-08-29 
08:35:18 ==
  I could not recreate the issue mentioned in bug, But machine is going in to 
Error state after below steps.

  1. Activate the partition with 130GB.
  2. Add 20GB.
  3. Remove 20GB.
  4. Trigger fadump.

  Than

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

[Nicholas Johnson]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1810861/+attachment/5227734/+files/WifiSyslog.txt

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1768115] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160.

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running
  with IO stress crashed@security_file_permission+0xf4/0x160.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Problem Description: Migration Guest running with IO stress
  crashed@security_file_permission+0xf4/0x160 after couple of
  migrations.

  Steps to re-create:

  Source host - boslcp3
  Destination host - boslcp4

  1.boslcp3 & boslcp4 installed with latest kernel
  root@boslcp3:~# uname -a
  Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  root@boslcp4:~# uname -a
  Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  2. Installed guest boslcp3g1 with kernel and started LTP run from
  boslcp3 host

  root@boslcp3g1:~# uname -a
  Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux

  3. Started migrating boslcp3g1 guest from source to destination & viceversa.
  4. After couple of migrations it crashed at boslcp4 & enters into xmon

  8:mon> t
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> S
  msr= 80001033  sprg0 = 
  pvr= 004e1202  sprg1 = c7a85800
  dec= 591e3e03  sprg2 = c7a85800
  sp = c004f8a234a0  sprg3 = 00010008
  toc= c16eae00  dar   = 023c
  srr0   = c00c355c  srr1  = 80001033 dsisr  = 4000
  dscr   =   ppr   = 0010 pir= 0011
  amr=   uamor = 
  dpdes  =   tir   =  cir= 
  fscr   = 05000180  tar   =  pspb   = 
  mmcr0  = 8000  mmcr1 =  mmcr2  = 
  pmc1   =  pmc2 =   pmc3 =   pmc4   = 
  mmcra  =    siar =  pmc5   = 026c
  sdar   =    sier =  pmc6   = 0861
  ebbhr  =   ebbrr =  bescr  = 
  iamr   = 4000
  pidr   = 0034  tidr  = 
  cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220]
  pc: c00e4854: xmon_core+0x1f24/0x3520
  lr: c00e4850: xmon_core+0x1f20/0x3520
  sp: c004f8a234a0
     msr: 80041033
    current = 0xc004f89faf00
    paca= 0xc7a85800   softe: 0irq_happened: 0x01
  pid   = 24028, comm = top
  Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 
4.15.0-20.21-generic 4.15.17)
  cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> r
  R00 = c043b7fc   R16 = 
  R01 = c004f8a23c90   R17 = ff70
  R02 = c16eae00   R18 = 0a51b4bebfc8
  R03 = c00279557200   R19 = 7fffe99edbb0
  R04 = c003242499c0   R20 = 0a51b4c04db0
  R05 = 0002   R21 = 0a51b4c20e90
  R06 = 0004   R22 = 00040f00
  R07 = ff81   R23 = 0a51b4c06560
  R08 = ff80   R24 = ff80
  R09 =    R25 = 0a51b4bec2b8
  R10 =    R26 = 71f177bb0b20
  R11 =    R27 = 
  R12 = 2000   R28 = c00279557200
  R13 = c7a85800   R29 = c004c7734210
  R14 =    R30 = 
 

[Kernel-packages] [Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  dmesg Error seen on system booting from Ubuntu18.04

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

Bug description:
  Problem Description
  ===
  dmesg Error seen on system booting from Ubuntu18.04
  Is this an issue?
  [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)

  user1@yob45wos:~$ sudo dmesg --level=alert
  user1@yob45wos:~$ sudo dmesg --level=crit
  user1@yob45wos:~$ sudo dmesg --level=err
  [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.531263] vio vio: uevent: failed to send synthetic uevent
  [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1)
  [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1)
  [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not 
supported by firmware: 0 0
  [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 
MRQ: 16
  [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not 
supported by firmware: 0 0
  [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 
MRQ: 16
  [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 
x0 x80 x0 x0 x0 0
  [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 
x0 x80 x0 x0 x0 0
  [   22.109545] vio vio: uevent: failed to send synthetic uevent
  user1@yob45wos:~$

  > 
  > Problem Description
  > ===
  > dmesg Error seen on system booting from Ubuntu18.04
  > Is this an issue?  These messages are seen on every IPL.  Is there an issue?
  > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)

  These messages should be marked as Warnings instead of Errors as they it 
supposedly a warning and not an error. 
  This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg 
--level=err' again in 18.04. 
  * In Ubuntu 17.04 : after reboot getting message in console like Unable to
  open file: /etc/keys/x509_ima.der (-2) (LP: #1656908)
  - SAUCE: ima: Downgrade error to warning

  Mirroring this bug to distro to fix this in the latest kernel.

  Thank you.

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

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

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

SRU request was submitted to kernel team.

* For Xenial and trusty-HWE (kernel 4.4): 
https://lists.ubuntu.com/archives/kernel-team/2019-January/097556.html
* For Bionic (kernel 4.15) and Cosmic (kernel 4.18): 
https://lists.ubuntu.com/archives/kernel-team/2019-January/097562.html

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

Title:
  ldisc crash on reopened tty

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:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  * Line discipline code is racy when we have buffer being flush while
  the tty is being initialized or reinitialized. For the first problem,
  we have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
  data race between tty_init_dev and flush of buf") - although it is not
  in Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.

  * For the race between the buffer flush while tty is being reopened,
  we have a patch that addresses this issue recently merged for 5.0-rc1:
  83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
  Ubuntu kernel currently contains this patch, hence we're hereby
  submitting the SRU request. The upstream complete patch series for
  this is in [0].

  * The approach of both patches are similar - they rely in locking/semaphore 
to prevent race conditions. Some additional patches are
  necessary to prevent correlated issues, like preventing a potential deadlock 
due to bad prioritization in servicing I/O over releasing
  tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc 
change is pending"). All the necessary fixes are grouped here in this SRU 
request.

  * The symptom of the race condition between the buffer flush and the
  tty reopen routine is a kernel crash with the following trace:

  BUG: unable to handle kernel paging request at 2268
  IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [...]
  Call Trace:
  [] ? kvm_sched_clock_read+0x1e/0x30
  [] n_tty_receive_buf2+0x14/0x20
  [] flush_to_ldisc+0xd5/0x120
  [] process_one_work+0x156/0x400
  [] worker_thread+0x11a/0x480
  [...]

  * A kernel crash was collected from an user, analysis is present in
  comment #4 in this LP.

  [Test Case]

  * It is not trivial to trigger this fault, but the usual recipe is to
  keep accessing a machine through SSH (or keep killing getty when in
  IPMI serial console) and in some way run commands before the terminal
  is ready in that machine (like hacking some echo into ttySx or pts in
  an infinite loop).

  * We have reports of users that could reproduce this issue in their
  production environment, and with the patches present in this SRU
  request the problem was fixed.

  [Regression Potential]

  * tty subsystem is highly central and patches in that area are always
  delicate. For example, the upstream series [0] is a re-spin (V6) due
  to a hard to reproduce issue reported in the PA-RISC architecture,
  which was found in the V5 iteration [1] but was fixed by the patch
  c96cf923a98d, present in this SRU request.

  * The patchset [0] is present in tty-next tree since mid-November, and
  the patch b027e2298bd5 is available upstream since January/2018 (it's
  available in both Ubuntu kernels 4.15 and 4.18), so the overall
  likelihood of regressions is low.

  * These patches were sniff-tested for the 3 versions (4.4, 4.15 and
  4.18) and didn't show any issues.

  [0] https://marc.info/?l=linux-kernel&m=154103190111795
  [1] https://marc.info/?l=linux-kernel&m=153737852618183

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

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

[Kernel-packages] [Bug 1708870] Re: Support for X553 Intel NIC in Xenial

[Leroy Tennison]

I am also needing the updated driver for a firewall appliance.

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1708870

Title:
  Support for X553 Intel NIC in Xenial

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Hey!

  The Intel Atom C3000 platform comes with an integrated X553 Intel NIC.
  Support was added in Linux 4.11:
  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=b3eb4e1860f35. PCI IDs are 8086:15E4 and
  8086:15E5.

  Would it be possible to backport such support into 4.4? Redhat
  provided support for such chips a few months back (through DKMS):
  https://access.redhat.com/errata/RHEA-2017:1194.

  Thanks.

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

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