[Kernel-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Hui Wang]

** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan

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

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

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

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

[Kernel-packages] [Bug 1892012] Re: Bluetooth doesn't turn on

[Brieuc du Garay]

@alexhung That's what I thought, even if I did tried powering off my laptop and 
unplug the charger for several minutes. Yet, I didn't take off the battery.
I did happen again few days ago, althought that time a simple `shutdown -r now` 
was enought to get it to work.

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

Title:
  Bluetooth doesn't turn on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UPDATE
  ==

  I tried another kernel (`5.4.0-40-generic` and it didn't worked.
  Trying to reboot (and get back to the latest kernel) it didn't shutdown, so I 
hard shutdown it, and restart with the `5.4.0-42-generic`.

  And now, it works.
  I hope the logs below may help you to find out what happened, and help others 
to fix their issue if it's similar to this one.

  ---

  
  Hello,

  For now, everything worked fine, until this morning when Bluetooth
  stop working.

  Ubuntu 20.04

  **What expected to happen :** Bluetooth turn on on start, and if it's
  off it turns on when I turn it on.

  **What happens :** it doesn't turn on.

  ```
   $ dmesg | grep -i blue
  [2.433133] Bluetooth: Core ver 2.22
  [2.433147] Bluetooth: HCI device and connection manager initialized
  [2.433149] Bluetooth: HCI socket layer initialized
  [2.433151] Bluetooth: L2CAP socket layer initialized
  [2.433153] Bluetooth: SCO socket layer initialized
  [3.559082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.559083] Bluetooth: BNEP filters: protocol multicast
  [3.559088] Bluetooth: BNEP socket layer initialized
  [4.456149] Bluetooth: hci0: command 0xfc05 tx timeout
  [4.456167] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  ```

  Last `/var/log/dpkg.log` logs (previous were from 3 days ago)
  ```
  2020-08-18 01:06:02 startup archives unpack
  2020-08-18 01:06:03 install python3-blessings:all  1.6-3
  2020-08-18 01:06:03 status half-installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 install python3-pynvml:amd64  7.352.0-3
  2020-08-18 01:06:03 status half-installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 install gpustat:all  0.6.0-1
  2020-08-18 01:06:03 status half-installed gpustat:all 0.6.0-1
  2020-08-18 01:06:03 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:03 startup packages configure
  2020-08-18 01:06:03 configure python3-blessings:all 1.6-3 
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status half-configured python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 configure python3-pynvml:amd64 7.352.0-3 
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status half-configured python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 status installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 configure gpustat:all 0.6.0-1 
  2020-08-18 01:06:04 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status half-configured gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status installed gpustat:all 0.6.0-1

  ```

  ```
   $ dpkg -l | grep -i blue
  ii  bluez 5.53-0ubuntu3   
  amd64Bluetooth tools and daemons
  ii  bluez-cups5.53-0ubuntu3   
  amd64Bluetooth printer driver for CUPS
  ii  bluez-obexd   5.53-0ubuntu3   
  amd64bluez obex daemon
  ii  gir1.2-gnomebluetooth-1.0:amd64   3.34.1-1
  amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth   3.34.1-1
  amd64GNOME Bluetooth tools
  ii  libbluetooth3:amd64   5.53-0ubuntu3   
  amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd643.34.1-1
  amd64GNOME Bluetooth tools - support library
  ii  libkf5bluezqt-data5.68.0-0ubuntu1 
  all  data files for bluez-qt
  ii  libkf5bluezqt6:amd64  5.68.0-0ubuntu1 
  amd64Qt wrapper for bluez
  ii  node-bluebird 3.5.1+dfsg2-2build1 
  all  Fully featured Promises/A+ implementation for Node.js
  ii  pulseaudio-module-bluetooth   1:13.99.1-1ubuntu3.5
  amd64Bluetooth module for PulseAudio sound server
  ii  qml-module-org-kde-bluezqt:amd64  5.68.0-0ubuntu1 

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

[Mike Pozulp]

@John Hoff

> Mike, depending on your answers to my many questions from today, if
the only way we know to proceed is to build and test a patch, could you
help with building the patch (or at least the basic framework of the
patch so I can just plug in the CORB values)?

Absolutely. I'll write a patch and test it on my machine, after which
I'll share it with you. In the mean time you could try Early Patching.
Your Early Patching file will have an enormous [verb] section which will
look like this

[verb]
0x1a 0x707 0xc5
.
.
.

Each line contains three space-separated hex values: Node ID, Verb ID,
and Payload. You will have one line for each verb in the CORB dump, so
that could be 1000s of lines.

I think hda-verb < Early Patching < kernel patch, in the sense that a
kernel patch has the highest-probability of success, hda-verb has the
lowest, and Early Patching is somewhere in between. This is because I
think that some codec values are read-write at initialization time but
then become read-only at runtime (only Realtek, the ALC298 manufacturer,
knows for sure*). A kernel patch allows us to write values at codec
initialization time, whereas hda-verb is at runtime, and Early Patching
is somewhere in between.

*Perhaps we can know: I found a datasheet for the ALC269 [1]. I think
the ALC269 is very similar to the ALC298 codec in our laptops. Among
other things, the datasheet describes verb semantics. It's a nice
supplement to the Intel HDA spec. I don't recall seeing anything about
initialization-time vs runtime, but perhaps I have not read it closely
enough - the datasheet is only somewhat less dense and technical than
the Intel HDA spec so it's not an easy read! :)

[1] https://www.hardwaresecrets.com/datasheets/alc269.pdf

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Relase of Ubuntu: 19.10

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

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

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

  !!DMI Information
  !!---

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

  
  !!Kernel Information
  !!--

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


  !!ALSA Version
  !!

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

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

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

  
  !!Soundcards recognised by ALSA
  !!-

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

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

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

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

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

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

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir

[Kernel-packages] [Bug 1892827] Re: device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init

[You-Sheng Yang]

No change resubmit, so PPA not rebuilt.

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

Title:
  device doesn't boot with kernel older than v5.7.7 on a usb key: hang
  at efi_tpm_eventlog_init

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some systems may hang at boot. With "earlycon=efifb", more debug
  messages for EFI are dumpped. Last call trace as:

RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
 efi_config_parse_tables+0x12d/0x213
 efi_init+0x218/0x36b
 ? e820__print_table+0x65/0x6e
 setup_arch+458/0xa84

  This affects all mainline kernel since v5.2 to v5.7.6. Fix available in
  v5.8-rc3 and has been backported to v5.7.7, v5.4.50.

  [Fix]
  Commit ea3cdcaa43b0 ("efi/tpm: Verify event log header before parsing")
  fixes commit 6b0326190205 ("efi: Attempt to get the TCG2 event log in
  the boot stub").

  [Test Case]
  So far it can be easily reproduced with a green installation of Focal on
  USB key on a few Dell platforms.

  [Regression Potential]
  Low. This checks validity of tmp event log header before parsing them,
  so it affects only platforms might generate invalid entries only.

  [Other Info]
  This affects -generic for eoan and oem-5.6 for focal, but the former has
  be EOL-ed.

  == Original Bug Description ==

  [Summary] device doesn't boot with kernel older than v5.7.7 on USB key

  [Steps to reproduce]
  1. Try to boot a green installation of Ubuntu Focal on a USB key.

  [Expected result]
  Boot up normally.

  [Actual result]
  Stuck at "loading initial ramdisk". With "earlycon=efifb", more debug 
messages for EFI are dumpped. Last call trace as:

    RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
    ...
    Call Trace:
     efi_config_parse_tables+0x12d/0x213
     efi_init+0x218/0x36b
     ? e820__print_table+0x65/0x6e
     setup_arch+458/0xa84

  [Failure rate]
  10/10

  [Additional information]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea3cdcaa43b08c9a747639f545b0ed5cca47f87e
 ("efi/tpm: Verify event log header before parsing") fixes in 6b0326190205 
("efi: Attempt to get the TCG2 event log in the boot stub").

  The fix is in linux-5.7.y and v5.8-rc3, and focal 5.4 and oem-5.6 are
  affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Tue Aug 25 02:51:58 2020
  InstallationDate: Installed on 2020-07-21 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-16-generic 
root=UUID=7c53c615-c466-43d7-9ca3-f8b8d895b7b0 ro initcall_debug debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.release: 0.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.3:bd08/05/2020:br0.4:svnDellInc.:pnInspiron3500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3500
  dmi.product.sku: 0A25
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1892827] Re: device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init

[You-Sheng Yang]

SRU v2: https://lists.ubuntu.com/archives/kernel-
team/2020-August/112992.html

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

Title:
  device doesn't boot with kernel older than v5.7.7 on a usb key: hang
  at efi_tpm_eventlog_init

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  Some systems may hang at boot. With "earlycon=efifb", more debug
  messages for EFI are dumpped. Last call trace as:

RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
 efi_config_parse_tables+0x12d/0x213
 efi_init+0x218/0x36b
 ? e820__print_table+0x65/0x6e
 setup_arch+458/0xa84

  This affects all mainline kernel since v5.2 to v5.7.6. Fix available in
  v5.8-rc3 and has been backported to v5.7.7, v5.4.50.

  [Fix]
  Commit ea3cdcaa43b0 ("efi/tpm: Verify event log header before parsing")
  fixes commit 6b0326190205 ("efi: Attempt to get the TCG2 event log in
  the boot stub").

  [Test Case]
  So far it can be easily reproduced with a green installation of Focal on
  USB key on a few Dell platforms.

  [Regression Potential]
  Low. This checks validity of tmp event log header before parsing them,
  so it affects only platforms might generate invalid entries only.

  [Other Info]
  This affects -generic for eoan and oem-5.6 for focal, but the former has
  be EOL-ed.

  == Original Bug Description ==

  [Summary] device doesn't boot with kernel older than v5.7.7 on USB key

  [Steps to reproduce]
  1. Try to boot a green installation of Ubuntu Focal on a USB key.

  [Expected result]
  Boot up normally.

  [Actual result]
  Stuck at "loading initial ramdisk". With "earlycon=efifb", more debug 
messages for EFI are dumpped. Last call trace as:

    RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
    ...
    Call Trace:
     efi_config_parse_tables+0x12d/0x213
     efi_init+0x218/0x36b
     ? e820__print_table+0x65/0x6e
     setup_arch+458/0xa84

  [Failure rate]
  10/10

  [Additional information]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea3cdcaa43b08c9a747639f545b0ed5cca47f87e
 ("efi/tpm: Verify event log header before parsing") fixes in 6b0326190205 
("efi: Attempt to get the TCG2 event log in the boot stub").

  The fix is in linux-5.7.y and v5.8-rc3, and focal 5.4 and oem-5.6 are
  affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Tue Aug 25 02:51:58 2020
  InstallationDate: Installed on 2020-07-21 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-16-generic 
root=UUID=7c53c615-c466-43d7-9ca3-f8b8d895b7b0 ro initcall_debug debug
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.release: 0.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.3:bd08/05/2020:br0.4:svnDellInc.:pnInspiron3500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3500
  dmi.product.sku: 0A25
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

[Kai-Heng Feng]

This is a kernel bug so not sure if it's wise to fix it from
userspace...

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

Title:
  No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc"
  is lowered to 8

Status in gnome-control-center:
  Unknown
Status in Linux:
  Unknown
Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user
  experience.

  existed upstream bug:
   - https://gitlab.freedesktop.org/drm/intel/-/issues/1890

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions

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

[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64

[Po-Hsu Lin]

Need to check if we still have this issue on 5.3 / 5.0 Variants.

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

Title:
  test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
  timeout" on D ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  This issue can be found on 2 different ARM64 node, TunderX Cavium node
  "starmie" and Moonshot "ms10-34-mcdivittB0-kernel"

  Running test_maps bpf test..
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Failed sockmap unexpected timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.12-

[Kernel-packages] [Bug 1845870] Re: test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 / 5.4 ARM64

[Po-Hsu Lin]

Spotted on 5.4.0-44.48-generic
With ARM64 node hotdog-kernel / ms10-34-mcdivittB0-kernel


** Tags added: sru-20200810

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

Title:
  test_verifier from ubuntu_bpf failed on B-hwe-edge 5.3 / 5.4 ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on a Moonshot node with B-hwe-edge 5.3 kernel,
  test failed with:
#13/p valid read map access into a read-only array 2 FAIL retval 65507 != 
-29 (run 1/1)
verification time 41 usec
stack depth 8
processed 14 insns (limit 100) max_states_per_insn 0 total_states 1 
peak_states 1 mark_read 1

  This is the only test failing in this test suite:
Summary: 1547 PASSED, 0 SKIPPED, 1 FAILED

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

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

[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64

[Po-Hsu Lin]

Passed on Focal ARM64
5.4.0-44.48-generic

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

Title:
  test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
  timeout" on D ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix

Bug description:
  This issue can be found on 2 different ARM64 node, TunderX Cavium node
  "starmie" and Moonshot "ms10-34-mcdivittB0-kernel"

  Running test_maps bpf test..
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Failed sockmap unexpected timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12
  Uname

[Kernel-packages] [Bug 1845643] Re: test_maps in ubuntu_bpf failed on s390x Disco (libbpf: Error loading ELF section .BTF: -22. Ignored and continue.)

[Po-Hsu Lin]

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

** This bug has been marked a duplicate of bug 1845860
   test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, 
but is missing or corrupted.)

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

Title:
  test_maps in ubuntu_bpf failed on s390x Disco (libbpf: Error loading
  ELF section .BTF: -22. Ignored and continue.)

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  Won't Fix

Bug description:
  The ubuntu_bpf test failed on Disco s390x with:

Failed to load SK_SKB parse prog
stderr:
libbpf: Error loading ELF section .BTF: -22. Ignored and continue.
libbpf: object file doesn't contain bpf program

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

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

[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

[Mathew Hodson]

** No longer affects: gnome-control-center (Ubuntu Focal)

** No longer affects: gnome-control-center (Ubuntu)

** No longer affects: nvidia-graphics-drivers-340 (Ubuntu Focal)

** No longer affects: nvidia-graphics-drivers-340 (Ubuntu)

** No longer affects: nvidia-graphics-drivers-440 (Ubuntu Focal)

** No longer affects: nvidia-graphics-drivers-440 (Ubuntu)

** No longer affects: nvidia-graphics-drivers-435 (Ubuntu Focal)

** No longer affects: nvidia-graphics-drivers-435 (Ubuntu)

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  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.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-n

[Kernel-packages] [Bug 1873054] Re: Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

[Po-Hsu Lin]

Test passed on Focal 5.4.0-44.48 amd64 generic / lowlatency, arm64,
s390x, P8 (not tested on P9, test aborted in other tests before this
one)

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

Title:
  Test Wakeup Tracer / RT Tracer fails in ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  In Focal,

  The following tests fail on baremetal/amd64:

  04/12 03:27:37 DEBUG| utils:0153| [stdout] # [51] Test wakeup tracer  
[FAIL]
  04/12 03:27:39 DEBUG| utils:0153| [stdout] # [52] Test wakeup RT tracer   
[FAIL]
  04/12 03:27:41 DEBUG| utils:0153| [stdout] # [53] event trigger - test 
inter-event histogram trigger expected fail actions[XFAIL]

  Full output below.

  04/12 03:25:07 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/12 03:25:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/12 03:25:17 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/12 03:25:21 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/12 03:25:22 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/12 03:25:23 DEBUG| utils:0153| [stdout] # [8] Generic dynamic event - 
add/remove kprobe events [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [9] Generic dynamic event - 
add/remove synthetic events  [PASS]
  04/12 03:25:24 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
selective clear (compatibility) [PASS]
  04/12 03:25:25 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
generic clear event [PASS]
  04/12 03:25:26 DEBUG| utils:0153| [stdout] # [12] event tracing - 
enable/disable with event level files   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [13] event tracing - 
restricts events based on pid   [PASS]
  04/12 03:25:27 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with subsystem level files   [PASS]
  04/12 03:25:28 DEBUG| utils:0153| [stdout] # [15] event tracing - 
enable/disable with top level files [PASS]
  04/12 03:25:30 DEBUG| utils:0153| [stdout] # [16] Test trace_printk from 
module   [PASS]
  04/12 03:25:35 DEBUG| utils:0153| [stdout] # [17] ftrace - function graph 
filters with stack tracer   [PASS]
  04/12 03:25:37 DEBUG| utils:0153| [stdout] # [18] ftrace - function graph 
filters [PASS]
  04/12 03:25:40 DEBUG| utils:0153| [stdout] # [19] ftrace - function pid 
filters   [PASS]
  04/12 03:25:41 DEBUG| utils:0153| [stdout] # [20] ftrace - stacktrace 
filter command  [PASS]
  04/12 03:25:43 DEBUG| utils:0153| [stdout] # [21] ftrace - function trace 
with cpumask[PASS]
  04/12 03:25:48 DEBUG| utils:0153| [stdout] # [22] ftrace - test for 
function event triggers   [PASS]
  04/12 03:25:49 DEBUG| utils:0153| [stdout] # [23] ftrace - function trace 
on module   [PASS]
  04/12 03:25:53 DEBUG| utils:0153| [stdout] # [24] ftrace - function 
profiling [PASS]
  04/12 03:25:59 DEBUG| utils:0153| [stdout] # [25] ftrace - function 
profiler with function tracing[PASS]
  04/12 03:26:03 DEBUG| utils:0153| [stdout] # [26] ftrace - test reading 
of set_ftrace_filter  [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [27] ftrace - test for 
function traceon/off triggers [PASS]
  04/12 03:26:07 DEBUG| utils:0153| [stdout] # [28] ftrace - test tracing 
error log support [PASS]
  04/12 03:26:11 DEBUG| utils:0153| [stdout] # [29] Test creation and 
deletion of trace instances while setting an event[PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [30] Test creation and 
deletion of trace instances   [PASS]
  04/12 03:26:13 DEBUG| utils:0153| [stdout] # [31] Kprobe dynamic event - 
adding and removing  [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [32] Kprobe dynamic event - 
busy event check [PASS]
  04/12 03:26:14 DEBUG| utils:0153| [stdout] # [33] Kprobe dynamic event 
with arguments [PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [34] Kprobe event with comm 
arguments[PASS]
  04/12 03:26:15 DEBUG| utils:0153| [stdout] # [35] Kprobe event string 
type argument   [PASS]
  04/12 03:26:16 DEBUG| utils:0153| [stdout] # [36] Kprobe event symbol 
argument[PASS]
  04/12 03:26:18 DEBUG| utils:0153| [stdout] # 

[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels

[Po-Hsu Lin]

** Tags added: sru-20200810

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

Title:
  ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 kernels

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Eoan:
  Incomplete
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New
Status in linux-gcp source package in Focal:
  New

Bug description:
  Test failed with:
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)

  Steps:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control

  Test output:
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 18 Mbytes
Try 2 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 22 Mbytes
Try 3 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 4 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 5 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 6 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 7 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 8 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 9 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 10 of 10
Sysdig capture started after 1 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Found:
   279845 sysdig events
   29882 context switches
   0 reads from /dev/zero by dd
   0 writes to /dev/null by dd
PASSED (trace at least 25 context switches)
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)
 
Summary: 1 passed, 2 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-10-generic 5.3.0-10.11
  ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 08:10 seq
   crw-rw 1 root audio 116, 33 Sep 18 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed Sep 18 08:18:54 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassi

[Kernel-packages] [Bug 1892677] Re: Fix non-working USB devices plugged during system sleep

[Po-Hsu Lin]

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

** This bug has been marked a duplicate of bug 1892678
   Fix non-working USB devices plugged during system sleep

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

Title:
  Fix non-working USB devices plugged during system sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Some USB devices aren't working if they are plugged under system sleep.

  [Fix]
  Consider xHCI PORTSC CAS bit over other conditions.

  [Test]
  Plug or re-plug USB devices during system sleep. USB devices always work
  after system resume.

  [Regression Potential]
  There could be devices that depends on the old (but wrong) behavior. 
  However it's really unlikely and it's against xHCI spec, we can deal 
  with those quirky devices if any.

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

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

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

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

Title:
  [Potential Regression] hyperv_connections / hyperv_stimer /
  hyperv_synic failed on B-i386

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on 4.15.0-114.115, with i386 generic /lowlatency on node
  fozzie.

  All 3 tests failed with timeout issue:
  * hyperv_connections
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UwdQ0PZort -smp 2 
-cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd 
/tmp/tmp.GNmO7BfE7a
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   EAX=00459001 EBX=0040aae0 ECX=4083 EDX=
   ESI= EDI= EBP=0044b158 ESP=0044b130
   EIP=004006b9 EFL=0202 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 0044a1f0  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=664fb17c DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=87 e0 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 <8b> 43 04 
83 c8 01 b9 82 00 00 40 0f 30 b8 01 00 00 00 b9 80 00 00 40 0f 30 83 c4 0c 0f b6
   qemu-system-i386: terminating on signal 15 from pid 12753 (timeout)
   FAIL hyperv_connections (timeout; duration=90s)

  * hyperv_stimer
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.P9Uky1nZUD -smp 2 
-cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # 
-initrd /tmp/tmp.uulivUIlYy
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   enabling apic
   cpus = 2
   EAX=00458001 EBX=0040aa9c ECX=4083 EDX=
   ESI= EDI=0004 EBP=0044aab8 ESP=0044aaa0
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 00449b60  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=4036d141 DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=86 64 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 01 00 00 00 
b9 80 00 00 40 0f 30 83 ec 04 6a 00 68 f1 00 00 00 6a 02 e8 ac 02 00 00 83
   EAX=00459001 EBX=0040aad8 ECX=400

[Kernel-packages] [Bug 1892971] Re: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-53-generic 3.13.0-53.89
  ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  taktak 2336 F pulseaudio
  CRDA:
   country TN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 20), (N/A, 20)
(5250 - 5330 @ 20), (N/A, 20), DFS
  Date: Wed Aug 26 02:47:26 2020
  DuplicateSignature: 
package:linux-image-3.13.0-53-generic:3.13.0-53.89:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3
  InstallationDate: Installed on 2012-12-06 (2819 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Vostro 1015
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  SourcePackage: linux
  Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2018-10-13 (682 days ago)
  dmi.bios.date: 09/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 047MWF
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1015
  dmi.sys.vendor: Dell Inc.

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

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

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

Title:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-53-generic 3.13.0-53.89
  ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  taktak 2336 F pulseaudio
  CRDA:
   country TN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 20), (N/A, 20)
(5250 - 5330 @ 20), (N/A, 20), DFS
  Date: Wed Aug 26 02:47:26 2020
  DuplicateSignature: 
package:linux-image-3.13.0-53-generic:3.13.0-53.89:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3
  InstallationDate: Installed on 2012-12-06 (2819 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Vostro 1015
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  SourcePackage: linux
  Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2018-10-13 (682 days ago)
  dmi.bios.date: 09/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 047MWF
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1015
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1892971] [NEW] package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[RTAKTAK]

Public bug reported:

package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-53-generic 3.13.0-53.89
ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  taktak 2336 F pulseaudio
CRDA:
 country TN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 20), (N/A, 20)
(5250 - 5330 @ 20), (N/A, 20), DFS
Date: Wed Aug 26 02:47:26 2020
DuplicateSignature: 
package:linux-image-3.13.0-53-generic:3.13.0-53.89:subprocess installed 
post-installation script returned error exit status 17
ErrorMessage: subprocess installed post-installation script returned error exit 
status 17
HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3
InstallationDate: Installed on 2012-12-06 (2819 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
MachineType: Dell Inc. Vostro 1015
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
SourcePackage: linux
Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
UpgradeStatus: Upgraded to trusty on 2018-10-13 (682 days ago)
dmi.bios.date: 09/17/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 047MWF
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1015
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-package i386 trusty

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

Title:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-53-generic 3.13.0-53.89
  ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  taktak 2336 F pulseaudio
  CRDA:
   country TN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 20), (N/A, 20)
(5250 - 5330 @ 20), (N/A, 20), DFS
  Date: Wed Aug 26 02:47:26 2020
  DuplicateSignature: 
package:linux-image-3.13.0-53-generic:3.13.0-53.89:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3
  InstallationDate: Installed on 2012-12-06 (2819 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Vostro 1015
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  SourcePackage: linux
  Title: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2018-10-13 (682 days ago)
  dmi.bios.date: 09/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 047MWF
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1015
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

[Daniel van Vugt]

My concern is that you might be taking functionality (deep/wide colour)
away from people for whom it 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/1890772

Title:
  No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc"
  is lowered to 8

Status in gnome-control-center:
  Unknown
Status in Linux:
  Unknown
Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user
  experience.

  existed upstream bug:
   - https://gitlab.freedesktop.org/drm/intel/-/issues/1890

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions

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

[Kernel-packages] [Bug 1892855] Re: [Potential Regression] hyperv_connections / hyperv_stimer / hyperv_synic failed on B-i386

[Po-Hsu Lin]

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

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

Title:
  [Potential Regression] hyperv_connections / hyperv_stimer /
  hyperv_synic failed on B-i386

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Issue found on 4.15.0-114.115, with i386 generic /lowlatency on node
  fozzie.

  All 3 tests failed with timeout issue:
  * hyperv_connections
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UwdQ0PZort -smp 2 
-cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd 
/tmp/tmp.GNmO7BfE7a
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   EAX=00459001 EBX=0040aae0 ECX=4083 EDX=
   ESI= EDI= EBP=0044b158 ESP=0044b130
   EIP=004006b9 EFL=0202 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 0044a1f0  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=664fb17c DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=87 e0 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 <8b> 43 04 
83 c8 01 b9 82 00 00 40 0f 30 b8 01 00 00 00 b9 80 00 00 40 0f 30 83 c4 0c 0f b6
   qemu-system-i386: terminating on signal 15 from pid 12753 (timeout)
   FAIL hyperv_connections (timeout; duration=90s)

  * hyperv_stimer
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-i386 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.P9Uky1nZUD -smp 2 
-cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # 
-initrd /tmp/tmp.uulivUIlYy
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.syscall [bit 11]
   qemu-system-i386: warning: host doesn't support requested feature: 
CPUID.8001H:EDX.lm [bit 29]
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 453000
   cr4 = 10
   enabling apic
   cpus = 2
   EAX=00458001 EBX=0040aa9c ECX=4083 EDX=
   ESI= EDI=0004 EBP=0044aab8 ESP=0044aaa0
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 00449b60  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0080 00406280  8b00 DPL=0 TSS32-busy
   GDT= 00406000 027f
   IDT=  0fff
   CR0=80010011 CR2= CR3=00453000 CR4=0010
   DR0= DR1= DR2=4036d141 DR3=
   DR6=0ff0 DR7=0400
   EFER=
   Code=86 64 aa 40 00 83 c8 01 ba 00 00 00 00 b9 83 00 00 40 0f 30 01 00 00 00 
b9 80 00 00 40 0f 30 83 ec 04 6a 00 68 f1 00 00 00 6a 02 e8 ac 02 00 00 83
   EAX=00459001 EBX=0040aad8 ECX=4083 EDX=
   ESI=003c EDI=0004 EBP=0009ffbc ESP=0009ffa4
   EIP=0040070c EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
   ES =0010   00c09300 DPL=0 DS [-WA]
   CS =0008   00c09b00 DPL=0 CS32 [-RA]
   SS =0010   00c09300 DPL=0 DS [-WA]
   DS =0010   00c09300 DPL=0 DS [-WA]
   FS =0010   00c09300 DPL=0 DS [-WA]
   GS =0010 0009f000  00c09300 DPL=0 DS [-WA]
   LDT=   8200 DPL=0 LDT
   TR =0088 004062e

[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

[Daniel van Vugt]

Although as a workaround, changing your background wallpaper should also
resolve it each time.

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

[Daniel van Vugt]

Just wait for the mutter version 3.36.5 update.

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Code that touches DSCR user MSR does not set dscr_inherit, which breaks DSCR 
restore doing context switches and inheritance when forking. DSCR is used to 
control cache hinting. This is caused by lack of kernel interrupt when the DSCR 
user MSR is written, which is controlled by FSCR which would otherwise cause a 
facility unavailable interrupt.

  [Test case]
  apt-get source linux
  cd linux-5.4.0/tools/testing/tools/selftests/powerpc/
  make -j 32
  make -C dscr run_tests
  make -C ptrace run_tests
  make -C tm run_tests

  Look up for "not ok" versus "ok", specially for
  dscr_inherit_exec_test, ptrace-tar and tm-resched-tar.

  [Potential regression]
  Manipulating DSCR might break on different machines (with DTs containing 
  /cpus/ibm,powerpc-cpu-features, for example). Code that does so might crash 
because the facility unavailable interrupt handling might be not working 
correctly.

  
  
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Hui Wang]

Please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874698
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878479,


I think if you install the alsa-ucm-conf - 1.2.2-1ubuntu0.1 and uninstall the 
workaround of retasking codec pin ([2.997562] snd_hda_intel :01:00.1: 
Applying patch firmware 'hda-jack-retask.fw'), the microphone should work.

About the system hang or crash, maybe it has sth to do with graphic?
Maybe could have a try with adding "nomodeset nvidia_drm.modeset=0" to
the bootargs.

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

Title:
  Microphone not working on HP Omen 17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Noctis Bennington]

** Attachment added: "intel_reg read 0x64000 0x64100 0x64200 0x64300 0x64400 
0x6C00C"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+attachment/5404549/+files/second-command.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).


  WORKAROUND: I installed the 4.15 kernel, so at the moment I can work
  with this. Higher than 4.15 the second monitor doesn't work. Tested
  until 5.8 and without good results. Just with 4.15.

  
  ---
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Noctis Bennington]

Okey, I did it. Tested with the last kernel (5.8.3).

Here are the results.

** Attachment added: "intel_reg read --count 20 0x64E00 0x64E60 0x64EC0 0x64F20 
0x64F80"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+attachment/5404548/+files/first-comand.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).


  WORKAROUND: I installed the 4.15 kernel, so at the moment I can work
  with this. Higher than 4.15 the second monitor doesn't work. Tested
  until 5.8 and without good results. Just with 4.15.

  
  ---
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate 

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[wangjun]

my computer is Lenovo Legion R7000 ，with the MSFT0001:00 04F3:3140
touchpad.

and i had tested the kernel 5.9.0 rc2 on fedora 32 with no lucky,

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --

[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rafael Motta]

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

experiencing this as well
Lenovo ideapad 330
jbl live400bt
mic over bluetooth not working :(
but fully works over cable plugged in

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Kernel-packages] [Bug 1837810] Re: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host

[Ian]

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

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

Title:
  KVM: Fix zero_page reference counter overflow when using KSM on KVM
  compute host

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

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

  [Impact]

  We are seeing a problem on OpenStack compute nodes, and KVM hosts,
  where a kernel oops is generated, and all running KVM machines are
  placed into the pause state.

  This is caused by the kernel's reserved zero_page reference counter
  overflowing from a positive number to a negative number, and hitting a
  (WARN_ON_ONCE(page_ref_count(page) <= 0)) condition in try_get_page().

  This only happens if the machine has Kernel Samepage Mapping (KSM)
  enabled, with "use_zero_pages" turned on. Each time a new VM starts
  and the kernel does a KSM merge run during a EPT violation, the
  reference counter for the zero_page is incremented in try_async_pf()
  and never decremented. Eventually, the reference counter will
  overflow, causing the KVM subsystem to fail.

  Syslog:
  error : qemuMonitorJSONCheckError:392 : internal error: unable to execute 
QEMU command 'cont': Resetting the Virtual Machine is required

  QEMU Logs:
  error: kvm run failed Bad address
  EAX=000afe00 EBX=000b ECX=0080 EDX=0cfe
  ESI=0003fe00 EDI=000afe00 EBP=0007 ESP=6d74
  EIP=000ee344 EFL=00010002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =0010   00c09300 DPL=0 DS   [-WA]
  CS =0008   00c09b00 DPL=0 CS32 [-RA]
  SS =0010   00c09300 DPL=0 DS   [-WA]
  DS =0010   00c09300 DPL=0 DS   [-WA]
  FS =0010   00c09300 DPL=0 DS   [-WA]
  GS =0010   00c09300 DPL=0 DS   [-WA]
  LDT=   8200 DPL=0 LDT
  TR =   8b00 DPL=0 TSS32-busy
  GDT= 000f7040 0037
  IDT= 000f707e 
  CR0=0011 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=c3 57 56 b8 00 fe 0a 00 be 00 fe 03 00 b9 80 00 00 00 89 c7  a5 a1 
00 80 03 00 8b 15 04 80 03 00 a3 00 80 0a 00 89 15 04 80 0a 00 b8 ae e2 00 00 31

  Kernel Oops:

  [  167.695986] WARNING: CPU: 1 PID: 3016 at 
/build/linux-hwe-FEhT7y/linux-hwe-4.15.0/include/linux/mm.h:852 
follow_page_pte+0x6f4/0x710
  [  167.696023] CPU: 1 PID: 3016 Comm: CPU 0/KVM Tainted: G   OE
4.15.0-106-generic #107~16.04.1-Ubuntu
  [  167.696023] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1 04/01/2014
  [  167.696025] RIP: 0010:follow_page_pte+0x6f4/0x710
  [  167.696026] RSP: 0018:a81802023908 EFLAGS: 00010286
  [  167.696027] RAX: ed8786e33a80 RBX: ed878c6d21b0 RCX: 
8000
  [  167.696027] RDX:  RSI: 3000 RDI: 
8001b8cea225
  [  167.696028] RBP: a81802023970 R08: 8001b8cea225 R09: 
90c4d55fa340
  [  167.696028] R10:  R11:  R12: 
ed8786e33a80
  [  167.696029] R13: 0326 R14: 90c4db94fc50 R15: 
90c4d55fa340
  [  167.696030] FS:  7f6a7798c700() GS:90c4edc8() 
knlGS:
  [  167.696030] CS:  0010 DS:  ES:  CR0: 80050033
  [  167.696031] CR2:  CR3: 000315580002 CR4: 
00162ee0
  [  167.696033] Call Trace:
  [  167.696047]  follow_pmd_mask+0x273/0x630
  [  167.696049]  follow_page_mask+0x178/0x230
  [  167.696051]  __get_user_pages+0xb8/0x740
  [  167.696052]  get_user_pages+0x42/0x50
  [  167.696068]  __gfn_to_pfn_memslot+0x18b/0x3b0 [kvm]
  [  167.696079]  ? mmu_set_spte+0x1dd/0x3a0 [kvm]
  [  167.696090]  try_async_pf+0x66/0x220 [kvm]
  [  167.696101]  tdp_page_fault+0x14b/0x2b0 [kvm]
  [  167.696104]  ? vmexit_fill_RSB+0x10/0x40 [kvm_intel]
  [  167.696114]  kvm_mmu_page_fault+0x62/0x180 [kvm]
  [  167.696117]  handle_ept_violation+0xbc/0x160 [kvm_intel]
  [  167.696119]  vmx_handle_exit+0xa5/0x580 [kvm_intel]
  [  167.696129]  vcpu_enter_guest+0x414/0x1260 [kvm]
  [  167.696138]  ? kvm_arch_vcpu_load+0x4d/0x280 [kvm]
  [  167.696148]  kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm]
  [  167.696157]  ? kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm]
  [  167.696165]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
  [  167.696166]  ? do_futex+0x129/0x590
  [  167.696171]  ? __switch_to+0x34c/0x4e0
  [  167.696174]  ? __switch_to_asm+0x35/0x70
  [  167.696176]  do_vfs_ioctl+0xa4/0x600
  [  167.696177]  SyS_ioctl+0x79/0x90
  [  167.696180]  ? exit_to_usermode_loop+0xa5/0xd0
  [  167.696181]  do_syscall_64+0x73/0x130
  [  167

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

** Description changed:

+ [Impact]
+ Code that touches DSCR user MSR does not set dscr_inherit, which breaks DSCR 
restore doing context switches and inheritance when forking. DSCR is used to 
control cache hinting. This is caused by lack of kernel interrupt when the DSCR 
user MSR is written, which is controlled by FSCR which would otherwise cause a 
facility unavailable interrupt.
+ 
+ [Test case]
+ apt-get source linux
+ cd linux-5.4.0/tools/testing/tools/selftests/powerpc/
+ make -j 32
+ make -C dscr run_tests
+ make -C ptrace run_tests
+ make -C tm run_tests
+ 
+ Look up for "not ok" versus "ok", specially for dscr_inherit_exec_test,
+ ptrace-tar and tm-resched-tar.
+ 
+ [Potential regression]
+ Manipulating DSCR might break on different machines (with DTs containing 
+ /cpus/ibm,powerpc-cpu-features, for example). Code that does so might crash 
because the facility unavailable interrupt handling might be not working 
correctly.
+ 
+ 
+ 
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)
  
-  # selftests: powerpc/dscr: dscr_inherit_exec_test 
-  # test: dscr_inherit_exec_test
-  # tags: git_version:unknown
-  # Parent DSCR 1 was not inherited over exec (kernel value)
-  # Child didn't exit cleanly
-  # failure: dscr_inherit_exec_test
-  not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1
+  # selftests: powerpc/dscr: dscr_inherit_exec_test
+  # test: dscr_inherit_exec_test
+  # tags: git_version:unknown
+  # Parent DSCR 1 was not inherited over exec (kernel value)
+  # Child didn't exit cleanly
+  # failure: dscr_inherit_exec_test
+  not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Code that touches DSCR user MSR does not set dscr_inherit, which breaks DSCR 
restore doing context switches and inheritance when forking. DSCR is used to 
control cache hinting. This is caused by lack of kernel interrupt when the DSCR 
user MSR is written, which is controlled by FSCR which would otherwise cause a 
facility unavailable interrupt.

  [Test case]
  apt-get source linux
  cd linux-5.4.0/tools/testing/tools/selftests/powerpc/
  make -j 32
  make -C dscr run_tests
  make -C ptrace run_tests
  make -C tm run_tests

  Look up for "not ok" versus "ok", specially for
  dscr_inherit_exec_test, ptrace-tar and tm-resched-tar.

  [Potential regression]
  Manipulating DSCR might break on different machines (with DTs containing 
  /cpus/ibm,powerpc-cpu-features, for example). Code that does so might crash 
because the facility unavailable interrupt handling might be not working 
correctly.

  
  
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1890136] Re: Fix false-negative return value for rtnetlink.sh in kselftests/net

[Ian]

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

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

Title:
  Fix false-negative return value for rtnetlink.sh in kselftests/net

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

Bug description:
  == Justification ==
  All the sub test cases in rtnetlink.sh from kselftests/net were using
  the same variable "ret" to store the return value of their test result,
  and it will be reset to 0 in the beginning of each test.

  This will cause false-negative result if the last case has passed.

  Also, the kci_test_encap() test in rtnetlink.sh is actually composed by
  two different sub-tests, kci_test_encap_vxlan() and kci_test_encap_fou()

  Therefore we should check the test result of these two to avoid
  false-negative result for this test case.

  == Fixes ==
  * c2a4d2747996 ("selftests: rtnetlink: correct the final return value for the 
test")
  * 72f70c159b53 ("selftests: rtnetlink: make kci_test_encap() return sub-test 
result")

  This issue is affecting our kernels from B to G, there is no such test
  in X thus it can be skipped.

  The first patch can be cherry-picked for E/F/G, but needs to be
  backported for B/D as they're missing some tests.
  The second patch can be cherry-picked for all affected kernels.

  == Test ==
  Manually tested. The test will fail as expected:
  $ sudo ./rtnetlink.sh
  PASS: policy routing
  PASS: route get
  echo $?
  PASS: preferred_lft addresses have expired
  PASS: promote_secondaries complete
  PASS: tc htb hierarchy
  PASS: gre tunnel endpoint
  PASS: gretap
  PASS: ip6gretap
  PASS: erspan
  PASS: ip6erspan
  PASS: bridge setup
  PASS: ipv6 addrlabel
  PASS: set ifalias a28e0b75-bcc7-4b62-8f5a-381215796229 for test-dummy0
  PASS: vrf
  PASS: vxlan
  FAIL: can't add fou port , skipping test
  PASS: macsec
  PASS: ipsec
  PASS: ipsec_offload
  PASS: bridge fdb get
  PASS: neigh get
  $ echo $?
  1

  == Regression Potential ==
  Low, changes limited to testing tools. It's expected to see this test
  failing after applying these patches, since it is reflecting the actual
  test result.


  == Original Bug Report ==
  In this test, it uses ret to store the return value of each test.

  However, this value will be reset to 0 in the beginning of each test.

  In the end of this test, it will judge PASS/FAIL base on this value.

  Thus this will cause false-negative in some cases.
  Below is an example for the test on Bionic OEM-OSP1, test "ip6erspan", 
"erspan", "ip6gretap" failed with return value 255, but the return value will 
soon be overridden with 0 if following test passed without any issue (I made 
the test to print === RET $ret === line for debugging purpose):

  PASS: policy routing
  === RET 0 ===
  PASS: route get
  === RET 0 ===
  PASS: preferred_lft addresses have expired
  === RET 0 ===
  PASS: tc htb hierarchy
  === RET 0 ===
  PASS: gre tunnel endpoint
  === RET 0 ===
  PASS: gretap
  === RET 0 ===
  Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
    [ local ADDR ]
    [ [i|o]seq ]
    [ [i|o]key KEY ]
    [ [i|o]csum ]
    [ hoplimit TTL ]
    [ encaplimit ELIM ]
    [ tclass TCLASS ]
    [ flowlabel FLOWLABEL ]
    [ dscp inherit ]
    [ fwmark MARK ]
    [ dev PHYS_DEV ]
    [ noencap ]
    [ encap { fou | gue | none } ]
    [ encap-sport PORT ]
    [ encap-dport PORT ]
    [ [no]encap-csum ]
    [ [no]encap-csum6 ]
    [ [no]encap-remcsum ]
    [ erspan IDX ]

  Where: ADDR  := IPV6_ADDRESS
     TTL   := { 0..255 } (default=64)
     KEY   := { DOTTED_QUAD | NUMBER }
     ELIM  := { none | 0..255 }(default=4)
     TCLASS:= { 0x0..0xff | inherit }
     FLOWLABEL := { 0x0..0xf | inherit }
     MARK  := { 0x0..0x | inherit }
  Cannot find device "ip6gretap00"
  FAIL: ip6gretap
  === RET 255 ===
  Usage: ... { gre | gretap | erspan } [ remote ADDR ]
  [ local ADDR ]
  [

[Kernel-packages] [Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled

[Matthew Ruffell]

I asked the customer to test 4.15.0-114-generic on Xenial HWE from
-proposed on their HP DL360 Gen10 machines with the Intel Xeon Gold 5120
CPU. The machine has Sub-NUMA Clustering enabled and it is active.

The machine boots successfully, and there are no call traces or kernel
oops present:

# uname -rv
4.15.0-114-generic #115~16.04.1-Ubuntu SMP Wed Aug 12 09:20:32 UTC 2020

[Tue Aug 25 16:42:20 2020] x86: Booting SMP configuration:
[Tue Aug 25 16:42:20 2020]  node #0, CPUs: #1 #2 #3 #4 #5 #6
[Tue Aug 25 16:42:20 2020]  node #1, CPUs: #7 #8 #9 #10 #11 #12 #13
[Tue Aug 25 16:42:20 2020]  node #0, CPUs: #14
[Tue Aug 25 16:42:20 2020] MDS CPU bug present and SMT on, data leak possible. 
See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for 
more details.
[Tue Aug 25 16:42:20 2020] TAA CPU bug present and SMT on, data leak possible. 
See 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html 
for more details.
[Tue Aug 25 16:42:20 2020] #15 #16 #17 #18 #19 #20
[Tue Aug 25 16:42:20 2020]  node #1, CPUs: #21 #22 #23 #24 #25 #26 #27
[Tue Aug 25 16:42:20 2020] smp: Brought up 2 nodes, 28 CPUs
[Tue Aug 25 16:42:20 2020] smpboot: Max logical packages: 1
[Tue Aug 25 16:42:20 2020] smpboot: Total of 28 processors activated (123200.00 
BogoMIPS)

This issue is fixed and I am happy to mark this bug verified.

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

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

Title:
  smpboot: don't call topology_sane() when Sub-NUMA-Clustering is
  enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

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

  [Impact]

  Intel Skylake server processors and onward have a different Last Level
  Cache (LLC) topology than earlier processors, and such processors have
  a new feature called Sub-NUMA-Clustering (SNC) which is similar to the
  existing Cluster-On-Die (CoD) feature earlier server processors has.

  Sub-NUMA-Clustering divides the system into two "slices", each of
  which are allocated half the CPU cores, half the Last Level Cache and
  one memory controller. Each slice is enumerated as a NUMA node.

  The difference between Sub-NUMA-Clustering and Cluster-On-Die is how
  the Last Level Cache is exposed to each NUMA node. CoD had the same
  cache line present in each half of the LLC. In SNC, each cache line is
  only present in its respective slice. Because of this, the semantics
  around accessing LLC changes, with a process accessing NUMA-local
  memory only seeing half the LLC capacity.

  On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and
  Bionic 4.15 kernels we see the following oops during NUMA node
  enumeration:

   node #0, CPUs: #1 #2 #3 #4 #5 #6
   node #1, CPUs: #7
  sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. 
Ignoring dependency.
  WARNING: CPU: 7 PID: 0 at 
/build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 
topology_sane.isra.4+0x6c/0x70
  Modules linked in:
  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu
  Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 
10/02/2018
  RIP: 0010:topology_sane.isra.4+0x6c/0x70
  Call Trace:
  set_cpu_sibling_map+0x153/0x540
  start_secondary+0xb2/0x200
  secondary_startup_64+0xa5/0xb0
  #8 #9 #10 #11 #12 #13
   node #0, CPUs: #14 #15 #16 #17 #18 #19 #20
   node #1, CPUs: #21 #22 #23 #24 #25 #26 #27
  smp: Brought up 2 nodes, 28 CPUs

  This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10.

  The oops happens because topology_sane() checks to see if the Last
  Level Cache line matches across different CPUs, which it no longer
  does.

  [Fix]

  The fix comes in the form of the following upstream commit, which
  landed in Linux 4.17:

  commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2
  Author: Alison Schofield 
  Date: Fri Apr 6 17:21:30 2018 -0700
  Subject: x86,sched: Allow topologies where NUMA nodes share an LLC
  Link: 
https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2

  The commit adds a check for this particular family of Intel
  processors, and if the CPU family matches, it simply skips the check
  to topology_sane().

  The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with
  the only remarks being re-arranging #includes and small context
  fixups.

  [Testcase]

  Unfortunately, this is hardware specific. To test this, you need a
  Intel Skylake server processor which supports Sub-NUMA-Clustering.

  We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10
  that has successfully tested the below test kernels, with good
  resul

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

Apparently, cherry-picking 0828137e8f16721842468e33df0460044a0c588b
("powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()") fixes the issue.
Which explains why 5.8 does not show the problem.

Building a kernel with that patch applied so I can test it.

Cascardo.

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  In Progress

Bug description:
  [Impact]
  Code that touches DSCR user MSR does not set dscr_inherit, which breaks DSCR 
restore doing context switches and inheritance when forking. DSCR is used to 
control cache hinting. This is caused by lack of kernel interrupt when the DSCR 
user MSR is written, which is controlled by FSCR which would otherwise cause a 
facility unavailable interrupt.

  [Test case]
  apt-get source linux
  cd linux-5.4.0/tools/testing/tools/selftests/powerpc/
  make -j 32
  make -C dscr run_tests
  make -C ptrace run_tests
  make -C tm run_tests

  Look up for "not ok" versus "ok", specially for
  dscr_inherit_exec_test, ptrace-tar and tm-resched-tar.

  [Potential regression]
  Manipulating DSCR might break on different machines (with DTs containing 
  /cpus/ibm,powerpc-cpu-features, for example). Code that does so might crash 
because the facility unavailable interrupt handling might be not working 
correctly.

  
  
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1891228] Re: Bionic update: upstream stable patchset 2020-08-11

[Ian]

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

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

Title:
  Bionic update: upstream stable patchset 2020-08-11

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-08-11

  Ported from the following upstream stable releases:
  v4.14.191, v4.19.136,
  v4.14.192, v4.19.137,
  v4.14.193, v4.19.138

     from git://git.kernel.org/

  AX.25: Fix out-of-bounds read in ax25_connect()
  AX.25: Prevent out-of-bounds read in ax25_sendmsg()
  dev: Defer free of skbs in flush_backlog
  drivers/net/wan/x25_asy: Fix to make it work
  net-sysfs: add a newline when printing 'tx_timeout' by sysfs
  net: udp: Fix wrong clean up for IS_UDPLITE macro
  rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA
  AX.25: Prevent integer overflows in connect and sendmsg
  ip6_gre: fix null-ptr-deref in ip6gre_init_net()
  rtnetlink: Fix memory(net_device) leak when ->newlink fails
  tcp: allow at most one TLP probe per flight
  regmap: debugfs: check count when read regmap file
  qrtr: orphan socket in qrtr_release()
  sctp: shrink stream outq only when new outcnt < old outcnt
  sctp: shrink stream outq when fails to do addstream reconf
  UBUNTU: upstream stable to v4.14.191, v4.19.136
  crypto: ccp - Release all allocated memory if sha type is invalid
  media: rc: prevent memory leak in cx23888_ir_probe
  iio: imu: adis16400: fix memory leak
  ath9k_htc: release allocated buffer if timed out
  ath9k: release allocated buffer if timed out
  PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge
  wireless: Use offsetof instead of custom macro.
  ARM: 8986/1: hw_breakpoint: Don't invoke overflow handler on uaccess 
watchpoints
  drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl()
  drm: hold gem reference until object is no longer accessed
  f2fs: check memory boundary by insane namelen
  f2fs: check if file namelen exceeds max value
  9p/trans_fd: abort p9_read_work if req status changed
  9p/trans_fd: Fix concurrency del of req_list in p9_fd_cancelled/p9_read_work
  x86/build/lto: Fix truncated .bss with -fdata-sections
  rds: Prevent kernel-infoleak in rds_notify_queue_get()
  xfs: fix missed wakeup on l_flush_wait
  net/x25: Fix x25_neigh refcnt leak when x25 disconnect
  net/x25: Fix null-ptr-deref in x25_disconnect
  selftests/net: rxtimestamp: fix clang issues for target arch PowerPC
  sh: Fix validation of system call number
  net: lan78xx: add missing endpoint sanity check
  net: lan78xx: fix transfer-buffer memory leak
  mlx4: disable device on shutdown
  mlxsw: core: Increase scope of RCU read-side critical section
  mlxsw: core: Free EMAD transactions using kfree_rcu()
  ibmvnic: Fix IRQ mapping disposal in error path
  bpf: Fix map leak in HASH_OF_MAPS map
  mac80211: mesh: Free ie data when leaving mesh
  mac80211: mesh: Free pending skb when destroying a mpath
  arm64/alternatives: move length validation inside the subsection
  arm64: csum: Fix handling of bad packets
  usb: hso: Fix debug compile warning on sparc32
  qed: Disable "MFW indication via attention" SPAM every 5 minutes
  nfc: s3fwrn5: add missing release on skb in s3fwrn5_recv_frame
  parisc: add support for cmpxchg on u8 pointers
  net: ethernet: ravb: exit if re-initialization fails in tx timeout
  Revert "i2c: cadence: Fix the hold bit setting"
  x86/unwind/orc: Fix ORC for newly forked tasks
  cxgb4: add missing release on skb in uld_send()
  xen-netfront: fix potential deadlock in xennet_remove()
  KVM: LAPIC: Prevent setting the tscdeadline timer if the lapic is hw disabled
  x86/i8259: Use printk_deferred() to prevent deadlock
  drm/amdgpu: fix multiple memory leaks in acp_hw_init
  selftests/net: psock_fanout: fix clang issues for target arch PowerPC
  net/mlx5: Verify Hardware supports requested ptp function on a given pin
  UBUNTU: upstream stable to v4.14.192, v4.19.137
  random32: update the net random state on interrupt and activity
  ARM: percpu.h: fix build error
  random: fix circular include dependency on arm64 after addition of percpu.h
  random32: remove net_rand_state from the latent entropy gcc plugin
  random32: move the pseudo-random 32-bit definitions to

[Kernel-packages] [Bug 1892091] Re: Bionic update: upstream stable patchset 2020-08-18

[Ian]

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

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

Title:
  Bionic update: upstream stable patchset 2020-08-18

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-08-18

  Ported from the following upstream stable releases:
 v4.19.139

     from git://git.kernel.org/

  USB: serial: qcserial: add EM7305 QDL product ID
  USB: iowarrior: fix up report size handling for some devices
  usb: xhci: define IDs for various ASMedia host controllers
  usb: xhci: Fix ASMedia ASM1142 DMA addressing
  Revert "ALSA: hda: call runtime_allow() for all hda controllers"
  ALSA: seq: oss: Serialize ioctls
  staging: android: ashmem: Fix lockdep warning for write operation
  Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
  Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
  Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt()
  omapfb: dss: Fix max fclk divider for omap36xx
  binder: Prevent context manager from incrementing ref 0
  vgacon: Fix for missing check in scrollback handling
  mtd: properly check all write ioctls for permissions
  leds: wm831x-status: fix use-after-free on unbind
  leds: da903x: fix use-after-free on unbind
  leds: lm3533: fix use-after-free on unbind
  leds: 88pm860x: fix use-after-free on unbind
  net/9p: validate fds in p9_fd_open
  drm/nouveau/fbcon: fix module unload when fbcon init has failed for some 
reason
  drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
  i2c: slave: improve sanity check when registering
  i2c: slave: add sanity check when unregistering
  usb: hso: check for return value in hso_serial_common_create()
  firmware: Fix a reference count leak.
  cfg80211: check vendor command doit pointer before use
  igb: reinit_locked() should be called with rtnl_lock
  atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
  tools lib traceevent: Fix memory leak in process_dynamic_array_len
  Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
  xattr: break delegations in {set,remove}xattr
  ipv4: Silence suspicious RCU usage warning
  ipv6: fix memory leaks on IPV6_ADDRFORM path
  net: ethernet: mtk_eth_soc: fix MTU warnings
  vxlan: Ensure FDB dump is performed under RCU
  net: lan78xx: replace bogus endpoint lookup
  hv_netvsc: do not use VF device if link is down
  net: gre: recompute gre csum for sctp over gre tunnels
  openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
  Revert "vxlan: fix tos value before xmit"
  selftests/net: relax cpu affinity requirement in msg_zerocopy test
  rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
  i40e: add num_vectors checker in iwarp handler
  i40e: Wrong truncation from u16 to u8
  i40e: Memory leak in i40e_config_iwarp_qvlist
  Smack: fix use-after-free in smk_write_relabel_self()
  UBUNTU: upstream stable to v4.19.139

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

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

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  In Progress

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test 
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

** Also affects: ubuntu-kernel-tests/trunk
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-kernel-tests

** No longer affects: ubuntu-kernel-tests/trunk

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  In Progress

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test 
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1888334] Re: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

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

Same thing as LP: #1888332. When writing to the privileged DSCR MSR
before running the remainder of the test, things will just work. This is
hinting again to dscr_inherit being unset when using the user DSCR MSR.

Cascardo.

** This bug has been marked a duplicate of bug 1888332
   [Potential Regression] dscr_inherit_exec_test from powerpc in 
ubuntu_kernel_selftests failed on B/E/F

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

Title:
  [Potential Regression] tm-resched-dscr from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Incomplete

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (skipped with P9 node)

  # selftests: powerpc/tm: tm-resched-dscr
  # test: tm_resched_dscr
  # tags: git_version:unknown
  # Binding to cpu 8
  # main test running as pid 142637
  # Check DSCR TM context switch: FAIL
  # failure: tm_resched_dscr
  not ok 1 selftests: powerpc/tm: tm-resched-dscr # exit=1

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

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

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

[John Hoff]

@gannon1

Mike, depending on your answers to my many questions from today, if the
only way we know to proceed is to build and test a patch, could you help
with building the patch (or at least the basic framework of the patch so
I can just plug in the CORB values)?  I used the attached spreadsheet to
parse out the values to hopefully make that process easier.  I am
comfortable making a new kernel if I have a probably valid patch, but I
am not as comfortable at this point making a good patch based on your
links.  I know I can and probably should learn that process, but I would
need to stand up a new machine and it would take much more time (and I
would really like to have sound again soon).

** Attachment added: "Play2Slim.ods"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404543/+files/Play2Slim.ods

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Relase of Ubuntu: 19.10

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

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

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

  !!DMI Information
  !!---

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

  
  !!Kernel Information
  !!--

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


  !!ALSA Version
  !!

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

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

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

  
  !!Soundcards recognised by ALSA
  !!-

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Packag

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

[John Hoff]

@gannon1

Some thoughts based on what I did today.  I did make a recording (twice
to make sure I didn't do it poorly) of the VM boot process.  So from the
time the VM initializes until you first see the win 10 desktop.  To my
surprise there is only 1 single CORB command during that process.  It is
this line and it is issued ~2173 times during the boot sequence of the
vm :

CORB[45] = 0x0 (caddr:0x0 nid:0x0 control:0x0 param:0x0)

So I don't think that was super helpful, other than it leads me to
believe that the audio device and speakers are not initialized until
needed, which might help shrink our search a bit.  I next took a simple
9 second wav file and placed it on the desktop.  I (trying 3 times to
make sure it was reproducible) booted the VM, cleared the logs, and then
clicked on the sound file to play it with media player.  It does play
through the speakers, so it seems like this data will have what we need.
I was also concerned that if the driver is enabled JIT then perhaps it
also disables it again when the sound ends, so I devised a way to
capture just the CORB commands between the time I clicked on the file
and I first heard sound

I then used scripting to reduce it to just the CORB[x] lines and that
gives us the attached smaller list of 944 CORB commands (attachment
Play2Slim).


** Attachment added: "Play2lim"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404542/+files/Play2Slim

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Relase of Ubuntu: 19.10

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

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

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

  !!DMI Information
  !!---

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

  
  !!Kernel Information
  !!--

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


  !!ALSA Version
  !!

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

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

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

  
  !!Soundcards recognised by ALSA
  !!-

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1888339] Re: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

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

Same issue as LP: #1888332. If we use DSCR privileged MSR when writing
in the tracee, it will set dscr_inherit, which will properly restore the
DSCR that is written by the tracer.

Cascardo.

** This bug has been marked a duplicate of bug 1888332
   [Potential Regression] dscr_inherit_exec_test from powerpc in 
ubuntu_kernel_selftests failed on B/E/F

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

Title:
  [Potential Regression] ptrace-tar from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Incomplete

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

  # selftests: powerpc/ptrace: ptrace-tar
  # test: ptrace_tar
  # tags: git_version:f21e446-dirty
  # [User Write (Running)] TAR: 10 PPR: 4 DSCR: 100
  # [User Read (Running)]  TAR: 20 PPR: 8 DSCR: 0
  # [Ptrace Read (Running)]TAR: 10 PPR: 4 DSCR: 100
  # [Ptrace Write (Running)]   TAR: 20 PPR: 8 DSCR: 200
  # failure: ptrace_tar
  not ok 4 selftests: powerpc/ptrace: ptrace-tar # exit=1

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

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

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-AC [1a56:143a]: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Nikolaj Løbner Sheller]

Sadly, the fix from LP:1891405 this does not seem to help in my case.

I did the following:
sudo add-apt-repository ppa:vicamo/ppa-1891405
sudo apt-get update
sudo apt upgrade
sudo reboot

After reboot I enabled WiFi and disabled Wired networking.

Wifi ran for 20 minutes before disconnecting.

Dmesg:
[   97.823914] pcieport :04:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
[ 1339.858946] ath10k_pci :02:00.0: failed to receive scan abortion 
completion: timed out

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-
  AC [1a56:143a]: Disabling wifi causes kernel warning in
  __sta_info_destroy_part2

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211]
  [ 3634.322902]  ? ath10k_warn.cold+0x1a/0x1f [ath10k_core]
  [ 3634.322911]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
  [ 3634.322913]  ? rtnl_is_locked+0x15/0x20
  [ 3634.322917]  ? inetdev_even

[Kernel-packages] [Bug 1854592] Re: kern.log flooded by ACPI error messages

[Alan AZZERA]

I can't as I'm already at the latest version. Is there a way to prevent
these messages to fill the logs ?

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

Title:
  kern.log flooded by ACPI error messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 19.10 AMD64 (completely up to date) on a Lenovo Thinkpad S1 Yoga 
12, and I've just noticed that /var/log/kern.log is flooded by messages like :
  Nov 30 21:12:44 yoga kernel: [  526.471259] ACPI: \_SB.PCI0.LPCB.EC0.ECRD: 1 
arguments were passed to a non-method ACPI object (RegionField) 
(20190703/nsarguments-204)
  Every about two seconds, 18 messages of this kind are recorded.
  What could I do to provide more informations ?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tley   1650 F pulseaudio
   /dev/snd/controlC1:  tley   1650 F pulseaudio
   /dev/snd/pcmC1D0p:   tley   1650 F...m pulseaudio
  Date: Sat Nov 30 21:18:09 2019
  InstallationDate: Installed on 2019-11-17 (13 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20DKS1MA00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=6662e662-b3da-478c-bf6b-ea7d12495e6e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JEET69WW (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DKS1MA00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJEET69WW(1.18):bd07/24/2015:svnLENOVO:pn20DKS1MA00:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DKS1MA00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S1 Yoga 12
  dmi.product.name: 20DKS1MA00
  dmi.product.sku: LENOVO_MT_20DK_BU_Think_FM_ThinkPad S1 Yoga 12
  dmi.product.version: ThinkPad S1 Yoga 12
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

This test failure is caused by the kernel not setting dscr_inherit when
the user dscr MSR is written to. Which is caused by FSCR not raising a
facility unavailable interrupt. Which is ironic as one of the other
patches that is backported is 993e3d96fd08c3ebf7566e43be9b8cd622063e6d
("powerpc/64s: Don't let DT CPU features set FSCR_DSCR"), which should
prevent this situation.

The reason dscr_inherit_test does not fail is because it writes to the
kernel MSR first. Changing dscr_inherit_exec_test to do the same, it
passes.

Testing 5.8 shows that it's fixed somehow, though I haven't found the
exact commit that would fix this. Reverting
912c0a7f2b5daa3cbb2bc10f303981e493de73bd ("powerpc/64s: Save FSCR to
init_task.thread.fscr after feature init") seems reasonable here.

But failing to inherit dscr would cause cache performance regressions
that are hard to justify respining the kernel for.

Cascardo.

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

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Won't Fix

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test 
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

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

Title:
  ACPI Error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
  -


  
  [0.297458] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297464] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297468] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297472] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297482] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297485] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297489] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297492] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297502] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297506] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297509] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297512] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297523] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297526] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297529] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297533] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297543] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297546] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297550] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297553] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297563] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297566] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297570] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297573] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297583] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297586] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297590] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297593] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297603] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.297607] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297610] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297614] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297623] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
  [0.297627] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
  [0.297630] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
  [0.297634] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
  [0.

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Confirmed

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test 
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1892909] [NEW] ACPI Error

[estebanalmeida]

Public bug reported:

5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
-


[0.297458] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297464] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297468] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297472] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297482] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297485] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297489] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297492] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297502] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297506] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297509] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297512] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297523] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297526] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297529] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297533] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297543] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297546] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297550] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297553] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297563] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297566] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297570] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297573] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297583] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297586] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297590] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297593] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297603] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297607] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297610] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297614] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297623] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKD (20190816/dspkginit-438)
[0.297627] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297630] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297634] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297644] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKA (20190816/dspkginit-438)
[0.297647] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKB (20190816/dspkginit-438)
[0.297650] ACPI Error: AE_NOT_FOUND, While resolving a named reference 
package element - LNKC (20190816/dspkginit-438)
[0.297654] ACPI Error: AE_NOT_FOUND,

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-AC [1a56:143a]: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Alex Hung]

Perhaps vicamo's comments #19 on LP:1891405 will 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/1872351

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-
  AC [1a56:143a]: Disabling wifi causes kernel warning in
  __sta_info_destroy_part2

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211]
  [ 3634.322902]  ? ath10k_warn.cold+0x1a/0x1f [ath10k_core]
  [ 3634.322911]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
  [ 3634.322913]  ? rtnl_is_locked+0x15/0x20
  [ 3634.322917]  ? inetdev_event+0x47/0x560
  [ 3634.322919]  ? skb_dequeue+0x5a/0x70
  [ 3634.322923]  notifier_call_chain+0x55/0x80
  [ 3634.322925]  raw_notifier_call_chain+0x16/0x20
  [ 3634.322927]  call_netdevice_notifiers_info+0x2e/0x60
  [ 3634.322929]  __dev_close_many+0x63/0x120
  [ 3634.322931]  dev_close_many+0x91/0x150
  [ 3634.322933]  dev_close.part.0+0x4a/0x70
  [ 3634.322936]  dev_close+0x18/0x20
  [ 3634.322955]  cfg80211_shutdown_all_interfaces+0x77

[Kernel-packages] [Bug 1886588] Re: ath10k_pci often crashes in focal

[Alex Hung]

vicamo posted a probable solution @
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891405. See #19
for more details

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

Title:
  ath10k_pci often crashes in focal

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WIreless connectivity has been very flaky in focal ever since release.
  Thought I'd start investigating a bit. This is all I found, but it
  clearly signisfies an error. Please let med know, if I can provide
  more information.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: firmware crashed! (guid 
ba24fee9-d0cb-42e2-9aef-06f0d07a053e)
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 
1 tracing 1 dfs 0 testmode 0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: board_file api 2 bmi_id 
N/A crc32 4ac0889b
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: htt-ver 3.60 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to get memcpy hi 
address for firmware address 4: -16
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to read firmware 
dump area: -16
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: Copy Engine register 
dump:
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [00]: 0x00034400  11  11 
  3   3
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [01]: 0x00034800   3   2 
175 176
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [02]: 0x00034c00  12  11 
 10  11
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [03]: 0x00035000  12  12 
 14  12
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [04]: 0x00035400 6557 
6549  11 203
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [05]: 0x00035800   0   0 
 64   0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [06]: 0x00035c00   3   1 
 10   8
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: [07]: 0x00036000   1   0 
  1   0
  [ma. juli  6 23:16:50 2020] ath10k_pci :3b:00.0: failed to read 
hi_board_data address: -28
  [ma. juli  6 23:16:51 2020] ieee80211 phy0: Hardware restart was requested
  [ma. juli  6 23:16:51 2020] ath10k_pci :3b:00.0: unsupported HTC service 
id: 1536
  [ma. juli  6 23:16:51 2020] ath10k_pci :3b:00.0: device successfully 
recovered
  [ma. juli  6 23:19:57 2020] mce: CPU2: Core temperature above threshold, cpu 
clock throttled (total events = 6714)
  [ma. juli  6 23:19:57 2020] mce: CPU1: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU5: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU4: Package temperature above threshold, 
cpu clock throttled (total events = 20892)
  [ma. juli  6 23:19:57 2020] mce: CPU2: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU0: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU3: Package temperature above threshold, 
cpu clock throttled (total events = 20893)
  [ma. juli  6 23:19:57 2020] mce: CPU2: Core temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU1: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU5: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU4: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU2: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU0: Package temperature/speed normal
  [ma. juli  6 23:19:57 2020] mce: CPU3: Package temperature/speed normal
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:08 2020] veth76e34af: renamed from eth0
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:08 2020] device veth76af7ee left promiscuous mode
  [ma. juli  6 23:20:08 2020] docker0: port 1(veth76af7ee) entered disabled 
state
  [ma. juli  6 23:20:18 2020] wlp59s0: deauthenticating from 00:22:07:80:6c:2e 
by local choice (Reason: 3=DEAUTH_LEAVING)
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  [ma. juli  6 23:21:46 2020] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 
1 tracing 1 dfs 0 testmode 0
  [ma. juli  6 23:21:

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Thanks Helmut and Francesco

I have a (bold ?) question.

As previously reported, it works (at least, moves and clicks as
expected, not talking gestures here) in the UEFI BIOS prior to the
loading of any operating system.

Does this mean there is a kind of working driver in code of the UEFI
BIOS ? If yes, any hope to get it from Lenovo or other vendors ?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegio

[Kernel-packages] [Bug 1892012] Re: Bluetooth doesn't turn on

[Alex Hung]

This sounds like Bluetooth hardware malfunctions until a full reset (or
completely powered off).

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

Title:
  Bluetooth doesn't turn on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UPDATE
  ==

  I tried another kernel (`5.4.0-40-generic` and it didn't worked.
  Trying to reboot (and get back to the latest kernel) it didn't shutdown, so I 
hard shutdown it, and restart with the `5.4.0-42-generic`.

  And now, it works.
  I hope the logs below may help you to find out what happened, and help others 
to fix their issue if it's similar to this one.

  ---

  
  Hello,

  For now, everything worked fine, until this morning when Bluetooth
  stop working.

  Ubuntu 20.04

  **What expected to happen :** Bluetooth turn on on start, and if it's
  off it turns on when I turn it on.

  **What happens :** it doesn't turn on.

  ```
   $ dmesg | grep -i blue
  [2.433133] Bluetooth: Core ver 2.22
  [2.433147] Bluetooth: HCI device and connection manager initialized
  [2.433149] Bluetooth: HCI socket layer initialized
  [2.433151] Bluetooth: L2CAP socket layer initialized
  [2.433153] Bluetooth: SCO socket layer initialized
  [3.559082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.559083] Bluetooth: BNEP filters: protocol multicast
  [3.559088] Bluetooth: BNEP socket layer initialized
  [4.456149] Bluetooth: hci0: command 0xfc05 tx timeout
  [4.456167] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  ```

  Last `/var/log/dpkg.log` logs (previous were from 3 days ago)
  ```
  2020-08-18 01:06:02 startup archives unpack
  2020-08-18 01:06:03 install python3-blessings:all  1.6-3
  2020-08-18 01:06:03 status half-installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 install python3-pynvml:amd64  7.352.0-3
  2020-08-18 01:06:03 status half-installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 install gpustat:all  0.6.0-1
  2020-08-18 01:06:03 status half-installed gpustat:all 0.6.0-1
  2020-08-18 01:06:03 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:03 startup packages configure
  2020-08-18 01:06:03 configure python3-blessings:all 1.6-3 
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status half-configured python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 configure python3-pynvml:amd64 7.352.0-3 
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status half-configured python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 status installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 configure gpustat:all 0.6.0-1 
  2020-08-18 01:06:04 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status half-configured gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status installed gpustat:all 0.6.0-1

  ```

  ```
   $ dpkg -l | grep -i blue
  ii  bluez 5.53-0ubuntu3   
  amd64Bluetooth tools and daemons
  ii  bluez-cups5.53-0ubuntu3   
  amd64Bluetooth printer driver for CUPS
  ii  bluez-obexd   5.53-0ubuntu3   
  amd64bluez obex daemon
  ii  gir1.2-gnomebluetooth-1.0:amd64   3.34.1-1
  amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth   3.34.1-1
  amd64GNOME Bluetooth tools
  ii  libbluetooth3:amd64   5.53-0ubuntu3   
  amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd643.34.1-1
  amd64GNOME Bluetooth tools - support library
  ii  libkf5bluezqt-data5.68.0-0ubuntu1 
  all  data files for bluez-qt
  ii  libkf5bluezqt6:amd64  5.68.0-0ubuntu1 
  amd64Qt wrapper for bluez
  ii  node-bluebird 3.5.1+dfsg2-2build1 
  all  Fully featured Promises/A+ implementation for Node.js
  ii  pulseaudio-module-bluetooth   1:13.99.1-1ubuntu3.5
  amd64Bluetooth module for PulseAudio sound server
  ii  qml-module-org-kde-bluezqt:amd64  5.68.0-0ubuntu1 
  amd64QML wrapper for bluez
  ```

  ```
   $ sudo service bluetooth status
  [sudo] password for brieucdug:
  ● bluetooth.service - Bluetooth service
   

[Kernel-packages] [Bug 1892547] Re: [ 0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) [ 0.172444] ACPI Exception: Could not find/resolve named pac

[Alex Hung]

This should be an ACPI BIOS bug, and there is not much to be done in
Linux.

An acpidump log (sudo acpidump > acpi.log) is required for more analysis
of what functions are impacted.

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

Title:
  [0.172384] ACPI Exception: Could not find/resolve named package
  element: OC06 (20170831/dspkginit-381) [0.172444] ACPI Exception:
  Could not find/resolve named package element: OC07
  (20170831/dspkginit-381)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [0.172384] ACPI Exception: Could not find/resolve named package
  element: OC06 (20170831/dspkginit-381)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-112-generic 4.15.0-112.113
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xilion 1667 F pulseaudio
  CurrentDesktop: LXDE
  Date: Fri Aug 21 22:15:54 2020
  HibernationDevice: RESUME=UUID=3a74be02-d33e-4932-8d91-4d1fa8672def
  InstallationDate: Installed on 2018-06-18 (795 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig:
   lono wireless extensions.
   
   enp0s29f7u2  no wireless extensions.
   
   enp1s3no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=4ed73824-614c-4c5a-a4ca-782b0ed7ace2 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-112-generic N/A
   linux-backports-modules-4.15.0-112-generic  N/A
   linux-firmware  1.173.19
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0301
  dmi.board.name: P5GPL-X SE
  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.:bvr0301:bd06/09/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5GPL-XSE: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/ubuntu/+source/linux/+bug/1892547/+subscriptions

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

[Kernel-packages] [Bug 1874503] Re: Mellanox Check For Write Combining Support

[Marcelo Cerri]

Patches were submitted to mailing review:
https://lists.ubuntu.com/archives/kernel-team/2020-August/112961.html

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

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

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

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

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

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

** Changed in: linux-azure-4.15 (Ubuntu Focal)
   Status: New => Invalid

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

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

** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  Mellanox Check For Write Combining Support

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  [Impact]

  Microsoft and Mellanox would like to request the following two commits
  in the releases that run on Azure:

  3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 
defines
  11f552e21755 IB/mlx5: Test write combining support

  These commits landed in mainline as of v5.5-rc1.

  These commits will improved network performance of RDMA out of the VF
  when WC can be used. The highest benefit is to RDMA and DPDK, but UCX
  should also see improved latency.

  The Mellanox driver uses WC to optimize posting work to the HCA, and
  getting this wrong in either direction can cause a significant
  performance loss.  These patches prevent the possible performance
  loss.

  [Test Case]

  Simply measure the network performance with the patches applied to
  check if there was some gain.

  [Regression Potential]

  It affects mainly the mlx5 driver and IB, while many of the instances
  do not make use of those, they are used by the high performance users.

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

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

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Noctis Bennington]

Oh, okey, I'll do it later.

I presume I have to do it with the actual kernel of 20.04? (5.4.0) Or
with the last kernel or...?

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).


  WORKAROUND: I installed the 4.15 kernel, so at the moment I can work
  with this. Higher than 4.15 the second monitor doesn't work. Tested
  until 5.8 and without good results. Just with 4.15.

  
  ---
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440

[Kernel-packages] [Bug 1892899] Re: Focal update: v5.4.60 upstream stable release

[Kamal Mostafa]

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.60 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.60 upstream stable release
-from git://git.kernel.org/
+ smb3: warn on confusing error scenario with sec=krb5
+ genirq/affinity: Make affinity setting if activated opt-in
+ genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()
+ PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context()
+ PCI: Add device even if driver attach failed
+ PCI: qcom: Define some PARF params needed for ipq8064 SoC
+ PCI: qcom: Add support for tx term offset for rev 2.1.0
+ btrfs: allow use of global block reserve for balance item deletion
+ btrfs: free anon block device right after subvolume deletion
+ btrfs: don't allocate anonymous block device for user invisible roots
+ btrfs: ref-verify: fix memory leak in add_block_entry
+ btrfs: stop incremening log_batch for the log root tree when syncing log
+ btrfs: remove no longer needed use of log_writers for the log root tree
+ btrfs: don't traverse into the seed devices in show_devname
+ btrfs: open device without device_list_mutex
+ btrfs: move the chunk_mutex in btrfs_read_chunk_tree
+ btrfs: relocation: review the call sites which can be interrupted by signal
+ btrfs: add missing check for nocow and compression inode flags
+ btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on 
relocation tree
+ btrfs: sysfs: use NOFS for device creation
+ btrfs: don't WARN if we abort a transaction with EROFS
+ btrfs: fix race between page release and a fast fsync
+ btrfs: fix messages after changing compression level by remount
+ btrfs: only search for left_info if there is no right_info in 
try_merge_free_space
+ btrfs: inode: fix NULL pointer dereference if inode doesn't need compression
+ btrfs: fix memory leaks after failure to lookup checksums during inode logging
+ btrfs: make sure SB_I_VERSION doesn't get unset by remount
+ btrfs: fix return value mixup in btrfs_get_extent
+ arm64: perf: Correct the event index in sysfs
+ dt-bindings: iio: io-channel-mux: Fix compatible string in example code
+ iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw()
+ xtensa: add missing exclusive access state management
+ xtensa: fix xtensa_pmu_setup prototype
+ cifs: Fix leak when handling lease break for cached root fid
+ powerpc/ptdump: Fix build failure in hashpagetable.c
+ powerpc: Allow 4224 bytes of stack expansion for the signal frame
+ powerpc: Fix circular dependency between percpu.h and mmu.h
+ pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH
+ media: vsp1: dl: Fix NULL pointer dereference on unbind
+ net: ethernet: stmmac: Disable hardware multicast filter
+ net: stmmac: dwmac1000: provide multicast filter fallback
+ net/compat: Add missing sock updates for SCM_RIGHTS
+ md/raid5: Fix Force reconstruct-write io stuck in degraded raid5
+ bcache: allocate meta data pages as compound pages
+ bcache: fix overflow in offset_to_stripe()
+ mac80211: fix misplaced while instead of if
+ driver core: Avoid binding drivers to dead devices
+ MIPS: CPU#0 is not hotpluggable
+ MIPS: qi_lb60: Fix routing to audio amplifier
+ ext2: fix missing percpu_counter_inc
+ khugepaged: collapse_pte_mapped_thp() flush the right range
+ khugepaged: collapse_pte_mapped_thp() protect the pmd lock
+ ocfs2: change slot number type s16 to u16
+ mm/page_counter.c: fix protection usage propagation
+ mm/memory_hotplug: fix unpaired mem_hotplug_begin/done
+ ftrace: Setup correct FTRACE_FL_REGS flags for module
+ kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler
+ tracing/hwlat: Honor the tracing_cpumask
+ tracing: Use trace_sched_process_free() instead of exit() for pid tracing
+ tracing: Move pipe reference to trace array instead of current_tracer
+ watchdog: f71808e_wdt: indicate WDIOF_CARDRESET support in 
watchdog_info.options
+ watchdog: f71808e_wdt: r

[Kernel-packages] [Bug 1874503] Re: Mellanox Check For Write Combining Support

[Marcelo Cerri]

** Description changed:

+ [Impact]
+ 
  Microsoft and Mellanox would like to request the following two commits
  in the releases that run on Azure:
  
  3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 
defines
  11f552e21755 IB/mlx5: Test write combining support
  
  These commits landed in mainline as of v5.5-rc1.
  
  These commits will improved network performance of RDMA out of the VF
  when WC can be used. The highest benefit is to RDMA and DPDK, but UCX
  should also see improved latency.
  
  The Mellanox driver uses WC to optimize posting work to the HCA, and
  getting this wrong in either direction can cause a significant
  performance loss.  These patches prevent the possible performance loss.
+ 
+ [Test Case]
+ 
+ Simply measure the network performance with the patches applied to check
+ if there was some gain.
+ 
+ [Regression Potential]
+ 
+ It affects mainly the mlx5 driver and IB, while many of the instances do
+ not make use of those, they are used by the high performance users.

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

Title:
  Mellanox Check For Write Combining Support

Status in linux-azure package in Ubuntu:
  New

Bug description:
  [Impact]

  Microsoft and Mellanox would like to request the following two commits
  in the releases that run on Azure:

  3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 
defines
  11f552e21755 IB/mlx5: Test write combining support

  These commits landed in mainline as of v5.5-rc1.

  These commits will improved network performance of RDMA out of the VF
  when WC can be used. The highest benefit is to RDMA and DPDK, but UCX
  should also see improved latency.

  The Mellanox driver uses WC to optimize posting work to the HCA, and
  getting this wrong in either direction can cause a significant
  performance loss.  These patches prevent the possible performance
  loss.

  [Test Case]

  Simply measure the network performance with the patches applied to
  check if there was some gain.

  [Regression Potential]

  It affects mainly the mlx5 driver and IB, while many of the instances
  do not make use of those, they are used by the high performance users.

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

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

[Kernel-packages] [Bug 1892899] [NEW] Focal update: v5.4.60 upstream stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

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

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

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Focal update: v5.4.60 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

[Kai-Heng Feng]

https://lkml.org/lkml/2020/8/25/934

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Screen flickers when using radeon.ko.
  It's a regression, it didn't happen on Trusty.

  [Fix]
  Quote the original commit log:
  "Instead of the closest reference divider prefer the lowest".

  [Test]
  Affected user confirms it fixes the issue.

  [Regression Potential]
  Low. Only affect radeaon, and it's in upstream stable tree.

  === Original Bug Report ===
  my laptop: HP Compaq nx9420
  my grafic card:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54

[Kai-Heng Feng]

https://lkml.org/lkml/2020/8/25/934

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

Title:
  Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
  upgrade kernel 4.15.0-54

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
  This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX 
and so on.
  I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 
kernel). I cannot upgrade to newer kernels.
  Seems that the fixes for bug #1791312 broke my kind of card.

  here is a video:
  https://youtu.be/9Rez7s0V6iA

  here is another user with same problem:
  https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005

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

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

[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

[Kai-Heng Feng]

Noctis Bennington,

Please install "intel-gpu-tools", then boot with kernel parameter
"blacklist=i915,snd_hda_intel modprobe.blacklist=i915,snd_hda_intel 3".

You might need to switch to other tty to see the login prompt.

Then read the register via the following command:
intel_reg read --count 20 0x64E00 0x64E60 0x64EC0 0x64F20 0x64F80
intel_reg read 0x64000 0x64100 0x64200 0x64300 0x64400 0x6C00C

Reply from Intel GFX devs:
https://lore.kernel.org/intel-gfx/20200824180438.gi6...@intel.com/

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).


  WORKAROUND: I installed the 4.15 kernel, so at the moment I can work
  with this. Higher than 4.15 the second monitor doesn't work. Tested
  until 5.8 and without good results. Just with 4.15.

  
  ---
  Proble

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Helmut Stult]

Right, it affects all MSFT touchpads.
At the moment there is nothing for MSFT - we will have to be very patient and 
hope, that someone can find a driver for it.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.v

[Kernel-packages] [Bug 1891811] Re: doesnt recognize the trackpad

[Kai-Heng Feng]

Is the trackpad connected via Bluetooth?

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

Title:
  doesnt recognize the trackpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  cat /proc/bus/input/devices doesnt show touchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thiago 1569 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 13:41:16 2020
  InstallationDate: Installed on 2020-08-15 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp1s0f0  no wireless extensions.
   
   usb0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. Macmini6,1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1b99b69-6ce5-4c95-80ca-69c1e70dff35 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 286.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031AEE4D24BFF0B1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini6,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-031AEE4D24BFF0B1
  dmi.modalias: 
dmi:bvnAppleInc.:bvr286.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacmini6,1:pvr1.0:rvnAppleInc.:rnMac-031AEE4D24BFF0B1:rvrMacmini6,1:cvnAppleInc.:ct16:cvrMac-031AEE4D24BFF0B1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini6,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Launchpad Bug Tracker]

This bug was fixed in the package bcache-tools - 1.0.8-2ubuntu0.18.04.1

---
bcache-tools (1.0.8-2ubuntu0.18.04.1) bionic; urgency=medium

  [ Ryan Harper ]
  * Add helper script to read bcache devs superblock (LP: #1861941)

 -- Rafael David Tinoco   Wed, 05 Aug 2020
17:44:05 -0300

** Changed in: bcache-tools (Ubuntu Bionic)
   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/1861941

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.

   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev events that were being read and filling
  the symlinks. We decided not to remove those (just from Groovy and on)
  so we don't need to worry on Breaks/Conflicts in between the kernel
  package and bcache-tools (and udev)).

   * Long story short: kernel will continue to emit bcache udev events
  as it did previously but now those events won't be used by anything -
  after installing this SRU - because udev wrapper script is doing this
  job (and doing it properly)

  [Other Info]

  - Original Description:

  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 5.4.0.12.15
    Candidate: 5.4.0.12.15
    Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
  linux-image-5.4.0-12-generic:
    Installed: 5.4.0-12.15
    Candidate: 5.4.0-12.15
    Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)

[Kernel-packages] [Bug 1892890] Re: The eggs were off and it hurts my belly.

[Tom Reynolds]

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

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

Title:
  The eggs were off and it hurts my belly.

Status in linux-lts-utopic package in Ubuntu:
  Invalid

Bug description:
  I bought some "posh" eggs, but when I ate them they were unhygienic.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Aug 25 14:37:28 2020
  InstallationDate: Installed on 2020-08-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1887294] Re: [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB

[fa2k]

One more crash on driver  450.57-0ubuntu0~0.20.04.4. I lost the dmesg
file, but it's pretty similar. Now I will update to
450.66-0ubuntu0~0.20.04.2.

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

Title:
  [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New

Bug description:
  The display is completely frozen, and no signal is output to the
  monitors. There is also no signal when switching to a console (Ctr-
  Alt-F1). I have normal access via SSH.

  It happens about once in 14 days. Only happens when turning the
  display off or on (about once in 15 screen power cycles).

  nvidia-smi still works (via SSH; without any options)

  DISPLAY=:1 xset dpms force on

  hangs indefinitely.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul 12 17:47:58 2020
  DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] 
https://repo.skype.com/deb stable main # disabled on upgrade to focal' was 
disabled (unknown mirror)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae]
  InstallationDate: Installed on 2016-07-27 (1445 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago)
  dmi.bios.date: 04/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8C WS
  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.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Jul  7 22:02:38 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post t

[Kernel-packages] [Bug 1892890] [NEW] The eggs were off and it hurts my belly.

[Harry Allan]

Public bug reported:

I bought some "posh" eggs, but when I ate them they were unhygienic.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
CurrentDesktop: Unity
Date: Tue Aug 25 14:37:28 2020
InstallationDate: Installed on 2020-08-25 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

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

Title:
  The eggs were off and it hurts my belly.

Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  I bought some "posh" eggs, but when I ate them they were unhygienic.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Aug 25 14:37:28 2020
  InstallationDate: Installed on 2020-08-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support

[Rex Tsai]

** No longer affects: oem-priority

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

Title:
  Harrison Peak  wifi / BT support

Status in HWE Next:
  New
Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  HrP2 will be supported in CML/TGL platform.

  Target Release: 20.04
  Target Kernel: 5.4

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

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

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Vedran Rafaelic]

Now after 15 min of sound and mic the audio playing crashed (youtube
video spins forever, audio tests in Settings dont work...).

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

Title:
  Microphone not working on HP Omen 17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Vedran Rafaelic]

After removing this option the internal mic works (the noise is
relatively high).

On Settings->Sound  I see Output Device: Speaker - Cannon Lake PCH cAVS
and Input Device: Digital Microphone - Cannon Lake PCH cAVS
(Both input and output with generic melody icon before them)

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

Title:
  Microphone not working on HP Omen 17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Vedran Rafaelic]

*or immediately after login (in 90% of cases, so i restarted it now like
10 times.)

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

Title:
  Microphone not working on HP Omen 17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17

[Vedran Rafaelic]

@Hui Wang
As I said, without this option my laptop freezes on login screen or immediately 
(in 90% of cases). I managed to start it now long enough to make a dmesg 
without dmic_detect=0. Not sure if it will freeze soon.


** Attachment added: "dmesg without option dmic_detect=0"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+attachment/5404437/+files/dmesg_new.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/1892714

Title:
  Microphone not working on HP Omen 17

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the following laptop https://support.hp.com/us-en/product/omen-
  by-hp-17-cb-laptop-pc/26122176/document/c06411586

  I cannot make the internal microphone to work. Sound->Input device
  gives no device list. Jack plug (pink) mic works.

  (The link says: HP Wide Vision HD Camera with integrated dual array
  digital microphone. So I guess this is the one and only internal
  microphone.)

  cat /proc/asound/card0/codec* | grep Codec   Codec: Realtek ALC285
  cat /proc/asound/card1/codec* | grep Codec   Codec: Nvidia GPU 92 HDMI/DP

  I guess the internal microphone is related to this "Realtek ALC285"
  codec.

  
  In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or 
otherwise my screen freezes soon after boot.

  I tried "options snd-hda-intel model=laptop-amic" and "model=laptop-
  dmic" and "model=auto". The "model=laptop-dmic" shows the device in
  "Sound->Input device" but it loops laptop's sound output into the
  input.

  
  OS: Ubuntu 20.04
  uname -a: 5.4.0-42-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  croraf 1940 F pulseaudio
   /dev/snd/controlC0:  croraf 1940 F pulseaudio
   /dev/snd/pcmC0D0p:   croraf 1940 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-16 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 7NG00EA#BED
  dmi.sys.vendor: HP

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

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

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

[John Hoff]

@gannon1

I am also going to create a new recording today that is just the VM
booting.  It seems to me that our problem may not be the audio device
itself, but the AKG smart amp not turning on.  I am not confident that
the disable and re-enable I was doing of the realtek audio device in
windows impacts the amp.  It might, but I know for sure that when I boot
the VM the speakers are made active because the sound works at that
point.  Also, I had to bind 4 different things to my immot group to make
this all work, so that also makes me think it is not just a single
device we are after

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Relase of Ubuntu: 19.10

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

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

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

  !!DMI Information
  !!---

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

  
  !!Kernel Information
  !!--

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


  !!ALSA Version
  !!

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

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

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

  
  !!Soundcards recognised by ALSA
  !!-

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /de

[Kernel-packages] [Bug 1892880] [NEW] WiFi connection is slow and occasionally drops

[John Haddad]

Public bug reported:

WiFi connection has high latency and slow speeds and is occasionally
dropped. Connecting to a TP-Link Archer A20 V1. Windows driver is
stable.

apt-cache policy bcmwl-kernel-source
bcmwl-kernel-source:
  Installed: 6.30.223.271+bdcom-0ubuntu5
  Candidate: 6.30.223.271+bdcom-0ubuntu5
  Version table:
 *** 6.30.223.271+bdcom-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages
100 /var/lib/dpkg/status

sudo lspci -vvnn | grep -A 9 Network
pcilib: sysfs_read_vpd: read failed: Input/output error
06:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4360 
802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
Subsystem: ASUSTeK Computer Inc. BCM4360 802.11ac Wireless Network 
Adapter [1043:85df]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

sudo dmidecode -s bios-version
2501

sudo dmidecode -s bios-release-date
07/21/2014

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 25 09:00:47 2020
InstallationDate: Installed on 2020-07-31 (25 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  WiFi connection is slow and occasionally drops

Status in bcmwl package in Ubuntu:
  New

Bug description:
  WiFi connection has high latency and slow speeds and is occasionally
  dropped. Connecting to a TP-Link Archer A20 V1. Windows driver is
  stable.

  apt-cache policy bcmwl-kernel-source
  bcmwl-kernel-source:
Installed: 6.30.223.271+bdcom-0ubuntu5
Candidate: 6.30.223.271+bdcom-0ubuntu5
Version table:
   *** 6.30.223.271+bdcom-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  sudo lspci -vvnn | grep -A 9 Network
  pcilib: sysfs_read_vpd: read failed: Input/output error
  06:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4360 
802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
Subsystem: ASUSTeK Computer Inc. BCM4360 802.11ac Wireless Network 
Adapter [1043:85df]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  sudo dmidecode -s bios-version
  2501

  sudo dmidecode -s bios-release-date
  07/21/2014

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 25 09:00:47 2020
  InstallationDate: Installed on 2020-07-31 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[John Hoff]

@gannon1

Not sure what happened to the enable file, here it is again...

Anyway, on your other comment, I assume the Verb ID and Payload you
mention would be the control and param values from my logging?

Do you know if that is a way to do this troubleshooting with the hda
verb approach as opposed to a patch (i.e. do you know how to properly
map the values from my new logging to HDA Verbs or is there another way
to execute the commands)?  I ask because I am not confident in my
ability to create a perfect patch on a single try (never having done it
before) and this is my main work computer, so I need to be somewhat
careful.  I could try the patch approach in a linux VM maybe, but not
sure if that would be predictable

** Attachment added: "Enable"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404413/+files/Enable

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Relase of Ubuntu: 19.10

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

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

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

  !!DMI Information
  !!---

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

  
  !!Kernel Information
  !!--

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


  !!ALSA Version
  !!

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

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

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

  
  !!Soundcards recognised by ALSA
  !!-

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ub

[Kernel-packages] [Bug 1882039] Re: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs

[Gavin Guo]

** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal

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

Title:
  The thread level parallelism would be a bottleneck when searching for
  the shared pmd by using hugetlbfs

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

Bug description:
  [Impact]

  There is performance overhead observed when many threads
  are using hugetlbfs in the database environment.

  [Fix]

  bdfbd98bc018 hugetlbfs: take read_lock on i_mmap for PMD sharing

  The patch improves the locking by using the read lock instead of the
  write lock. And it allows multiple threads searching the suitable shared
  VMA. As there is no modification inside the searching process. The 
  improvement increases the parallelism and decreases the waiting time of
  the other threads.

  [Test]

  The customer stand-up a database with seed data. Then they have a
  loading "driver" which makes a bunch of connections that look like user
  workflows from the database perspective. Finally, the measuring response
  times improvement can be observed for these "users" as well as various
  other metrics at the database level.

  [Regression Potential]

  The modification is only in replacing the write lock to a read one. And 
  there is no modification inside the loop. The regression probability is
  low.

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

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

[Kernel-packages] [Bug 1892849] Re: [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support

[Frank Heimes]

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Frank Heimes (fheimes)
   Status: New

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

Title:
  [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New

Bug description:
  Problem description:

  When a NVMe drive is assigned/hotplugged to a Linux LPAR then
  a bug is hit in lib/list_debug.c. And the device is not accessible, there is 
no /dev/ file
  and lspci does not report it also.

  
  [ 1681.564462] list_add double add: new=eed0f808, 
prev=eed0f808, next=4070a300.
  [ 1681.564489] [ cut here ]
  [ 1681.564490] kernel BUG at lib/list_debug.c:31!
  [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP
  [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter 
ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat 
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat 
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 
des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch 
vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 
sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio 
ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt
  [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2
  [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR)
  [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 
(__list_add_valid+0x70/0xa8)
  [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [ 1681.564545] Krnl GPRS: 0040 0027 0058 
0007
  [ 1681.564546]3ffcadb4   
03e0051a7ce0
  [ 1681.564547]4070a300 eed0f808 eed0f808 
4070a300
  [ 1681.564548]f56a2000 40c2c788 3ffcadb4 
03e0051a7bc8
  [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl
%r2,405d03ba
3ffcadae: c0e5ffdd30b1brasl   
%r14,3fb70f10
   #3ffcadb4: af00mc  0,0
   >3ffcadb8: b9040054lgr 
%r5,%r4
3ffcadbc: c02000302aadlarl
%r2,405d0316
3ffcadc2: b9040041lgr 
%r4,%r1
3ffcadc6: c0e5ffdd30a5brasl   
%r14,3fb70f10
3ffcadcc: af00mc  0,0
  [ 1681.564592] Call Trace:
  [ 1681.564594]  [<3ffcadb8>] __list_add_valid+0x70/0xa8
  [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8)
  [ 1681.564599]  [<3faf2920>] zpci_create_device+0x60/0x1b0
  [ 1681.564601]  [<3faf704a>] zpci_event_availability+0x282/0x2f0
  [ 1681.564605]  [<40367848>] chsc_process_crw+0x2b8/0xa18
  [ 1681.564607]  [<4036f35c>] crw_collect_info+0x254/0x348
  [ 1681.564610]  [<3fb2a6ea>] kthread+0x14a/0x168
  [ 1681.564613]  [<403a55c0>] ret_from_fork+0x24/0x2c
  [ 1681.564614] Last Breaking-Event-Address:
  [ 1681.564618]  [<3fb70f62>] printk+0x52/0x58
  [ 1681.564620] ---[ end trace 7ea67c348aa67e14 ]---

  
  uname:
  Linux t83lp49.lnxne.boe 5.8.0-rc1+ #2 SMP Thu Jun 18 12:38:02 CEST 2020 s390x 
s390x s390x GNU/Linux

  How to reproduce:
  1. Unassign a NVMe drive in HMC from your LPAR
  2. Reassign it to your LPAR again
  3. dmesg

  
  == Solution

  The issue with VF attach/detach is with the fact that
  on IBM Z VFs can be enabled/disabled individually using

  echo 0 > /sys/bus/pci/slots//power

  If this was done with a VF linked to a parent PF the
  symlink in the parent (/sys/bus/pci/devices//virtfnX)
  would become stale while the VF is disabled and
  when turned back on the VF would not get linked to the PF
  again and so could not be used e.g. with QEMU which
  relies on the links.
  Similarly stale virtfn links could remain after
  removing VFs through.

  echo 0 > /sys/bus/pci/devices//sriov_numvfs

  Furthermore there was a missing pci_dev_put() when
  searching for the parent PF potentially resulting
  in a too high reference count of the paren

[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

[Dimitri John Ledkov]

I've already bootstrapped rustc using these changes. In both focal &
groovy. This is really good!

For me it was enough to have it just in -proposed. But yeah, we do need
this in -updates too.

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

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

Title:
  linux-libc-dev broken for crossbuilding, Multi-Arch:same violation

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-riscv source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Invalid

Bug description:
  SRU Justificatoin

  Impact: Building linux-libc-dev for riscv64 from the linux-riscv
  package means that it can have a different version from the package on
  other architectures. This makes it uninstallable for cross building.

  Fix: Move the riscv64 linux-libc-dev build back to the main kernel
  package so that the version will match.

  Test Case: See below.

  Regression Potential: This could cause trouble if the main kernel
  package version is behind the linux-riscv package version, and may
  require artificially inflating the version of the linux package.
  Currently this is not necessary, but it needs to be kept in mind when
  preparing packages for upload with the fixes applied.

  ---

  # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  linux-libc-dev is already the newest version (5.4.0-26.30).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 
5.4.0-27.31 is to be installed
   linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 
5.4.0-26.30 is to be installed
  E: Unable to correct problems, you have held broken packages.

  $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e 
groovy
   linux-libc-dev | 5.4.0-24.28| focal| riscv64
   linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-26.30| groovy   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-27.31| groovy   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-security   | riscv64
   linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64
   linux-libc-dev | 5.4.0-40.44| focal-security   | amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, 
i386, ppc64el, s390x
   linux-libc-dev | 5.4.0-40.44| groovy-proposed  | amd64, arm64, armhf, 
i386, ppc64el, s390x

  This is broken.

  linux-libc-dev must have identical content for common files, across
  all architectures, and must have identical version number.

  A few ways to fix this:

  * Either enforce that src:linux & src:linux-riscv are at the same
  version number. But then reasons for splitting riscv into a separate
  build dissappear

  * Make src:linux build _just_ the headers linux-libc-dev for risv64,
  and nothing else. And stop bulding linux-libc-dev form the src:linux-
  riscv package. Just like it does for i386.

  * Or create new src:linux-headers that only builds linux-libc-dev for
  all architectures, without building any kernels. This way for example,
  we could rev userspace headers to v5.8/v5.9 ahead of said kernel
  landing, to shake out build-failures / userspace issues, whilst the
  kernel itself is still baking in bootstrap/proposed PPA.

  This must be address in Focal and Groovy

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

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

[Kernel-packages] [Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Po-Hsu Lin]

A bisect for arch/powerpc/ shows this is the first bad commit on 4.15:

$ git bisect bad
7d10952e8a56f87a53fc57594078555a9dfd4a07 is the first bad commit
commit 7d10952e8a56f87a53fc57594078555a9dfd4a07
Author: Michael Ellerman 
Date:   Thu May 28 00:58:42 2020 +1000

powerpc/64s: Save FSCR to init_task.thread.fscr after feature init

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

commit 912c0a7f2b5daa3cbb2bc10f303981e493de73bd upstream.

At boot the FSCR is initialised via one of two paths. On most systems
it's set to a hard coded value in __init_FSCR().

On newer skiboot systems we use the device tree CPU features binding,
where firmware can tell Linux what bits to set in FSCR (and HFSCR).

In both cases the value that's configured at boot is not propagated
into the init_task.thread.fscr value prior to the initial fork of init
(pid 1), which means the value is not used by any processes other than
swapper (the idle task).

For the __init_FSCR() case this is OK, because the value in
init_task.thread.fscr is initialised to something sensible. However it
does mean that the value set in __init_FSCR() is not used other than
for swapper, which is odd and confusing.

The bigger problem is for the device tree CPU features case it
prevents firmware from setting (or clearing) FSCR bits for use by user
space. This means all existing kernels can not have features
enabled/disabled by firmware if those features require
setting/clearing FSCR bits.

We can handle both cases by saving the FSCR value into
init_task.thread.fscr after we have initialised it at boot. This fixes
the bug for device tree CPU features, and will allow us to simplify
the initialisation for the __init_FSCR() case in a future patch.

Fixes: 5a61ef74f269 ("powerpc/64s: Support new device tree binding for 
discovering CPU features")
Cc: sta...@vger.kernel.org # v4.12+
Signed-off-by: Michael Ellerman 
Link: https://lore.kernel.org/r/20200527145843.2761782-3-...@ellerman.id.au
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Kamal Mostafa 
Signed-off-by: Khalid Elmously 

:04 04 9c654d310ed9b7c4a1cf16620d120ec93624eda3 
05b34a61190e63ccde3b7d02e2183dc64b32c812 M  arch


$ git bisect log
git bisect start '--' 'arch/powerpc/'
\# bad: [f4daf25f7f8608d1c14c85ea0b73c9e1e1eb2dba] UBUNTU: Ubuntu-4.15.0-114.115
git bisect bad f4daf25f7f8608d1c14c85ea0b73c9e1e1eb2dba
\# good: [495149ddc61a5997857fda041ccd4c81cac46e00] UBUNTU: 
Ubuntu-4.15.0-112.113
git bisect good 495149ddc61a5997857fda041ccd4c81cac46e00
\# bad: [07ad1246146fa49430d2455bd45db1c8da4d521c] powerpc/perf/hv-24x7: Fix 
inconsistent output values incase multiple hv-24x7 events run
git bisect bad 07ad1246146fa49430d2455bd45db1c8da4d521c
\# good: [f30471f4138df69bd4585d91c1f31a282daa41e7] powerpc/64s: Don't let DT 
CPU features set FSCR_DSCR
git bisect good f30471f4138df69bd4585d91c1f31a282daa41e7
\# bad: [0e198dfae237e9a9654d87b7c6df12146feaec26] sched/core: Fix illegal RCU 
from offline CPUs
git bisect bad 0e198dfae237e9a9654d87b7c6df12146feaec26
\# bad: [7d10952e8a56f87a53fc57594078555a9dfd4a07] powerpc/64s: Save FSCR to 
init_task.thread.fscr after feature init
git bisect bad 7d10952e8a56f87a53fc57594078555a9dfd4a07
\# first bad commit: [7d10952e8a56f87a53fc57594078555a9dfd4a07] powerpc/64s: 
Save FSCR to init_task.thread.fscr after feature init

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

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Incomplete

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

   # selftests: powerpc/dscr: dscr_inherit_exec_test 
   # test: dscr_inherit_exec_test
   # tags: git_version:unknown
   # Parent DSCR 1 was not inherited over exec (kernel value)
   # Child didn't exit cleanly
   # failure: dscr_inherit_exec_test
   not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

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

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

[Kernel-packages] [Bug 1888339] Re: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Po-Hsu Lin]

A bisect for arch/powerpc/ shows this is the first bad commit:

$ git bisect bad
7d10952e8a56f87a53fc57594078555a9dfd4a07 is the first bad commit
commit 7d10952e8a56f87a53fc57594078555a9dfd4a07
Author: Michael Ellerman 
Date:   Thu May 28 00:58:42 2020 +1000

powerpc/64s: Save FSCR to init_task.thread.fscr after feature init

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

commit 912c0a7f2b5daa3cbb2bc10f303981e493de73bd upstream.

At boot the FSCR is initialised via one of two paths. On most systems
it's set to a hard coded value in __init_FSCR().

On newer skiboot systems we use the device tree CPU features binding,
where firmware can tell Linux what bits to set in FSCR (and HFSCR).

In both cases the value that's configured at boot is not propagated
into the init_task.thread.fscr value prior to the initial fork of init
(pid 1), which means the value is not used by any processes other than
swapper (the idle task).

For the __init_FSCR() case this is OK, because the value in
init_task.thread.fscr is initialised to something sensible. However it
does mean that the value set in __init_FSCR() is not used other than
for swapper, which is odd and confusing.

The bigger problem is for the device tree CPU features case it
prevents firmware from setting (or clearing) FSCR bits for use by user
space. This means all existing kernels can not have features
enabled/disabled by firmware if those features require
setting/clearing FSCR bits.

We can handle both cases by saving the FSCR value into
init_task.thread.fscr after we have initialised it at boot. This fixes
the bug for device tree CPU features, and will allow us to simplify
the initialisation for the __init_FSCR() case in a future patch.

Fixes: 5a61ef74f269 ("powerpc/64s: Support new device tree binding for 
discovering CPU features")
Cc: sta...@vger.kernel.org # v4.12+
Signed-off-by: Michael Ellerman 
Link: https://lore.kernel.org/r/20200527145843.2761782-3-...@ellerman.id.au
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Kamal Mostafa 
Signed-off-by: Khalid Elmously 

:04 04 9c654d310ed9b7c4a1cf16620d120ec93624eda3 
05b34a61190e63ccde3b7d02e2183dc64b32c812 M  arch


$ git bisect log
git bisect start '--' 'arch/powerpc/'
\# bad: [f4daf25f7f8608d1c14c85ea0b73c9e1e1eb2dba] UBUNTU: Ubuntu-4.15.0-114.115
git bisect bad f4daf25f7f8608d1c14c85ea0b73c9e1e1eb2dba
\# good: [495149ddc61a5997857fda041ccd4c81cac46e00] UBUNTU: 
Ubuntu-4.15.0-112.113
git bisect good 495149ddc61a5997857fda041ccd4c81cac46e00
\# bad: [07ad1246146fa49430d2455bd45db1c8da4d521c] powerpc/perf/hv-24x7: Fix 
inconsistent output values incase multiple hv-24x7 events run
git bisect bad 07ad1246146fa49430d2455bd45db1c8da4d521c
\# good: [f30471f4138df69bd4585d91c1f31a282daa41e7] powerpc/64s: Don't let DT 
CPU features set FSCR_DSCR
git bisect good f30471f4138df69bd4585d91c1f31a282daa41e7
\# bad: [0e198dfae237e9a9654d87b7c6df12146feaec26] sched/core: Fix illegal RCU 
from offline CPUs
git bisect bad 0e198dfae237e9a9654d87b7c6df12146feaec26
\# bad: [7d10952e8a56f87a53fc57594078555a9dfd4a07] powerpc/64s: Save FSCR to 
init_task.thread.fscr after feature init
git bisect bad 7d10952e8a56f87a53fc57594078555a9dfd4a07
\# first bad commit: [7d10952e8a56f87a53fc57594078555a9dfd4a07] powerpc/64s: 
Save FSCR to init_task.thread.fscr after feature init

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

Title:
  [Potential Regression] ptrace-tar from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Incomplete

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)

  # selftests: powerpc/ptrace: ptrace-tar
  # test: ptrace_tar
  # tags: git_version:f21e446-dirty
  # [User Write (Running)] TAR: 10 PPR: 4 DSCR: 100
  # [User Read (Running)]  TAR: 20 PPR: 8 DSCR: 0
  # [Ptrace Read (Running)]TAR: 10 PPR: 4 DSCR: 100
  # [Ptrace Write (Running)]   TAR: 20 PPR: 8 DSCR: 200
  # failure: ptrace_tar
  not ok 4 selftests: powerpc/ptrace: ptrace-tar # exit=1

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

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

[Kernel-packages] [Bug 1888334] Re: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on B/E/F

[Po-Hsu Lin]

A bisect for arch/powerpc/ shows this is the first bad commit:

$ git bisect bad
7d10952e8a56f87a53fc57594078555a9dfd4a07 is the first bad commit
commit 7d10952e8a56f87a53fc57594078555a9dfd4a07
Author: Michael Ellerman 
Date:   Thu May 28 00:58:42 2020 +1000

powerpc/64s: Save FSCR to init_task.thread.fscr after feature init

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

commit 912c0a7f2b5daa3cbb2bc10f303981e493de73bd upstream.

At boot the FSCR is initialised via one of two paths. On most systems
it's set to a hard coded value in __init_FSCR().

On newer skiboot systems we use the device tree CPU features binding,
where firmware can tell Linux what bits to set in FSCR (and HFSCR).

In both cases the value that's configured at boot is not propagated
into the init_task.thread.fscr value prior to the initial fork of init
(pid 1), which means the value is not used by any processes other than
swapper (the idle task).

For the __init_FSCR() case this is OK, because the value in
init_task.thread.fscr is initialised to something sensible. However it
does mean that the value set in __init_FSCR() is not used other than
for swapper, which is odd and confusing.

The bigger problem is for the device tree CPU features case it
prevents firmware from setting (or clearing) FSCR bits for use by user
space. This means all existing kernels can not have features
enabled/disabled by firmware if those features require
setting/clearing FSCR bits.

We can handle both cases by saving the FSCR value into
init_task.thread.fscr after we have initialised it at boot. This fixes
the bug for device tree CPU features, and will allow us to simplify
the initialisation for the __init_FSCR() case in a future patch.

Fixes: 5a61ef74f269 ("powerpc/64s: Support new device tree binding for 
discovering CPU features")
Cc: sta...@vger.kernel.org # v4.12+
Signed-off-by: Michael Ellerman 
Link: https://lore.kernel.org/r/20200527145843.2761782-3-...@ellerman.id.au
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Kamal Mostafa 
Signed-off-by: Khalid Elmously 

:04 04 9c654d310ed9b7c4a1cf16620d120ec93624eda3 
05b34a61190e63ccde3b7d02e2183dc64b32c812 M  arch


$ git bisect log
git bisect start '--' 'arch/powerpc/'
\# bad: [f4daf25f7f8608d1c14c85ea0b73c9e1e1eb2dba] UBUNTU: Ubuntu-4.15.0-114.115
git bisect bad f4daf25f7f8608d1c14c85ea0b73c9e1e1eb2dba
\# good: [495149ddc61a5997857fda041ccd4c81cac46e00] UBUNTU: 
Ubuntu-4.15.0-112.113
git bisect good 495149ddc61a5997857fda041ccd4c81cac46e00
\# bad: [07ad1246146fa49430d2455bd45db1c8da4d521c] powerpc/perf/hv-24x7: Fix 
inconsistent output values incase multiple hv-24x7 events run
git bisect bad 07ad1246146fa49430d2455bd45db1c8da4d521c
\# good: [f30471f4138df69bd4585d91c1f31a282daa41e7] powerpc/64s: Don't let DT 
CPU features set FSCR_DSCR
git bisect good f30471f4138df69bd4585d91c1f31a282daa41e7
\# bad: [0e198dfae237e9a9654d87b7c6df12146feaec26] sched/core: Fix illegal RCU 
from offline CPUs
git bisect bad 0e198dfae237e9a9654d87b7c6df12146feaec26
\# bad: [7d10952e8a56f87a53fc57594078555a9dfd4a07] powerpc/64s: Save FSCR to 
init_task.thread.fscr after feature init
git bisect bad 7d10952e8a56f87a53fc57594078555a9dfd4a07
\# first bad commit: [7d10952e8a56f87a53fc57594078555a9dfd4a07] powerpc/64s: 
Save FSCR to init_task.thread.fscr after feature init

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

Title:
  [Potential Regression] tm-resched-dscr from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Incomplete

Bug description:
  Issue found on 5.3.0-64.58 with P8 node modoc (skipped with P9 node)

  # selftests: powerpc/tm: tm-resched-dscr
  # test: tm_resched_dscr
  # tags: git_version:unknown
  # Binding to cpu 8
  # main test running as pid 142637
  # Check DSCR TM context switch: FAIL
  # failure: tm_resched_dscr
  not ok 1 selftests: powerpc/tm: tm-resched-dscr # exit=1

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

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

[Kernel-packages] [Bug 1862878] Re: add_key01 from ubuntu_ltp_syscalls failed on Bionic s390x

[Po-Hsu Lin]

Didn't see this in this cycle 4.15.0-114.115 on s2lp3.

Let's keep an eye on this for another cycle.


** Changed in: ubuntu-kernel-tests
   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/1862878

Title:
  add_key01 from ubuntu_ltp_syscalls failed on Bionic s390x

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue found on s2lp3 s390x Ubuntu LPAR
  Test failed with:
add_key01.c:77: FAIL: add_key call failed unexpectedly: ENOMEM (12)

  
  <<>>
  tag=add_key01 stime=1581482840
  cmdline="add_key01"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_buffers.c:55: INFO: Test is using guarded buffers
  tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
  add_key01.c:63: INFO: The key type is keyrings and plen is 0
  add_key01.c:79: PASS: add_key call succeeded as expected
  add_key01.c:63: INFO: the key type is keyrings and plen is 1
  add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)
  add_key01.c:63: INFO: The key type is user and plen is 32767
  add_key01.c:79: PASS: add_key call succeeded as expected
  add_key01.c:63: INFO: The key type is user and plen is 32768
  add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)
  add_key01.c:63: INFO: The key type is logon and plen is 32767
  add_key01.c:79: PASS: add_key call succeeded as expected
  add_key01.c:63: INFO: The key type is logon and plen is 32768
  add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)
  add_key01.c:63: INFO: The key type is big_key and plen is 1048575
  add_key01.c:77: FAIL: add_key call failed unexpectedly: ENOMEM (12)
  add_key01.c:63: INFO: The key type is big_key and plen is 1048576
  add_key01.c:83: PASS: add_key call failed as expected: EINVAL (22)

  Summary:
  passed   7
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  dmesg output:
  [  847.773454] BUG: non-zero pgtables_bytes on freeing mm: 16384
  [  847.773603] BUG: non-zero pgtables_bytes on freeing mm: 16384
  [  848.733118] LTP: starting add_key01
  [  848.736003] WARNING: CPU: 2 PID: 4833 at 
/build/linux-Vp68rX/linux-4.15.0/mm/page_alloc.c:4230 
__alloc_pages_nodemask+0x28e/0xfe8
  [  848.736004] Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 
ebtable_filter ebtables ip6table_filter ip6_tables aufs xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp 
bridge iptable_filter overlay openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack 
8021q garp stp mrp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
dm_service_time zcommon(PO) znvpair(PO) spl(O) dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua qeth_l2 genwqe_card crc_itu_t chsc_sch eadm_sch qeth 
ctcm ccwgroup fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel 
ib_iser rdma_cm nfsd iw_cm ib_cm auth_rpcgss iscsi_tcp libiscsi_tcp libiscsi 
nfs_acl lockd scsi_transport_iscsi grace sunrpc ip_tables x_tables
  [  848.736051]  btrfs zstd_compress zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear mlx4_en mlx4_ib ib_core ptp pps_core crc32_vx_s390 
ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 
sha_common mlx4_core devlink zfcp qdio scsi_transport_fc dasd_eckd_mod dasd_mod
  [  848.736077] CPU: 2 PID: 4833 Comm: add_key01 Tainted: P   O 
4.15.0-87-generic #87-Ubuntu
  [  848.736077] Hardware name: IBM 2964 N63 400 (LPAR)
  [  848.736079] Krnl PSW : 4532b723 0968d01f 
(__alloc_pages_nodemask+0x28e/0xfe8)
  [  848.736082]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [  848.736083] Krnl GPRS:  0001 014040c0 
0009
  [  848.736084]  000f 
0009
  [  848.736085]0050663c 001f 014000c0 
000f
  [  848.736086] 00943a68 0003b436fc90 
0003b436fb00
  [  848.736094] Krnl Code: 002e16b2: a7210200  tmll%r2,512
002e16b6: a774ff4a  brc 
7,002e154a
   #002e16ba: a7f40001  brc 
15,002e16bc
   >002e16be: a7f4ff46  brc 
15,002e154a
002e16c2: a708  lhi %r0,0
002e16c6: a7f4ff08  brc 
15,002e14d6
002e16ca: e31003380004  lg  %r1,824

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

[Jeff Lane]

Marked Groovy task as invalid. Patches are all in 5.5, and thus already
present in Groovy.

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

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

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

Title:
  Devlink -  add RoCE disable kernel support

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Invalid

Bug description:
  [Impact]

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

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

  [Test Case]

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

  User command examples:

  - Disable RoCE::

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

  - Read RoCE enablement state::

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

  [Regression Potential]

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

  Test 5.4 Ubuntu kernels have also been tested by Mellanox and have
  been verified working.

  [Other Info]

  Feature patchset:

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

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

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

  userspace:

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

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

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

[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: change DFLT_CCERROR counter name

[Frank Heimes]

On top I've created builds of the patched kernel packages (for focal and 
bionic), available for further testing:
https://people.canonical.com/~fheimes/lp1891454_debs/

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
  avoid confusion.

  * This counter counts completed DEFLATE instructions with exit code 0,
  1 or 2.

  * And since exit code 0 means success and exit code 1 or 2 indicate
  errors the name can be ambiguous.

  [Fix]

  * Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.

  * Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
  -cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch

  * Backport Bionic:
  https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
  new-extended-counters-for-IBM-z15.patch

  [Test Case]

  * Enable hardware counters in the activation profile of a z15 LPAR.

  * Just check the countername in sysfs with: ls
  /sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}

  [Regression Potential]

  * The regression potential can be considered as low, since:

  * Counters like these are usually not activated by default and need to
  be explicitly enabled.

  * No code functionality is changed with that patch, only a renaming is
  done at 3 places in one code file
  arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
  events/arch/s390/cf_z15/extended.json.

  * The fix got already upstream accepted in 5.8-rc7, hence it got
  upstream reviewed,

  * and the modifications are limited to s390x, are only relevant for
  the z15 / LinuxONE III hw generation that are relatively new.

  * Issue with the renaming I can think of are that people don't know
  about the new name and may look for the old one and don't find it
  anymore,

  * and with that also if the old counter name is used in scripts or
  applications, these may fails due to an unknown counter name.

  [Other Info]

  * The backports are based on commit
  3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
  DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.

  * Hence this SRU is not requested for groovy, since it's already in groovys 
kernel 5.8 in proposed, but only requested for focal and bionic.
  __

  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
     IBM z15.  This counter counts completed DEFLATE instructions
     with exit code 0, 1 or 2. Since exit code 0 means success
     and exit code 1 or 2 indicate errors, change the counter
     name to avoid confusion.  This counter is incremented each
     time the DEFLATE instruction completed regardless if an
     error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
     currently succeeds. After this patch has been applied the
     command does not work anymore. The file does not exist
     anymore. Use command
     # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
     instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8

  Will be integrated into 20.10 by kernel 5.8 integration.

  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided

  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

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

[Kernel-packages] [Bug 1876770] Re: speed for CX4 VF showing as unknown in ethtool output

[William Breathitt Gray]

Patches have been posted to the Kernel Team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-August/112754.html

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

Title:
  speed for CX4 VF showing as unknown in ethtool output

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Triaged
Status in linux-azure source package in Focal:
  Triaged
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  While deploying a VM in D series (D8S_V3 and D16S_V3) and enabling
  accelerated networking, MLX5 drivers are getting installed.  However,
  accelerated networking is not showing as enabled in guest OS. The same
  VM is showing enabled from portal.

  
  The problem is in the Mellanox driver for the CX-4 VF.  Mellanox has already 
fixed the problem in three separate patches, which are all in mainline.

  We would like to request the following three commits in all supported
  releases:

  2f5438ca0ee0 ("net/mlx5: Tidy up and fix reverse christmas ordring")
  c268ca6087f5 ("net/mlx5: Expose port speed when possible")
  dc392fc56f39 ("net/mlx5: Expose link speed directly")

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

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

[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: change DFLT_CCERROR counter name

[Frank Heimes]

Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2020-August/thread.html#112945
Changing status for Focal and Bionic to 'In Progress'.

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

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

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

** Description changed:

+ SRU Justification:
+ ==
+ 
+ [Impact]
+ 
+ * Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
+ avoid confusion.
+ 
+ * This counter counts completed DEFLATE instructions with exit code 0, 1
+ or 2.
+ 
+ * And since exit code 0 means success and exit code 1 or 2 indicate
+ errors the name can be ambiguous.
+ 
+ [Fix]
+ 
+ * Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
+ 
+ * Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
+ -cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
+ 
+ * Backport Bionic:
+ https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-new-
+ extended-counters-for-IBM-z15.patch
+ 
+ [Test Case]
+ 
+ * Enable hardware counters in the activation profile of a z15 LPAR.
+ 
+ * Just check the countername in sysfs with: ls
+ /sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
+ 
+ [Regression Potential]
+ 
+ * The regression potential can be considered as low, since:
+ 
+ * Counters like these are usually not activated by default and need to
+ be explicitly enabled.
+ 
+ * No code functionality is changed with that patch, only a renaming is
+ done at 3 places in one code file arch/s390/kernel/perf_cpum_cf_events.c
+ as well as in /tools/perf/pmu-events/arch/s390/cf_z15/extended.json.
+ 
+ * The fix got already upstream accepted in 5.8-rc7, hence it got
+ upstream reviewed,
+ 
+ * and the modifications are limited to s390x, are only relevant for the
+ z15 / LinuxONE III hw generation that are relatively new.
+ 
+ * Issue with the renaming I can think of are that people don't know
+ about the new name and may look for the old one and don't find it
+ anymore,
+ 
+ * and with that also if the old counter name is used in scripts or
+ applications, these may fails due to an unknown counter name.
+ 
+ [Other Info]
+ 
+ * The backports are based on commit
+ 3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
+ DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
+ 
+ * Hence this SRU is not requested for groovy, since it's already in groovys 
kernel 5.8 in proposed, but only requested for focal and bionic.
+ __
+ 
  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
-IBM z15.  This counter counts completed DEFLATE instructions
-with exit code 0, 1 or 2. Since exit code 0 means success
-and exit code 1 or 2 indicate errors, change the counter
-name to avoid confusion.  This counter is incremented each
-time the DEFLATE instruction completed regardless if an
-error was detected or not.
+    IBM z15.  This counter counts completed DEFLATE instructions
+    with exit code 0, 1 or 2. Since exit code 0 means success
+    and exit code 1 or 2 indicate errors, change the counter
+    name to avoid confusion.  This counter is incremented each
+    time the DEFLATE instruction completed regardless if an
+    error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
-currently succeeds. After this patch has been applied the
-command does not work anymore. The file does not exist
-anymore. Use command 
-# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
-instead.
+    currently succeeds. After this patch has been applied the
+    command does not work anymore. The file does not exist
+    anymore. Use command
+    # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
+    instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8
  
  Will be integrated into 20.10 by kernel 5.8 integration.
  
  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided
  
  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status i

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

[Sean Feole]

** No longer affects: linux-aws (Ubuntu Eoan)

** No longer affects: linux (Ubuntu Eoan)

** No longer affects: linux-aws (Ubuntu Disco)

** No longer affects: linux (Ubuntu Disco)

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "crypto_user02 crypto_user02" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1889735] Re: tap: use after free

[Stefan Bader]

This is an upstream fix for a change that was released in v4.8. So we
can treat that as part of stable.

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

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

Title:
  tap: use after free

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

Bug description:
  [Impact]

  If the socket buffer array of a tap queue is full, a received package
  needs to be dropped. Currently, the check for the array being full is
  performed lockless, which might lead to use-after-free errors if the
  socket buffer array has been resized.

  [Test Case]

  TBD.

  [Regression Potential]

  The check for the array being full is simply dropped. In case the
  array is full, subsequent frame handling will fail and the frame is
  eventually dropped. A regression would manifest itself if the frame is
  not dropped for whatever reason and inserted into the full (ring)
  buffer, overwriting the oldest frame in the buffer. So we'd end up
  with frame/packet loss.

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

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

[Kernel-packages] [Bug 1891222] Re: Only notify Hyper-V for die events that are oops

[William Breathitt Gray]

A patch has been submitted to the Kernel Team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-August/112784.html

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

Title:
  Only notify Hyper-V for die events that are oops

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-4.15 package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Currently, Hyper-V may be notified of a panic for any die event.

  However, this results in false panic notifications for various user space 
traps
  that are die events. 

  The following commit fixes this by ignoring die events that is not an
  oops:

  608a973bd52e ("Drivers: hv: vmbus: Only notify Hyper-V for die events
  that are oops")

  We would like to request this commit in all releases supported on
  Azure and Hyper-V.

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

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

[Kernel-packages] [Bug 1891222] Re: Only notify Hyper-V for die events that are oops

[William Breathitt Gray]

A patch has been submitted to the Kernel Team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-August/112787.html

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

Title:
  Only notify Hyper-V for die events that are oops

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-4.15 package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Currently, Hyper-V may be notified of a panic for any die event.

  However, this results in false panic notifications for various user space 
traps
  that are die events. 

  The following commit fixes this by ignoring die events that is not an
  oops:

  608a973bd52e ("Drivers: hv: vmbus: Only notify Hyper-V for die events
  that are oops")

  We would like to request this commit in all releases supported on
  Azure and Hyper-V.

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

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

[Kernel-packages] [Bug 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04

[Tim Epkes]

Christian I work with Neil, the setup is in a qemu VM.  so the host OS
is Ubuntu 18.04 in both cases, its just within the Guest VM that the os
changes from 18.04 to 20.04 with the exact same parameters.  it is
automated, so the setup is exact comparison with the only difference
being the OS version.

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

Title:
  Pci passthrough interface not showing up in Ubuntu 20.04 but does show
  in 18.04

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  
  After setting up pci pass through for a virtual function it did not show up 
as an interface in Ubuntu 20.04, it did however show up as a PCI device. 
  After reverting back to 18.04 with exactly the same configuration the 
interface showed up as expected.
  Bellow is the configuration and output for both 18.04 and 20.04.

  virt-install 
  --import 
  --connect qemu:///system --name emsk8sm1 --ram 8192 
  --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio   
  --disk  cidata.img,device=cdrom,format=img  
  --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04
  --network 
bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea
  --hostdev 3b:02.5
  --console pty,target_type=serial
  --graphics type=vnc,listen=0.0.0.0 
  --noautoconsole
  --autostart -v


  Configuration of 18.04 where the passthrough works

  Version
  Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  virsh dumpxml emsk8sm1
  






  


  lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
  00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)  <--- Pass through interface

  
  ip link show [interface shows inside of vm ens6]
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
  3: ens6:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff


  Configuration of 20.04 where the VF shows as a PCI device but does not show 
as an interface

  Version
  Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  virsh dumpxml emsk8sm1
  






  


  lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
  00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)   <--- Pass through interface

  
  ip link show [ens 6 does not show as an interface} 
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
  3: tunl0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
  link/ipip 0.0.0.0 brd 0.0.0.0
  4: sit0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
  link/sit 0.0.0.0 brd 0.0.0.0

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

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

[Kernel-packages] [Bug 1892849] Re: [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes 
(fheimes)

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

Title:
  [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Problem description:

  When a NVMe drive is assigned/hotplugged to a Linux LPAR then
  a bug is hit in lib/list_debug.c. And the device is not accessible, there is 
no /dev/ file
  and lspci does not report it also.

  
  [ 1681.564462] list_add double add: new=eed0f808, 
prev=eed0f808, next=4070a300.
  [ 1681.564489] [ cut here ]
  [ 1681.564490] kernel BUG at lib/list_debug.c:31!
  [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP
  [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter 
ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat 
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat 
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 
des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch 
vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 
sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio 
ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt
  [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2
  [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR)
  [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 
(__list_add_valid+0x70/0xa8)
  [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [ 1681.564545] Krnl GPRS: 0040 0027 0058 
0007
  [ 1681.564546]3ffcadb4   
03e0051a7ce0
  [ 1681.564547]4070a300 eed0f808 eed0f808 
4070a300
  [ 1681.564548]f56a2000 40c2c788 3ffcadb4 
03e0051a7bc8
  [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl
%r2,405d03ba
3ffcadae: c0e5ffdd30b1brasl   
%r14,3fb70f10
   #3ffcadb4: af00mc  0,0
   >3ffcadb8: b9040054lgr 
%r5,%r4
3ffcadbc: c02000302aadlarl
%r2,405d0316
3ffcadc2: b9040041lgr 
%r4,%r1
3ffcadc6: c0e5ffdd30a5brasl   
%r14,3fb70f10
3ffcadcc: af00mc  0,0
  [ 1681.564592] Call Trace:
  [ 1681.564594]  [<3ffcadb8>] __list_add_valid+0x70/0xa8
  [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8)
  [ 1681.564599]  [<3faf2920>] zpci_create_device+0x60/0x1b0
  [ 1681.564601]  [<3faf704a>] zpci_event_availability+0x282/0x2f0
  [ 1681.564605]  [<40367848>] chsc_process_crw+0x2b8/0xa18
  [ 1681.564607]  [<4036f35c>] crw_collect_info+0x254/0x348
  [ 1681.564610]  [<3fb2a6ea>] kthread+0x14a/0x168
  [ 1681.564613]  [<403a55c0>] ret_from_fork+0x24/0x2c
  [ 1681.564614] Last Breaking-Event-Address:
  [ 1681.564618]  [<3fb70f62>] printk+0x52/0x58
  [ 1681.564620] ---[ end trace 7ea67c348aa67e14 ]---

  
  uname:
  Linux t83lp49.lnxne.boe 5.8.0-rc1+ #2 SMP Thu Jun 18 12:38:02 CEST 2020 s390x 
s390x s390x GNU/Linux

  How to reproduce:
  1. Unassign a NVMe drive in HMC from your LPAR
  2. Reassign it to your LPAR again
  3. dmesg

  
  == Solution

  The issue with VF attach/detach is with the fact that
  on IBM Z VFs can be enabled/disabled individually using

  echo 0 > /sys/bus/pci/slots//power

  If this was done with a VF linked to a parent PF the
  symlink in the parent (/sys/bus/pci/devices//virtfnX)
  would become stale while the VF is disabled and
  when turned back on the VF would not get linked to the PF
  again and so could not be used e.g. with QEMU which
  relies on the links.
  Similarly stale virtfn links could remain after
  removing VFs through.

  echo 0 > /sys/bus/pci/devices//sriov_numvfs

  Furthermore there was a missing pci_dev_put() when
  searching for the parent PF potentially resulting
  in a too high reference count of the parent PFs.

  Th

[Kernel-packages] [Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes

[James Falcon]

https://github.com/canonical/cloud-init/pull/539

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

Title:
  [linux-azure] Delay during boot of some instance sizes

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We are seeing a long delay, about 100s, when booting new E32s_v3 VMs.

  We don’t see this delay with smaller sized Ubuntu VMs(D2s and NC6
  sizes).

  I attached a screen shot of the boot delay.  You can see between
  7.022911 and 101.325958 seconds there is no activity.

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

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

[Kernel-packages] [Bug 1891222] Re: Only notify Hyper-V for die events that are oops

[William Breathitt Gray]

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

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

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

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

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

** No longer affects: linux-azure-5.4 (Ubuntu)

** No longer affects: linux-azure-5.4 (Ubuntu Focal)

** No longer affects: linux-azure-5.4 (Ubuntu Bionic)

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

Title:
  Only notify Hyper-V for die events that are oops

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-4.15 package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Currently, Hyper-V may be notified of a panic for any die event.

  However, this results in false panic notifications for various user space 
traps
  that are die events. 

  The following commit fixes this by ignoring die events that is not an
  oops:

  608a973bd52e ("Drivers: hv: vmbus: Only notify Hyper-V for die events
  that are oops")

  We would like to request this commit in all releases supported on
  Azure and Hyper-V.

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

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

[Kernel-packages] [Bug 1891222] Re: Only notify Hyper-V for die events that are oops

[Marcelo Cerri]

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

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

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

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

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

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

** Changed in: linux-azure-4.15 (Ubuntu Focal)
   Status: New => Invalid

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

Title:
  Only notify Hyper-V for die events that are oops

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-4.15 package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Currently, Hyper-V may be notified of a panic for any die event.

  However, this results in false panic notifications for various user space 
traps
  that are die events. 

  The following commit fixes this by ignoring die events that is not an
  oops:

  608a973bd52e ("Drivers: hv: vmbus: Only notify Hyper-V for die events
  that are oops")

  We would like to request this commit in all releases supported on
  Azure and Hyper-V.

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

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

[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend

[Stefan Bader]

The asking for Xenial happened because the kernel fix came back via
upstream stable and had the reference to this bug intact. Xenial was
already released but included previous changes in the changelog to care
for the case of that release not being done.

** Tags removed: verification-needed-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/1867983

Title:
  Computer is frozen after suspend

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems with ATA drives freeze during suspend

  [Fix]
  Avoid circular sync dependency by using async cookie.

  [Test]
  User reports positive feedback.

  [Regression Potential]
  Low. This patch makes synchronize more targeted, prevents many potential
  freeze.

  === Original Bug Report ===
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs

[Christopher Townsend]

Both the 18.04 & 16.04 Ubuntu Minimal cloud images use the kvm kernel by
default, so we need this fix applied to those kernels as well.  Are
there plans for that so that we can use those Minimal images in LXD?

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

Title:
  Make linux-kvm bootable in LXD VMs

Status in cloud-images:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released

Bug description:
  The `disk-kvm.img` images which are to be preferred when run under
  virtualization, currently completely fail to boot under UEFI.

  A workaround was put in place such that LXD instead will pull generic-
  based images until this is resolved, this however does come with a
  much longer boot time (as the kernel panics, reboots and then boots)
  and also reduced functionality from cloud-init, so we'd still like
  this fixed in the near future.

  To get things behaving, it looks like we need the following config
  options to be enable in linux-kvm:

   - CONFIG_EFI_STUB
   - CONFIG_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS_COMMON

  == Rationale ==
  We'd like to be able to use the linux-kvm based images for LXD, those will 
directly boot without needing the panic+reboot behavior of generic images and 
will be much lighter in general.

  We also need the LXD agent to work, which requires functional virtio
  vsock.

  == Test case ==
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz 
focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809
   - lxc launch bug1873809 v1
   - lxc console v1
   - 
   - 
   - lxc exec v1 bash

  To validate a new kernel, you'll need to manually repack the .img file
  and install the new kernel in there.

  == Regression potential ==
  I don't know who else is using those kvm images right now, but those changes 
will cause a change to the kernel binary such that it contains the EFI stub 
bits + a signature. This could cause some (horribly broken) systems to no 
longer be able to boot that kernel. Though considering that such a setup is 
common to our other kernels, this seems unlikely.

  Also, this will be introducing virtio vsock support which again, could
  maybe confused some horribly broken systems?

  
  In either case, the kernel conveniently is the only package which ships 
multiple versions concurently, so rebooting on the previous kernel is always an 
option, mitigating some of the risks.

  
  -- Details from original report --
  User report on the LXD side: https://github.com/lxc/lxd/issues/7224

  I've reproduced this issue with:
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda 
focal-server-cloudimg-amd64-disk-kvm.img -m 1G

  On the graphical console, you'll see EDK2 load (TianoCore) followed by basic 
boot messages and then a message from grub (error: can't find command 
`hwmatch`).
  Those also appear on successful boots of other images so I don't think 
there's anything concerning that. However it'll hang indefinitely and eat up 
all your CPU.

  Switching to the text console view (serial0), you'll see the same
  issue as that LXD report:

  BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found
  BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  error: can't find command `hwmatch'.
  e X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 
 
  ExceptionData - 
  RIP  - 3FF2DA12, CS  - 0038, RFLAGS - 00200202
  RAX  - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF
  RBX  - 0398, RSP - 3FF1C638, RBP - 3FF34360
  RSI  - 3FF343B8, RDI - 1000
  R8   - 3E80F108, R9  - 3E815B98, R10 - 0065
  R11  - 2501, R12 - 0004, R13 - 3E80F100
  R14  - , R15 - 
  DS   - 0030, ES  - 0030, FS  - 0030
  GS   - 0030, SS  - 0030
  CR0  - 80010033, CR2 - , CR3 - 3FC01000
  CR4  - 0668, CR8 - 
  DR0  - , DR1 - , DR2 - 
  DR3  - , DR6 - 0FF0, DR7 - 0400
  GDTR - 3FBEEA98 0047, LDTR 

[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend

[Stefan Bader]

@Glandos, the fix is now in a proposed kernel for Focal and should be
verified.

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

Title:
  Computer is frozen after suspend

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems with ATA drives freeze during suspend

  [Fix]
  Avoid circular sync dependency by using async cookie.

  [Test]
  User reports positive feedback.

  [Regression Potential]
  Low. This patch makes synchronize more targeted, prevents many potential
  freeze.

  === Original Bug Report ===
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1892849] Re: [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support

[Andrew Cloke]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   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/1892849

Title:
  [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support

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

Bug description:
  Problem description:

  When a NVMe drive is assigned/hotplugged to a Linux LPAR then
  a bug is hit in lib/list_debug.c. And the device is not accessible, there is 
no /dev/ file
  and lspci does not report it also.

  
  [ 1681.564462] list_add double add: new=eed0f808, 
prev=eed0f808, next=4070a300.
  [ 1681.564489] [ cut here ]
  [ 1681.564490] kernel BUG at lib/list_debug.c:31!
  [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP
  [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter 
ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat 
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat 
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 
des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch 
vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 
sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio 
ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt
  [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2
  [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR)
  [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 
(__list_add_valid+0x70/0xa8)
  [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
RI:0 EA:3
  [ 1681.564545] Krnl GPRS: 0040 0027 0058 
0007
  [ 1681.564546]3ffcadb4   
03e0051a7ce0
  [ 1681.564547]4070a300 eed0f808 eed0f808 
4070a300
  [ 1681.564548]f56a2000 40c2c788 3ffcadb4 
03e0051a7bc8
  [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl
%r2,405d03ba
3ffcadae: c0e5ffdd30b1brasl   
%r14,3fb70f10
   #3ffcadb4: af00mc  0,0
   >3ffcadb8: b9040054lgr 
%r5,%r4
3ffcadbc: c02000302aadlarl
%r2,405d0316
3ffcadc2: b9040041lgr 
%r4,%r1
3ffcadc6: c0e5ffdd30a5brasl   
%r14,3fb70f10
3ffcadcc: af00mc  0,0
  [ 1681.564592] Call Trace:
  [ 1681.564594]  [<3ffcadb8>] __list_add_valid+0x70/0xa8
  [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8)
  [ 1681.564599]  [<3faf2920>] zpci_create_device+0x60/0x1b0
  [ 1681.564601]  [<3faf704a>] zpci_event_availability+0x282/0x2f0
  [ 1681.564605]  [<40367848>] chsc_process_crw+0x2b8/0xa18
  [ 1681.564607]  [<4036f35c>] crw_collect_info+0x254/0x348
  [ 1681.564610]  [<3fb2a6ea>] kthread+0x14a/0x168
  [ 1681.564613]  [<403a55c0>] ret_from_fork+0x24/0x2c
  [ 1681.564614] Last Breaking-Event-Address:
  [ 1681.564618]  [<3fb70f62>] printk+0x52/0x58
  [ 1681.564620] ---[ end trace 7ea67c348aa67e14 ]---

  
  uname:
  Linux t83lp49.lnxne.boe 5.8.0-rc1+ #2 SMP Thu Jun 18 12:38:02 CEST 2020 s390x 
s390x s390x GNU/Linux

  How to reproduce:
  1. Unassign a NVMe drive in HMC from your LPAR
  2. Reassign it to your LPAR again
  3. dmesg

  
  == Solution

  The issue with VF attach/detach is with the fact that
  on IBM Z VFs can be enabled/disabled individually using

  echo 0 > /sys/bus/pci/slots//power

  If this was done with a VF linked to a parent PF the
  symlink in the parent (/sys/bus/pci/devices//virtfnX)
  would become stale while the VF is disabled and
  when turned back on the VF would not get linked to the PF
  again and so could not be used e.g. with QEMU which
  relies on the links.
  Similarly stale virtfn links could remain after
  removing VFs through.

  echo 0 > /sys/bus/pci/devices//sriov_numvfs

  Furthermore there was a missing pci_dev_put() when
  searching for the parent PF potentially resulting
  in a too high reference count of the parent PFs.

  This has been fixed upstream and in 5.8 stable
  with the following 3 upstream commits:

  3cddb79afc60bcdb5fd9dd7a1c64a8d03bdd460f s390/pci: fix z

[Kernel-packages] [Bug 1786013] Re: Packaging resync

[Stefan Bader]

** Changed in: linux (Ubuntu Precise)
 Assignee: Mohd Humaizi bin Mohd Yunos (mhmy2020) => (unassigned)

** Tags removed: verification-done-cosmic verification-needed-disco 
verification-needed-eoan verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Committed
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

[Sujit Kumar]

How do I implement this fix for my system?

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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