[Kernel-packages] [Bug 1821390] Re: apic-split will fail in kvm_units_tests

[Po-Hsu Lin]

Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64

** Tags added: sr

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

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

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

** Tags removed: sr
** Tags added: sru-20200316

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

Title:
  apic-split will fail in kvm_units_tests

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 source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

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

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

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

[Po-Hsu Lin]

Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64

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

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Confirmed

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; 

[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed

[Po-Hsu Lin]

Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64

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

Title:
  apic test in kvm-unit-test failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Robbie]

While not an actual driver...I found this utility on reddit...It's a
python script that checks for the mode, and if you're in the num pad
mode, it evaluates position of tap and sends numpad presses.  Works for
me!

https://gitlab.com/Thraen/gx735_touchpad_numpad/

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1868544] Re: Missing wireless network interface after kernel 5.3.0-43 installed

[Francis Ginther]

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

** This bug has been marked a duplicate of bug 1868442
   Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan

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

Title:
  Missing wireless network interface after kernel 5.3.0-43 installed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I apologize if this is a repeat of the bug I filed a couple of days
  ago, but I don't see on launchpad that it shows I filed a bug, so I am
  filling another.  Also didn't know what to file the bug under so I
  chose network-manager.  It appears to be a bug with kernel 5.3.0-43.

  I updated to latest kernel: initrd.img-5.3.0-43-generic and find that my 
network is in airplane mode. ifconfig shows there is no wireless interface 
setup. When I go back to kernel 5.3.0-42 everything is working correctly. I am 
using an HP laptop.
  I can see the wireless network controller with lshw:

  lshw -C network
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: eno1
 version: 15
 serial: b4:b6:86:e7:67:29
 size: 100Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.108 latency=0 
link=yes multicast=yes port=MII speed=100Mbit/s
 resources: irq:38 ioport:e000(size=256) memory:fe904000-fe904fff 
memory:fe90-fe903fff
*-network
 description: Network controller
 product: Dual Band Wireless-AC 3168NGW [Stone Peak]
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 version: 10
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=iwlwifi latency=0
 resources: irq:43 memory:fe80-fe801fff

  lspci |grep Network
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW 
[Stone Peak] (rev 10)

  iwconfig
  lo no wireless extensions.

  eno1 no wireless extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
  Uname: Linux 5.3.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  Date: Mon Mar 23 05:37:31 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-30 (479 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-11-29T22:07:37.505878
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   eno1ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
b6cda306-c004-3fd6-89b9-1be0460aa25d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rustin 1685 F pulseaudio
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-11-30 

Re: [Kernel-packages] [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys

[Jared Young]

Thank you!

On Sun, Mar 22, 2020 at 11:45 PM Kai-Heng Feng 
wrote:

> https://lkml.org/lkml/2020/3/23/29
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860303
>
> Title:
>   Backlight brightness cannot be adjusted using keys
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I cannot adjust the screen brightness using the keyboard keys or
>   changing /sys/call/backlight/intel_backlight/brightness values. I've
>   only been able to adjust the backlight using xrandr.
>
>   Followed bug report on
> https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques
> and attached files. Additional information:
>   1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not
> change the screen brightness
>   2. video.use_bios_initial_backlight=0 does not enable brightness to be
> changed
>   3. Cannot login to when using kernel paramater acpi_osi=. Login does not
> work and on one boot "y"s were being continuously typed without any keys
> being depressed. It was odd.
>   4. video.use_native_backlight=1 does not enabel brightness to be changed
>   5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had
> no impact
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: linux-image-5.3.0-26-generic 5.3.0-26.28
>   ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
>   Uname: Linux 5.3.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu8.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  jaredy 1649 F pulseaudio
>/dev/snd/pcmC0D0p:   jaredy 1649 F...m pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 19 19:51:45 2020
>   InstallationDate: Installed on 2020-01-03 (16 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   MachineType: HP HP Spectre x360 Convertible 13t-aw100
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic
> root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash
> acpi_backlight=vendor vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-5.3.0-26-generic N/A
>linux-backports-modules-5.3.0-26-generic  N/A
>linux-firmware1.183.3
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/15/2019
>   dmi.bios.vendor: AMI
>   dmi.bios.version: F.10
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 86FA
>   dmi.board.vendor: HP
>   dmi.board.version: 87.43
>   dmi.chassis.type: 31
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Spectre
>   dmi.product.name: HP Spectre x360 Convertible 13t-aw100
>   dmi.product.sku: 6YG70AV
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions
>

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

Title:
  Backlight brightness cannot be adjusted using keys

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot adjust the screen brightness using the keyboard keys or
  changing /sys/call/backlight/intel_backlight/brightness values. I've
  only been able to adjust the backlight using xrandr.

  Followed bug report on 
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and 
attached files. Additional information:
  1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change 
the screen brightness
  2. video.use_bios_initial_backlight=0 does not enable brightness to be changed
  3. Cannot login to when using kernel paramater acpi_osi=. Login does not work 
and on one boot "y"s were being continuously typed without any keys being 
depressed. It was odd. 
  4. video.use_native_backlight=1 does not enabel brightness to be changed
  5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no 
impact

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-generic 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaredy 1649 F pulseaudio
   /dev/snd/pcmC0D0p:   jaredy 1649 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 19 19:51:45 2020
  InstallationDate: Installed on 

[Kernel-packages] [Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Hui Wang]

@Jeremy,

Many machines have their internal mic connected to the PCH, to make the
internal mic work, the kernel needs those changes. And if you want the
sound to work as before with -43 kernel, you could add "snd-hda-intel
dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, then the audio
will work as -40 or before.

thx.

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command

[Carlo Wood]

I can now 100% reproduce this:

1) Run an application to test that the connected USB3 device (a 3D camera) 
works (cheese).
   It works.
2) Power off the 3D camera.
   This produces the well-known dmesg lines.
3) Power on the 3D camera; run cheese again: "No device detected".
4) sudo rmmod xhci_pci
5) sudo modprobe xhci_pci
6) Verify that dmesg printed detection of the 3D camera again, go to 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/1313279

Title:
  xHCI host not responding to stop endpoint command

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

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Hardware: Intel NUC D34010WYK (Core i3 4010U)
  Memory: 4 gigabytes
  USD device: PCTV 292e DVB-T tuner

  I have 2 PCTV 292e DVB-T tuners connected to the system. When I start
  to use either of the tuner, the xHCI host crashes. Since I'm booting
  from an USB disk. If I only connect 1 of the tuners, the system works
  ok. It does not matter which one of the tuners I connect.

  [   68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [   68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host.

  Sometimes this also leads to this:

  [  638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0
  [  638.183057] PGD 0 
  [  638.183077] Oops:  [#1] SMP 

  I can also observe the same fault with OpenELEC Linux distribution
  that runs kernel 3.14 when I run the system from an internal SATA SSD
  drive (not from an external USB disk).

  lsusb -v: http://paste.ubuntu.com/7343384/
  dmesg: http://sprunge.us/HMXH
  dmesg (crash type 2): http://sprunge.us/PSiX

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lubuntu-desktop 0.55
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sun Apr 27 11:12:22 2014
  InstallationDate: Installed on 2014-04-07 (19 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: lubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)

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

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

[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command

[Carlo Wood]

I bought a PCI Express USB 3.0 card to overcome the above... invain.
It performed better, in the sense that the xHCI host controller gets
less often unresponsive and that it just works with iommu enabled in
the BIOS as all the other USB did.

However, I STILL get a reproducible freeze up:

[ 5964.638609] xhci_hcd :08:00.0: xHCI host not responding to stop endpoint 
command.
[ 5964.639671] xhci_hcd :08:00.0: xHCI host controller not responding, 
assume dead
[ 5964.639679] xhci_hcd :08:00.0: HC died; cleaning up

I compiled kernel 5.6-rc7 with xhci_pci and xhci_hcd as modules.
This allows me to cover without rebooting: rmmod xhci_pci xhci_hcd
followed by a modprobe xhci_pci recovers functionality.

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

Title:
  xHCI host not responding to stop endpoint command

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

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Hardware: Intel NUC D34010WYK (Core i3 4010U)
  Memory: 4 gigabytes
  USD device: PCTV 292e DVB-T tuner

  I have 2 PCTV 292e DVB-T tuners connected to the system. When I start
  to use either of the tuner, the xHCI host crashes. Since I'm booting
  from an USB disk. If I only connect 1 of the tuners, the system works
  ok. It does not matter which one of the tuners I connect.

  [   68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [   68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host.

  Sometimes this also leads to this:

  [  638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0
  [  638.183057] PGD 0 
  [  638.183077] Oops:  [#1] SMP 

  I can also observe the same fault with OpenELEC Linux distribution
  that runs kernel 3.14 when I run the system from an internal SATA SSD
  drive (not from an external USB disk).

  lsusb -v: http://paste.ubuntu.com/7343384/
  dmesg: http://sprunge.us/HMXH
  dmesg (crash type 2): http://sprunge.us/PSiX

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lubuntu-desktop 0.55
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Sun Apr 27 11:12:22 2014
  InstallationDate: Installed on 2014-04-07 (19 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: lubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)

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

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

[Kernel-packages] [Bug 1866909] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mranw...@us.ibm.com 2020-03-23 19:45 EDT---
Hi Frank,

That's what I see, too, and all of those are in focal already, along
with the other three whose titles matched.  The config options in
500c7ab1a9db are already on in focal, too.

The ones we're not sure of are these two TBD ones:
sysfs enablement: TBD
platform keyring changes for powerpc: TBD

I think Nanya can confirm and add TBD ids.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Monday, 23. March 2020 21:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs

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

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

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Edward Savage]

Regenerating initramfs as suggested by Dan resolved this issue for me.

I did not attempt to change compression or change any settings in the
BIOS.

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

Title:
  initramfs unpacking failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

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

[Kernel-packages] [Bug 1868628] Re: Xenial update: 4.4.216 upstream stable release

[Khaled El Mously]

Also, this patch:
 - mm: make page ref count overflow check tighter and more explicit

seems to exist already in the xenial tree:

"d4a5d4fe58f1c28 mm: make page ref count overflow check tighter and more
explicit"

which was part of the fix for CVE-2019-11487

Both the xenial patch and the linux-stable patch purport to backport
f958d7b528b1b40c44cfda5eabe2d82760d868c3 - however, they are different
from each other. The one that we already had in Xenial is the one that
looks like the upstream patch. The linux-stable version of the patch is
quite different.

I will check with Cascardo on what to do about this.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11487

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

Title:
  Xenial update: 4.4.216 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  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:

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

  
  Linux 4.4.216
  crypto: algif_skcipher - use ZERO_OR_NULL_PTR in skcipher_recvmsg_async
  dm cache: fix a crash due to incorrect work item cancelling
  powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems
  dmaengine: coh901318: Fix a double lock bug in dma_tc_handle()
  hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT()
  ARM: imx: build v7_cpu_resume() unconditionally
  RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen()
  RDMA/iwcm: Fix iwcm work deallocation
  ASoC: dapm: Correct DAPM handling of active widgets during shutdown
  ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path
  ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output
  dmaengine: tegra-apb: Prevent race conditions of tasklet vs free list
  dmaengine: tegra-apb: Fix use-after-free
  vt: selection, push sel_lock up
  vt: selection, push console lock down
  vt: selection, close sel_buffer race
  fat: fix uninit-memory access for partial initialized inode
  vgacon: Fix a UAF in vgacon_invert_region
  usb: core: port: do error out if usb_autopm_get_interface() fails
  usb: core: hub: do error out if usb_autopm_get_interface() fails
  usb: quirks: add NO_LPM quirk for Logitech Screen Share
  usb: storage: Add quirk for Samsung Fit flash
  cifs: don't leak -EAGAIN for stat() during reconnect
  s390/cio: cio_ignore_proc_seq_next should increase position index
  watchdog: da9062: do not ping the hw during stop()
  net: ks8851-ml: Fix 16-bit IO operation
  net: ks8851-ml: Fix 16-bit data access
  net: ks8851-ml: Remove 8-bit bus accessors
  drm/msm/dsi: save pll state before dsi host is powered off
  drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
  usb: gadget: serial: fix Tx stall after buffer overflow
  usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
  serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
  audit: always check the netlink payload length in audit_receive_msg()
  fs: prevent page refcount overflow in pipe_buf_get
  pipe: add pipe_buf_get() helper
  mm: prevent get_user_pages() from overflowing page refcount
  mm, gup: ensure real head page is ref-counted when using hugepages
  mm, gup: remove broken VM_BUG_ON_PAGE compound check for hugepages
  mm: add 'try_get_page()' helper function
  mm: make page ref count overflow check tighter and more explicit
  slip: stop double free sl->dev in slip_open
  KVM: Check for a bad hva before dropping into the ghc slow path
  namei: only return -ECHILD from follow_dotdot_rcu()
  net: netlink: cap max groups which will be considered in netlink_bind()
  include/linux/bitops.h: introduce BITS_PER_TYPE
  ecryptfs: Fix up bad backport of fe2e082f5da5b4a0a92ae32978f81507ef37ec66
  i2c: jz4780: silence log flood on txabrt
  MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
  HID: hiddev: Fix race in in hiddev_disconnect()
  HID: core: increase HID report buffer size to 8KiB
  HID: core: fix off-by-one memset in hid_report_raw_event()
  audit: fix error handling in audit_data_to_entry()
  ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
  net: sched: correct flower port blocking
  nfc: pn544: Fix occasional HW initialization failure
  sctp: move the format error check out of __sctp_sf_do_9_1_abort
  ipv6: Fix route replacement with dev-only route
  ipv6: Fix nlmsg_flags when splitting a 

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Updates
- phase-changed: Monday, 23. March 2020 21:37 UTC
+ phase: Complete
+ phase-changed: Monday, 23. March 2020 21:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-updates: Ongoing -- packages not yet published
+ reason: {}
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Monday, 23. March 2020 21:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs

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

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

[Kernel-packages] [Bug 1868628] Re: Xenial update: 4.4.216 upstream stable release

[Khaled El Mously]

Also skipped:
 - mm: add 'try_get_page()' helper function

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

Title:
  Xenial update: 4.4.216 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  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:

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

  
  Linux 4.4.216
  crypto: algif_skcipher - use ZERO_OR_NULL_PTR in skcipher_recvmsg_async
  dm cache: fix a crash due to incorrect work item cancelling
  powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems
  dmaengine: coh901318: Fix a double lock bug in dma_tc_handle()
  hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT()
  ARM: imx: build v7_cpu_resume() unconditionally
  RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen()
  RDMA/iwcm: Fix iwcm work deallocation
  ASoC: dapm: Correct DAPM handling of active widgets during shutdown
  ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path
  ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output
  dmaengine: tegra-apb: Prevent race conditions of tasklet vs free list
  dmaengine: tegra-apb: Fix use-after-free
  vt: selection, push sel_lock up
  vt: selection, push console lock down
  vt: selection, close sel_buffer race
  fat: fix uninit-memory access for partial initialized inode
  vgacon: Fix a UAF in vgacon_invert_region
  usb: core: port: do error out if usb_autopm_get_interface() fails
  usb: core: hub: do error out if usb_autopm_get_interface() fails
  usb: quirks: add NO_LPM quirk for Logitech Screen Share
  usb: storage: Add quirk for Samsung Fit flash
  cifs: don't leak -EAGAIN for stat() during reconnect
  s390/cio: cio_ignore_proc_seq_next should increase position index
  watchdog: da9062: do not ping the hw during stop()
  net: ks8851-ml: Fix 16-bit IO operation
  net: ks8851-ml: Fix 16-bit data access
  net: ks8851-ml: Remove 8-bit bus accessors
  drm/msm/dsi: save pll state before dsi host is powered off
  drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
  usb: gadget: serial: fix Tx stall after buffer overflow
  usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
  serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
  audit: always check the netlink payload length in audit_receive_msg()
  fs: prevent page refcount overflow in pipe_buf_get
  pipe: add pipe_buf_get() helper
  mm: prevent get_user_pages() from overflowing page refcount
  mm, gup: ensure real head page is ref-counted when using hugepages
  mm, gup: remove broken VM_BUG_ON_PAGE compound check for hugepages
  mm: add 'try_get_page()' helper function
  mm: make page ref count overflow check tighter and more explicit
  slip: stop double free sl->dev in slip_open
  KVM: Check for a bad hva before dropping into the ghc slow path
  namei: only return -ECHILD from follow_dotdot_rcu()
  net: netlink: cap max groups which will be considered in netlink_bind()
  include/linux/bitops.h: introduce BITS_PER_TYPE
  ecryptfs: Fix up bad backport of fe2e082f5da5b4a0a92ae32978f81507ef37ec66
  i2c: jz4780: silence log flood on txabrt
  MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
  HID: hiddev: Fix race in in hiddev_disconnect()
  HID: core: increase HID report buffer size to 8KiB
  HID: core: fix off-by-one memset in hid_report_raw_event()
  audit: fix error handling in audit_data_to_entry()
  ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
  net: sched: correct flower port blocking
  nfc: pn544: Fix occasional HW initialization failure
  sctp: move the format error check out of __sctp_sf_do_9_1_abort
  ipv6: Fix route replacement with dev-only route
  ipv6: Fix nlmsg_flags when splitting a multipath route
  net: phy: restore mdio regs in the iproc mdio driver
  net: fib_rules: Correctly set table field when table number exceeds 8 bits
  sysrq: Remove duplicated sysrq message
  sysrq: Restore original console_loglevel when sysrq disabled
  cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
  cifs: Fix mode output in debugging statements
  cfg80211: check wiphy driver existence for drvinfo report
  mac80211: consider more elements in parsing CRC
  ipmi:ssif: Handle a possible NULL pointer reference
  ext4: fix potential race between s_group_info online resizing and access
  ext4: fix potential race between 

[Kernel-packages] [Bug 1868627] Re: Xenial update: 4.4.215 upstream stable release

[Khaled El Mously]

Skipped:
 - x86/vdso: Use RDPID in preference to LSL when available
 - KVM: x86: emulate RDPID
 - Revert "ipc, sem: remove uneeded sem_undo_list lock usage in exit_sem()"
 - KVM: nVMX: Refactor IO bitmap checks into helper function
 - KVM: nVMX: Check IO instruction VM-exit conditions

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

Title:
  Xenial update: 4.4.215 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  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:

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

  
  Linux 4.4.215
  xen: Enable interrupts when calling _cond_resched()
  ALSA: seq: Fix concurrent access to queue current tick/time
  ALSA: seq: Avoid concurrent access to queue flags
  ALSA: rawmidi: Avoid bit fields for state flags
  ecryptfs: replace BUG_ON with error handling code
  scsi: Revert "target: iscsi: Wait for all commands to finish before freeing a 
session"
  scsi: Revert "RDMA/isert: Fix a recently introduced regression related to 
logout"
  Btrfs: fix btrfs_wait_ordered_range() so that it waits for all ordered extents
  KVM: apic: avoid calculating pending eoi from an uninitialized val
  KVM: nVMX: Check IO instruction VM-exit conditions
  KVM: nVMX: Refactor IO bitmap checks into helper function
  ext4: add cond_resched() to __ext4_find_entry()
  ext4: fix a data race in EXT4_I(inode)->i_disksize
  netfilter: xt_bpf: add overflow checks
  KVM: nVMX: Don't emulate instructions in guest mode
  vt: vt_ioctl: fix race in VT_RESIZEX
  VT_RESIZEX: get rid of field-by-field copyin
  xhci: apply XHCI_PME_STUCK_QUIRK to Intel Comet Lake platforms
  Revert "ipc,sem: remove uneeded sem_undo_list lock usage in exit_sem()"
  tty: serial: imx: setup the correct sg entry for tx dma
  x86/mce/amd: Fix kobject lifetime
  staging: rtl8188eu: Fix potential overuse of kernel memory
  staging: rtl8188eu: Fix potential security hole
  USB: hub: Don't record a connect-change event during reset-resume
  USB: Fix novation SourceControl XL after suspend
  usb: uas: fix a plug & unplug racing
  staging: vt6656: fix sign of rx_dbm to bb_pre_ed_rssi.
  staging: android: ashmem: Disallow ashmem memory from being remapped
  floppy: check FDC index for errors before assigning it
  enic: prevent waking up stopped tx queues over watchdog reset
  selinux: ensure we cleanup the internal AVC counters on error in avc_update()
  brd: check and limit max_part par
  microblaze: Prevent the overflow of the start
  irqchip/gic-v3-its: Reference to its_invall_cmd descriptor when building 
INVALL
  bcache: explicity type cast in bset_bkey_last()
  reiserfs: prevent NULL pointer dereference in reiserfs_insert_item()
  lib/scatterlist.c: adjust indentation in __sg_alloc_table
  ocfs2: fix a NULL pointer dereference when call 
ocfs2_update_inode_fsync_trans()
  radeon: insert 10ms sleep in dce5_crtc_load_lut
  trigger_next should increase position index
  drm/nouveau/disp/nv50-: prevent oops when no channel method map provided
  iwlegacy: ensure loop counter addr does not wrap and cause an infinite loop
  hostap: Adjust indentation in prism2_hostapd_add_sta
  ARM: 8951/1: Fix Kexec compilation issue.
  jbd2: switch to use jbd2_journal_abort() when failed to submit the commit 
record
  ALSA: hda - Add docking station support for Lenovo Thinkpad T420s
  s390/ftrace: generate traced function stack frame
  remoteproc: Initialize rproc_class before use
  ide: serverworks: potential overflow in svwks_set_pio_mode()
  cmd64x: potential buffer overflow in cmd64x_program_timings()
  scsi: iscsi: Don't destroy session if there are outstanding connections
  iommu/arm-smmu-v3: Use WRITE_ONCE() when changing validity of an STE
  drm/vmwgfx: prevent memory leak in vmw_cmdbuf_res_add
  drm/nouveau: Fix copy-paste error in nouveau_fence_wait_uevent_handler
  driver core: Print device when resources present in really_probe()
  PCI: Don't disable bridge BARs when assigning bus resources
  ASoC: atmel: fix build error with CONFIG_SND_ATMEL_SOC_DMA=m
  wan: ixp4xx_hss: fix compile-testing on 64-bit
  Input: edt-ft5x06 - work around first register access error
  rcu: Use WRITE_ONCE() for assignments to ->pprev for hlist_nulls
  soc/tegra: fuse: Correct straps' address for older Tegra124 device trees
  usbip: Fix unsafe unaligned pointer usage
  tools lib api fs: Fix gcc9 stringop-truncation 

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Updates
- phase-changed: Monday, 23. March 2020 17:46 UTC
+ phase: Promote to Updates
+ phase-changed: Monday, 23. March 2020 21:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Pending -- ready to copy
+   promote-to-updates: Ongoing -- packages not yet published
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Monday, 23. March 2020 21:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason: {}
  variant: debs

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

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

[Kernel-packages] [Bug 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.

[semidark]

and again. it got stuck. even with the intel_pstate=no_hwp kernel
parameter.Damn!

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

Title:
  intel_pstate not working. CPU frequency fixed at 800MHz. No cpu
  frequency scaling.

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

Bug description:
  intel_pstate not working. CPU frequency fixed at 800MHz.

  I've tried to modify frequency using "cpufreq-set" and also by
  directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*"
  to no success.

  I tried different versions of kernel, it started working on 4.17.0 but
  stopped working soon. These are the versions I tested.

  5.2.3   - Not Working
  5.1.0   - Not Working
  4.19.60 - Not Working
  4.18.20 - Not Working
  4.17.19 - Not Working
  4.17.10 - Not Working
  4.17.5  - Not Working
  4.17.3  - Not Working
  4.17.2  - Working
  4.17.1  - Working
  4.17.0  - Working
  4.16.18 - Not Working
  4.15.0  - Not Working

  Please let me know if anything else is needed.
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-55-generic 4.15.0-55.60
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srijan 2219 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Jul 27 11:34:10 2019
  InstallationDate: Installed on 2018-11-25 (243 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Predator PH315-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic 
root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor 
i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 
nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 
i915.disable_power_well=1 nmi_watchdog=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-55-generic N/A
   linux-backports-modules-4.15.0-55-generic  N/A
   linux-firmware 1.173.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Sienta_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.24
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24:
  dmi.product.family: Predator Helios 300
  dmi.product.name: Predator PH315-51
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1868628] Re: Xenial update: 4.4.216 upstream stable release

[Khaled El Mously]

Skipped:
 - include/linux/bitops.h: introduce BITS_PER_TYPE
 - mm, gup: ensure real head page is ref-counted when using hugepages
 - mm: prevent get_user_pages() from overflowing page refcount
 - pipe: add pipe_buf_get() helper
 - fs: prevent page refcount overflow in pipe_buf_get

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

Title:
  Xenial update: 4.4.216 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  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:

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

  
  Linux 4.4.216
  crypto: algif_skcipher - use ZERO_OR_NULL_PTR in skcipher_recvmsg_async
  dm cache: fix a crash due to incorrect work item cancelling
  powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems
  dmaengine: coh901318: Fix a double lock bug in dma_tc_handle()
  hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT()
  ARM: imx: build v7_cpu_resume() unconditionally
  RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen()
  RDMA/iwcm: Fix iwcm work deallocation
  ASoC: dapm: Correct DAPM handling of active widgets during shutdown
  ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path
  ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output
  dmaengine: tegra-apb: Prevent race conditions of tasklet vs free list
  dmaengine: tegra-apb: Fix use-after-free
  vt: selection, push sel_lock up
  vt: selection, push console lock down
  vt: selection, close sel_buffer race
  fat: fix uninit-memory access for partial initialized inode
  vgacon: Fix a UAF in vgacon_invert_region
  usb: core: port: do error out if usb_autopm_get_interface() fails
  usb: core: hub: do error out if usb_autopm_get_interface() fails
  usb: quirks: add NO_LPM quirk for Logitech Screen Share
  usb: storage: Add quirk for Samsung Fit flash
  cifs: don't leak -EAGAIN for stat() during reconnect
  s390/cio: cio_ignore_proc_seq_next should increase position index
  watchdog: da9062: do not ping the hw during stop()
  net: ks8851-ml: Fix 16-bit IO operation
  net: ks8851-ml: Fix 16-bit data access
  net: ks8851-ml: Remove 8-bit bus accessors
  drm/msm/dsi: save pll state before dsi host is powered off
  drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
  usb: gadget: serial: fix Tx stall after buffer overflow
  usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
  serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
  audit: always check the netlink payload length in audit_receive_msg()
  fs: prevent page refcount overflow in pipe_buf_get
  pipe: add pipe_buf_get() helper
  mm: prevent get_user_pages() from overflowing page refcount
  mm, gup: ensure real head page is ref-counted when using hugepages
  mm, gup: remove broken VM_BUG_ON_PAGE compound check for hugepages
  mm: add 'try_get_page()' helper function
  mm: make page ref count overflow check tighter and more explicit
  slip: stop double free sl->dev in slip_open
  KVM: Check for a bad hva before dropping into the ghc slow path
  namei: only return -ECHILD from follow_dotdot_rcu()
  net: netlink: cap max groups which will be considered in netlink_bind()
  include/linux/bitops.h: introduce BITS_PER_TYPE
  ecryptfs: Fix up bad backport of fe2e082f5da5b4a0a92ae32978f81507ef37ec66
  i2c: jz4780: silence log flood on txabrt
  MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
  HID: hiddev: Fix race in in hiddev_disconnect()
  HID: core: increase HID report buffer size to 8KiB
  HID: core: fix off-by-one memset in hid_report_raw_event()
  audit: fix error handling in audit_data_to_entry()
  ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
  net: sched: correct flower port blocking
  nfc: pn544: Fix occasional HW initialization failure
  sctp: move the format error check out of __sctp_sf_do_9_1_abort
  ipv6: Fix route replacement with dev-only route
  ipv6: Fix nlmsg_flags when splitting a multipath route
  net: phy: restore mdio regs in the iproc mdio driver
  net: fib_rules: Correctly set table field when table number exceeds 8 bits
  sysrq: Remove duplicated sysrq message
  sysrq: Restore original console_loglevel when sysrq disabled
  cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
  cifs: Fix mode output in debugging statements
  cfg80211: check wiphy driver existence for drvinfo 

[Kernel-packages] [Bug 1868629] Re: Xenial update: 4.4.217 upstream stable release

[Khaled El Mously]

Skipped:
 - mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() (Stefan 
applied that as a SAUCE patch, but it's basically identical)

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

Title:
  Xenial update: 4.4.217 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  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:

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

  
  Linux 4.4.217
  ipv4: ensure rcu_read_lock() in cipso_v4_error()
  mm: slub: add missing TID bump in kmem_cache_alloc_bulk()
  ARM: 8958/1: rename missed uaccess .fixup section
  ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_functional()
  jbd2: fix data races at struct journal_head
  signal: avoid double atomic counter increments for user accounting
  net: ks8851-ml: Fix IRQ handling and locking
  perf/amd/uncore: Replace manual sampling check with CAP_NO_INTERRUPT flag
  batman-adv: Don't schedule OGM for disabled interface
  batman-adv: Avoid free/alloc race when handling OGM buffer
  batman-adv: Only read OGM tvlv_len after buffer len check
  batman-adv: Reduce tt_global hash refcnt only for removed entry
  batman-adv: Reduce tt_local hash refcnt only for removed entry
  batman-adv: Reduce claim hash refcnt only for removed entry
  batman-adv: Prevent duplicated tvlv handler
  batman-adv: Prevent duplicated global TT entry
  batman-adv: Prevent duplicated nc_node entry
  batman-adv: Prevent duplicated gateway_node entry
  batman-adv: Avoid storing non-TT-sync flags on singular entries too
  batman-adv: Fix debugfs path for renamed softif
  batman-adv: Fix debugfs path for renamed hardif
  batman-adv: prevent TT request storms by not sending inconsistent TT TLVLs
  batman-adv: Fix TT sync flags for intermediate TT responses
  batman-adv: Avoid race in TT TVLV allocator helper
  batman-adv: Fix skbuff rcsum on packet reroute
  batman-adv: update data pointers after skb_cow()
  batman-adv: Fix internal interface indices types
  batman-adv: Fix lock for ogm cnt access in batadv_iv_ogm_calc_tq
  batman-adv: fix TT sync flag inconsistencies
  batman-adv: Fix rx packet/bytes stats on local ARP reply
  batman-adv: Fix transmission of final, 16th fragment
  batman-adv: Fix double free during fragment merge error
  batman-adv: Add missing refcnt for last_candidate
  batman-adv: Fix speedy join in gateway client mode
  batman-adv: Free last_bonding_candidate on release of orig_node
  batman-adv: Fix reference leak in batadv_find_router
  batman-adv: Fix non-atomic bla_claim::backbone_gw access
  batman-adv: lock crc access in bridge loop avoidance
  batman-adv: Fix orig_node_vlan leak on orig_node_release
  batman-adv: Avoid nullptr dereference in dat after vlan_insert_tag
  batman-adv: Avoid nullptr dereference in bla after vlan_insert_tag
  batman-adv: Clean up untagged vlan when destroying via rtnl-link
  batman-adv: Fix ICMP RR ethernet access after skb_linearize
  batman-adv: Fix use-after-free/double-free of tt_req_node
  batman-adv: fix skb deref after free
  batman-adv: Avoid duplicate neigh_node additions
  batman-adv: Fix reference counting of vlan object for tt_local_entry
  batman-adv: Drop reference to netdevice on last reference
  batman-adv: Deactivate TO_BE_ACTIVATED hardif on shutdown
  batman-adv: init neigh node last seen field
  batman-adv: Fix integer overflow in batadv_iv_ogm_calc_tq
  batman-adv: Fix unexpected free of bcast_own on add_if error
  batman-adv: Avoid endless loop in bat-on-bat netdevice check
  batman-adv: Only put orig_node_vlan list reference when removed
  batman-adv: Only put gw_node list reference when removed
  batman-adv: Fix invalid read while copying bat_iv.bcast_own
  efi: Add a sanity check to efivar_store_raw()
  ipv6: restrict IPV6_ADDRFORM operation
  mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame()
  iommu/vt-d: Ignore devices with out-of-spec domain number
  iommu/vt-d: Fix the wrong printing in RHSA parsing
  netfilter: cthelper: add missing attribute validation for cthelper
  nl80211: add missing attribute validation for channel switch
  nl80211: add missing attribute validation for critical protocol indication
  iommu/vt-d: Fix a bug in intel_iommu_iova_to_phys() for huge page
  iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint
  efi: Fix a race and a buffer overflow while reading efivars via 

[Kernel-packages] [Bug 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 4.15.0-1075.80

---
linux-azure (4.15.0-1075.80) xenial; urgency=medium

  * xenial/linux-azure: 4.15.0-1075.80 -proposed tracker (LP: #1867860)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 09:06:32 -0300

** Changed in: linux-azure (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  xenial/linux-azure: 4.15.0-1074.79 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Saturday, 14. March 2020 01:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Stalled -- waiting for signoff
  trackers:
trusty/linux-azure: bug 1865197
xenial/linux-azure/azure-kernel: bug 1865196
  variant: debs

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

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

[Kernel-packages] [Bug 1863285] Re: bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 5.0.0-1035.37

---
linux-azure (5.0.0-1035.37) bionic; urgency=medium

  * bionic/linux-azure: 5.0.0-1035.37 -proposed tracker (LP: #1867856)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 00:38:02 -0300

** Changed in: linux-azure (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  bionic/linux-azure: 5.0.0-1033.35 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865110
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 18. February 2020 07:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1863284
  variant: debs

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

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

[Kernel-packages] [Bug 1865193] Re: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 5.0.0-1035.37

---
linux-azure (5.0.0-1035.37) bionic; urgency=medium

  * bionic/linux-azure: 5.0.0-1035.37 -proposed tracker (LP: #1867856)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 00:38:02 -0300

** Changed in: linux-azure (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  bionic/linux-azure: 5.0.0-1034.36 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865110
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Monday, 16. March 2020 11:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure/azure-kernel: bug 1865192
  variant: debs

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

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

[Kernel-packages] [Bug 1864745] Re: xenial/linux-azure: 4.15.0-1073.78 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 4.15.0-1075.80

---
linux-azure (4.15.0-1075.80) xenial; urgency=medium

  * xenial/linux-azure: 4.15.0-1075.80 -proposed tracker (LP: #1867860)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 09:06:32 -0300

** Changed in: linux-azure (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  xenial/linux-azure: 4.15.0-1073.78 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865109
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 27. February 2020 22:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1864744
xenial/linux-azure/azure-kernel: bug 1864743
  variant: debs

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

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

[Kernel-packages] [Bug 1863344] Re: xenial/linux-azure: 4.15.0-1072.77 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 4.15.0-1075.80

---
linux-azure (4.15.0-1075.80) xenial; urgency=medium

  * xenial/linux-azure: 4.15.0-1075.80 -proposed tracker (LP: #1867860)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 09:06:32 -0300

** Changed in: linux-azure (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  xenial/linux-azure: 4.15.0-1072.77 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1864753
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 20. February 2020 23:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1863343
xenial/linux-azure/azure-kernel: bug 1863342
  variant: debs

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.0.0-1035.37

---
linux-azure (5.0.0-1035.37) bionic; urgency=medium

  * bionic/linux-azure: 5.0.0-1035.37 -proposed tracker (LP: #1867856)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 00:38:02 -0300

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

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-base source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-base source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  Fix Released

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.3.0-1016.17

---
linux-azure (5.3.0-1016.17) eoan; urgency=medium

  * eoan/linux-azure: 5.3.0-1016.17 -proposed tracker (LP: #1867852)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 13:51:06 -0300

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

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

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-base source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-base source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  Fix Released

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 4.15.0-1075.80

---
linux-azure (4.15.0-1075.80) xenial; urgency=medium

  * xenial/linux-azure: 4.15.0-1075.80 -proposed tracker (LP: #1867860)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 09:06:32 -0300

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-base source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-base source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-base source package in Focal:
  Fix Released

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake

[frio]

Hi, sorry, for whatever reason I missed notifications about this thread
in my inbox.

I'm on BIOS 1.1.3; I believe you can update using fwupdmgr if you're on
an older version still.  I've forgotten which screen the option is
under; I'll post again next time I reboot.

I may have been replying to the wrong thread, however -- there's another
thread about display corruption on resuming from S3 (which has to be
manually enabled), and... the reply I *thought* I put there,
suspiciously, is in this thread.  Doh.

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

Title:
  Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on
  Intel Comet Lake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just received a new Dell XPS 13 7390 laptop. With factory
  preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics
  was severely distorted. The display would constantly flicker with
  areas of the display staying black or showing patterns of square color
  blocks.

  Booting in recovery mode worked, though and I was able to install all
  updates for preinstalled 18.04 LTS with the OEM kernel. Problems in
  non-recovery mode persisted after installing all updates. I then
  updated to Ubuntu 19.04 and changed to "generic" linux kernel image
  without success: Problem persisted, only recovery mode was usable. I
  updated once more to 19.10 again without any success.

  From the perhaps related bug #1849947 I tried latest drm-tip kernel
  from

  https://kernel.ubuntu.com/~kernel-ppa/mainline/

  drm-tip kernel solves the issue for first boot, but after resuming
  from suspend, the same issues display issues occur.

  Kernel images I tried:
  - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics 
output without "nomodeset"
  - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output 
without "nomodeset"
  - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output 
without "nomodeset"
  - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted 
graphics output after resuming from suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.0-994-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 18:51:15 2019
  DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-11-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic 
root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell 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 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1863274] Re: eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 5.3.0-1016.17

---
linux-azure (5.3.0-1016.17) eoan; urgency=medium

  * eoan/linux-azure: 5.3.0-1016.17 -proposed tracker (LP: #1867852)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 13:51:06 -0300

** Changed in: linux-azure (Ubuntu Eoan)
   Status: Confirmed => Fix Released

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

Title:
  eoan/linux-azure: 5.3.0-1014.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Eoan:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Tuesday, 18. February 2020 07:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1863273
  variant: debs

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

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

[Kernel-packages] [Bug 1865190] Re: eoan/linux-azure: 5.3.0-1015.16 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-azure - 5.3.0-1016.17

---
linux-azure (5.3.0-1016.17) eoan; urgency=medium

  * eoan/linux-azure: 5.3.0-1016.17 -proposed tracker (LP: #1867852)

  * linux-azure: Update SGX version and udev rules (LP: #1867820)
- SAUCE: linux-azure: Update SGX to version LD_1.22
- [Packaging] linux-azure: Add dependency to linux-base-sgx

 -- Marcelo Henrique Cerri   Wed, 18 Mar
2020 13:51:06 -0300

** Changed in: linux-azure (Ubuntu Eoan)
   Status: Confirmed => Fix Released

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

Title:
  eoan/linux-azure: 5.3.0-1015.16 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1865111
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Signoff
  phase-changed: Friday, 13. March 2020 17:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Stalled -- waiting for signoff
  trackers:
bionic/linux-azure-5.3: bug 1865189
  variant: debs

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

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

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  In Progress
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Updates
  phase-changed: Monday, 23. March 2020 17:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  variant: debs

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

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

[Kernel-packages] [Bug 1868626] [NEW] Allow BPF tracing under lockdown

[Thadeu Lima de Souza Cascardo]

Public bug reported:

[Impact]
BPF tracing is allowed on Bionic and on Focal under integrity lockdown, which 
is going to be the default before release. Right now, Eoan does not allow 
kprobes and BPF reads under lockdown, preventing BPF tracing and kprobe tracing.

[Test case]
sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping...\n", pid); }'
sudo bpftrace -e 'tracepoint:syscalls:sys_enter_openat { printf("filename: 
[%s]; flags: [%d]\n", str(args->filename), args->flags); }'

The last one should show the filename and flags.

[Regression potential]
This would allow privileged users to possibly read some kernel data that was 
not possible before. However, this is already possible on systems that are not 
under lockdown, which are all non-secure boot systems by default. This also 
matches the behavior of signed kernels of Bionic and Focal.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed

** Affects: linux (Ubuntu Eoan)
 Importance: Critical
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Allow BPF tracing under lockdown

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

Bug description:
  [Impact]
  BPF tracing is allowed on Bionic and on Focal under integrity lockdown, which 
is going to be the default before release. Right now, Eoan does not allow 
kprobes and BPF reads under lockdown, preventing BPF tracing and kprobe tracing.

  [Test case]
  sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping...\n", pid); 
}'
  sudo bpftrace -e 'tracepoint:syscalls:sys_enter_openat { printf("filename: 
[%s]; flags: [%d]\n", str(args->filename), args->flags); }'

  The last one should show the filename and flags.

  [Regression potential]
  This would allow privileged users to possibly read some kernel data that was 
not possible before. However, this is already possible on systems that are not 
under lockdown, which are all non-secure boot systems by default. This also 
matches the behavior of signed kernels of Bionic and Focal.

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

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

[Kernel-packages] [Bug 1868627] [NEW] Xenial update: 4.4.215 upstream stable release

[Khaled El Mously]

Public bug reported:


SRU Justification

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

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


Linux 4.4.215
xen: Enable interrupts when calling _cond_resched()
ALSA: seq: Fix concurrent access to queue current tick/time
ALSA: seq: Avoid concurrent access to queue flags
ALSA: rawmidi: Avoid bit fields for state flags
ecryptfs: replace BUG_ON with error handling code
scsi: Revert "target: iscsi: Wait for all commands to finish before freeing a 
session"
scsi: Revert "RDMA/isert: Fix a recently introduced regression related to 
logout"
Btrfs: fix btrfs_wait_ordered_range() so that it waits for all ordered extents
KVM: apic: avoid calculating pending eoi from an uninitialized val
KVM: nVMX: Check IO instruction VM-exit conditions
KVM: nVMX: Refactor IO bitmap checks into helper function
ext4: add cond_resched() to __ext4_find_entry()
ext4: fix a data race in EXT4_I(inode)->i_disksize
netfilter: xt_bpf: add overflow checks
KVM: nVMX: Don't emulate instructions in guest mode
vt: vt_ioctl: fix race in VT_RESIZEX
VT_RESIZEX: get rid of field-by-field copyin
xhci: apply XHCI_PME_STUCK_QUIRK to Intel Comet Lake platforms
Revert "ipc,sem: remove uneeded sem_undo_list lock usage in exit_sem()"
tty: serial: imx: setup the correct sg entry for tx dma
x86/mce/amd: Fix kobject lifetime
staging: rtl8188eu: Fix potential overuse of kernel memory
staging: rtl8188eu: Fix potential security hole
USB: hub: Don't record a connect-change event during reset-resume
USB: Fix novation SourceControl XL after suspend
usb: uas: fix a plug & unplug racing
staging: vt6656: fix sign of rx_dbm to bb_pre_ed_rssi.
staging: android: ashmem: Disallow ashmem memory from being remapped
floppy: check FDC index for errors before assigning it
enic: prevent waking up stopped tx queues over watchdog reset
selinux: ensure we cleanup the internal AVC counters on error in avc_update()
brd: check and limit max_part par
microblaze: Prevent the overflow of the start
irqchip/gic-v3-its: Reference to its_invall_cmd descriptor when building INVALL
bcache: explicity type cast in bset_bkey_last()
reiserfs: prevent NULL pointer dereference in reiserfs_insert_item()
lib/scatterlist.c: adjust indentation in __sg_alloc_table
ocfs2: fix a NULL pointer dereference when call ocfs2_update_inode_fsync_trans()
radeon: insert 10ms sleep in dce5_crtc_load_lut
trigger_next should increase position index
drm/nouveau/disp/nv50-: prevent oops when no channel method map provided
iwlegacy: ensure loop counter addr does not wrap and cause an infinite loop
hostap: Adjust indentation in prism2_hostapd_add_sta
ARM: 8951/1: Fix Kexec compilation issue.
jbd2: switch to use jbd2_journal_abort() when failed to submit the commit record
ALSA: hda - Add docking station support for Lenovo Thinkpad T420s
s390/ftrace: generate traced function stack frame
remoteproc: Initialize rproc_class before use
ide: serverworks: potential overflow in svwks_set_pio_mode()
cmd64x: potential buffer overflow in cmd64x_program_timings()
scsi: iscsi: Don't destroy session if there are outstanding connections
iommu/arm-smmu-v3: Use WRITE_ONCE() when changing validity of an STE
drm/vmwgfx: prevent memory leak in vmw_cmdbuf_res_add
drm/nouveau: Fix copy-paste error in nouveau_fence_wait_uevent_handler
driver core: Print device when resources present in really_probe()
PCI: Don't disable bridge BARs when assigning bus resources
ASoC: atmel: fix build error with CONFIG_SND_ATMEL_SOC_DMA=m
wan: ixp4xx_hss: fix compile-testing on 64-bit
Input: edt-ft5x06 - work around first register access error
rcu: Use WRITE_ONCE() for assignments to ->pprev for hlist_nulls
soc/tegra: fuse: Correct straps' address for older Tegra124 device trees
usbip: Fix unsafe unaligned pointer usage
tools lib api fs: Fix gcc9 stringop-truncation compilation error
ALSA: sh: Fix compile warning wrt const
pinctrl: sh-pfc: sh7269: Fix CAN function GPIOs
x86/vdso: Provide missing include file
ARM: dts: r8a7779: Add device node for ARM global timer
scsi: aic7xxx: Adjust indentation in ahc_find_syncrate
ACPICA: Disassembler: create buffer fields in ACPI_PARSE_LOAD_PASS1
orinoco: avoid assertion in case of NULL pointer
rtlwifi: rtl_pci: Fix -Wcast-function-type
iwlegacy: Fix -Wcast-function-type
ipw2x00: Fix -Wcast-function-type
b43legacy: Fix -Wcast-function-type
ALSA: usx2y: Adjust indentation in snd_usX2Y_hwdep_dsp_status
reiserfs: Fix spurious unlock in reiserfs_fill_super() error handling
NFC: port100: Convert cpu_to_le16(le16_to_cpu(E1) + E2) to use le16_add_cpu().
regulator: rk808: Lower 

[Kernel-packages] [Bug 1868629] [NEW] Xenial update: 4.4.217 upstream stable release

[Khaled El Mously]

Public bug reported:


SRU Justification

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

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


Linux 4.4.217
ipv4: ensure rcu_read_lock() in cipso_v4_error()
mm: slub: add missing TID bump in kmem_cache_alloc_bulk()
ARM: 8958/1: rename missed uaccess .fixup section
ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_functional()
jbd2: fix data races at struct journal_head
signal: avoid double atomic counter increments for user accounting
net: ks8851-ml: Fix IRQ handling and locking
perf/amd/uncore: Replace manual sampling check with CAP_NO_INTERRUPT flag
batman-adv: Don't schedule OGM for disabled interface
batman-adv: Avoid free/alloc race when handling OGM buffer
batman-adv: Only read OGM tvlv_len after buffer len check
batman-adv: Reduce tt_global hash refcnt only for removed entry
batman-adv: Reduce tt_local hash refcnt only for removed entry
batman-adv: Reduce claim hash refcnt only for removed entry
batman-adv: Prevent duplicated tvlv handler
batman-adv: Prevent duplicated global TT entry
batman-adv: Prevent duplicated nc_node entry
batman-adv: Prevent duplicated gateway_node entry
batman-adv: Avoid storing non-TT-sync flags on singular entries too
batman-adv: Fix debugfs path for renamed softif
batman-adv: Fix debugfs path for renamed hardif
batman-adv: prevent TT request storms by not sending inconsistent TT TLVLs
batman-adv: Fix TT sync flags for intermediate TT responses
batman-adv: Avoid race in TT TVLV allocator helper
batman-adv: Fix skbuff rcsum on packet reroute
batman-adv: update data pointers after skb_cow()
batman-adv: Fix internal interface indices types
batman-adv: Fix lock for ogm cnt access in batadv_iv_ogm_calc_tq
batman-adv: fix TT sync flag inconsistencies
batman-adv: Fix rx packet/bytes stats on local ARP reply
batman-adv: Fix transmission of final, 16th fragment
batman-adv: Fix double free during fragment merge error
batman-adv: Add missing refcnt for last_candidate
batman-adv: Fix speedy join in gateway client mode
batman-adv: Free last_bonding_candidate on release of orig_node
batman-adv: Fix reference leak in batadv_find_router
batman-adv: Fix non-atomic bla_claim::backbone_gw access
batman-adv: lock crc access in bridge loop avoidance
batman-adv: Fix orig_node_vlan leak on orig_node_release
batman-adv: Avoid nullptr dereference in dat after vlan_insert_tag
batman-adv: Avoid nullptr dereference in bla after vlan_insert_tag
batman-adv: Clean up untagged vlan when destroying via rtnl-link
batman-adv: Fix ICMP RR ethernet access after skb_linearize
batman-adv: Fix use-after-free/double-free of tt_req_node
batman-adv: fix skb deref after free
batman-adv: Avoid duplicate neigh_node additions
batman-adv: Fix reference counting of vlan object for tt_local_entry
batman-adv: Drop reference to netdevice on last reference
batman-adv: Deactivate TO_BE_ACTIVATED hardif on shutdown
batman-adv: init neigh node last seen field
batman-adv: Fix integer overflow in batadv_iv_ogm_calc_tq
batman-adv: Fix unexpected free of bcast_own on add_if error
batman-adv: Avoid endless loop in bat-on-bat netdevice check
batman-adv: Only put orig_node_vlan list reference when removed
batman-adv: Only put gw_node list reference when removed
batman-adv: Fix invalid read while copying bat_iv.bcast_own
efi: Add a sanity check to efivar_store_raw()
ipv6: restrict IPV6_ADDRFORM operation
mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame()
iommu/vt-d: Ignore devices with out-of-spec domain number
iommu/vt-d: Fix the wrong printing in RHSA parsing
netfilter: cthelper: add missing attribute validation for cthelper
nl80211: add missing attribute validation for channel switch
nl80211: add missing attribute validation for critical protocol indication
iommu/vt-d: Fix a bug in intel_iommu_iova_to_phys() for huge page
iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint
efi: Fix a race and a buffer overflow while reading efivars via sysfs
ARC: define __ALIGN_STR and __ALIGN symbols for ARC
KVM: x86: clear stale x86_emulate_ctxt->intercept value
gfs2_atomic_open(): fix O_EXCL|O_CREAT handling on cold dcache
drm/amd/display: remove duplicated assignment to grph_obj_type
iommu/vt-d: quirk_ioat_snb_local_iommu: replace WARN_TAINT with pr_warn + 
add_taint
net: fq: add missing attribute validation for orphan mask
bonding/alb: make sure arp header is pulled before accessing it
slip: make slhc_compress() more robust against malicious packets
net: fec: validate the new settings in fec_enet_set_coalesce()
macvlan: add cond_resched() during multicast 

[Kernel-packages] [Bug 1868628] [NEW] Xenial update: 4.4.216 upstream stable release

[Khaled El Mously]

Public bug reported:


SRU Justification

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

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


Linux 4.4.216
crypto: algif_skcipher - use ZERO_OR_NULL_PTR in skcipher_recvmsg_async
dm cache: fix a crash due to incorrect work item cancelling
powerpc: fix hardware PMU exception bug on PowerVM compatibility mode systems
dmaengine: coh901318: Fix a double lock bug in dma_tc_handle()
hwmon: (adt7462) Fix an error return in ADT7462_REG_VOLT()
ARM: imx: build v7_cpu_resume() unconditionally
RMDA/cm: Fix missing ib_cm_destroy_id() in ib_cm_insert_listen()
RDMA/iwcm: Fix iwcm work deallocation
ASoC: dapm: Correct DAPM handling of active widgets during shutdown
ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path
ASoC: pcm: Fix possible buffer overflow in dpcm state sysfs output
dmaengine: tegra-apb: Prevent race conditions of tasklet vs free list
dmaengine: tegra-apb: Fix use-after-free
vt: selection, push sel_lock up
vt: selection, push console lock down
vt: selection, close sel_buffer race
fat: fix uninit-memory access for partial initialized inode
vgacon: Fix a UAF in vgacon_invert_region
usb: core: port: do error out if usb_autopm_get_interface() fails
usb: core: hub: do error out if usb_autopm_get_interface() fails
usb: quirks: add NO_LPM quirk for Logitech Screen Share
usb: storage: Add quirk for Samsung Fit flash
cifs: don't leak -EAGAIN for stat() during reconnect
s390/cio: cio_ignore_proc_seq_next should increase position index
watchdog: da9062: do not ping the hw during stop()
net: ks8851-ml: Fix 16-bit IO operation
net: ks8851-ml: Fix 16-bit data access
net: ks8851-ml: Remove 8-bit bus accessors
drm/msm/dsi: save pll state before dsi host is powered off
drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
usb: gadget: serial: fix Tx stall after buffer overflow
usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
audit: always check the netlink payload length in audit_receive_msg()
fs: prevent page refcount overflow in pipe_buf_get
pipe: add pipe_buf_get() helper
mm: prevent get_user_pages() from overflowing page refcount
mm, gup: ensure real head page is ref-counted when using hugepages
mm, gup: remove broken VM_BUG_ON_PAGE compound check for hugepages
mm: add 'try_get_page()' helper function
mm: make page ref count overflow check tighter and more explicit
slip: stop double free sl->dev in slip_open
KVM: Check for a bad hva before dropping into the ghc slow path
namei: only return -ECHILD from follow_dotdot_rcu()
net: netlink: cap max groups which will be considered in netlink_bind()
include/linux/bitops.h: introduce BITS_PER_TYPE
ecryptfs: Fix up bad backport of fe2e082f5da5b4a0a92ae32978f81507ef37ec66
i2c: jz4780: silence log flood on txabrt
MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
HID: hiddev: Fix race in in hiddev_disconnect()
HID: core: increase HID report buffer size to 8KiB
HID: core: fix off-by-one memset in hid_report_raw_event()
audit: fix error handling in audit_data_to_entry()
ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
net: sched: correct flower port blocking
nfc: pn544: Fix occasional HW initialization failure
sctp: move the format error check out of __sctp_sf_do_9_1_abort
ipv6: Fix route replacement with dev-only route
ipv6: Fix nlmsg_flags when splitting a multipath route
net: phy: restore mdio regs in the iproc mdio driver
net: fib_rules: Correctly set table field when table number exceeds 8 bits
sysrq: Remove duplicated sysrq message
sysrq: Restore original console_loglevel when sysrq disabled
cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
cifs: Fix mode output in debugging statements
cfg80211: check wiphy driver existence for drvinfo report
mac80211: consider more elements in parsing CRC
ipmi:ssif: Handle a possible NULL pointer reference
ext4: fix potential race between s_group_info online resizing and access
ext4: fix potential race between s_flex_groups online resizing and access
ext4: fix potential race between online resizing and write operations
iwlwifi: pcie: fix rb_allocator workqueue allocation

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

** Affects: linux (Ubuntu Xenial)
 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 Xenial)
   Importance: Undecided
 

[Kernel-packages] [Bug 1868623] [NEW] Bionic update: upstream stable patchset 2020-03-23

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2020-03-23

Ported from the following upstream stable releases:
v4.14.173, v4.19.107,
   v4.19.108,
   v4.19.109

   from git://git.kernel.org/

iwlwifi: pcie: fix rb_allocator workqueue allocation
ext4: fix potential race between online resizing and write operations
ext4: fix potential race between s_flex_groups online resizing and access
ext4: fix potential race between s_group_info online resizing and access
ipmi:ssif: Handle a possible NULL pointer reference
drm/msm: Set dma maximum segment size for mdss
dax: pass NOWAIT flag to iomap_apply
mac80211: consider more elements in parsing CRC
cfg80211: check wiphy driver existence for drvinfo report
qmi_wwan: re-add DW5821e pre-production variant
qmi_wwan: unconditionally reject 2 ep interfaces
net: ena: fix potential crash when rxfh key is NULL
net: ena: fix uses of round_jiffies()
net: ena: add missing ethtool TX timestamping indication
net: ena: fix incorrect default RSS key
net: ena: rss: fix failure to get indirection table
net: ena: rss: store hash function as values and not bits
net: ena: fix incorrectly saving queue numbers when setting RSS indirection 
table
net: ena: ethtool: use correct value for crc32 hash
net: ena: ena-com.c: prevent NULL pointer dereference
cifs: Fix mode output in debugging statements
cfg80211: add missing policy for NL80211_ATTR_STATUS_CODE
sysrq: Restore original console_loglevel when sysrq disabled
sysrq: Remove duplicated sysrq message
net: fib_rules: Correctly set table field when table number exceeds 8 bits
net: phy: restore mdio regs in the iproc mdio driver
nfc: pn544: Fix occasional HW initialization failure
sctp: move the format error check out of __sctp_sf_do_9_1_abort
ipv6: Fix nlmsg_flags when splitting a multipath route
ipv6: Fix route replacement with dev-only route
qede: Fix race between rdma destroy workqueue and link change event
net: sched: correct flower port blocking
ext4: potential crash on allocation error in ext4_alloc_flex_bg_array()
audit: fix error handling in audit_data_to_entry()
ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro
ACPI: watchdog: Fix gas->access_width usage
KVM: VMX: check descriptor table exits on instruction emulation
HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock
HID: core: fix off-by-one memset in hid_report_raw_event()
HID: core: increase HID report buffer size to 8KiB
tracing: Disable trace_printk() on post poned tests
Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs"
HID: hiddev: Fix race in in hiddev_disconnect()
MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()'
i2c: altera: Fix potential integer overflow
i2c: jz4780: silence log flood on txabrt
drm/i915/gvt: Separate display reset from ALL_ENGINES reset
usb: charger: assign specific number for enum value
ecryptfs: Fix up bad backport of fe2e082f5da5b4a0a92ae32978f81507ef37ec66
net: netlink: cap max groups which will be considered in netlink_bind()
net: atlantic: fix potential error handling
net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE
namei: only return -ECHILD from follow_dotdot_rcu()
mwifiex: drop most magic numbers from mwifiex_process_tdls_action_frame()
KVM: SVM: Override default MMIO mask if memory encryption is enabled
KVM: Check for a bad hva before dropping into the ghc slow path
drivers: net: xgene: Fix the order of the arguments of 'alloc_etherdev_mqs()'
kprobes: Set unoptimized flag after unoptimizing code
perf hists browser: Restore ESC as "Zoom out" of DSO/thread/etc
mm/huge_memory.c: use head to check huge zero page
mm, thp: fix defrag setting if newline is not used
audit: always check the netlink payload length in audit_receive_msg()
vhost: Check docket sk_family instead of call getname
EDAC/amd64: Set grain per DIMM
net: dsa: bcm_sf2: Forcibly configure IMP port for 1Gb/sec
RDMA/core: Fix pkey and port assignment in get_new_pps
RDMA/core: Fix use of logical OR in get_new_pps
kprobes: Fix optimize_kprobe()/unoptimize_kprobe() cancellation logic
serial: ar933x_uart: set UART_CS_{RX,TX}_READY_ORIDE
selftests: fix too long argument
usb: gadget: composite: Support more than 500mA MaxPower
usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
usb: gadget: serial: fix Tx stall after buffer overflow
drm/msm/mdp5: rate limit pp done timeout warnings
drm: msm: Fix return type of dsi_mgr_connector_mode_valid for kCFI
drm/msm/dsi: save pll 

[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display

[Bump]

Has anybody checked how other distros operate this? Maybe Debian/Kali?

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

Title:
  systemd-backlight does not save and restore brightness for nvidia
  display

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers
  on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5%
  steps. However, after a reboot or after a shutdown, brightness level
  reverts to 100%. Please fix to is "remembers" the current brightness
  value at shutdown time, like in does Windows.

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

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

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i am using dell laptop touchpad is not working on ubuntu but it was
  perfect on the window please solve the bug and help me to use my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   omkar  2437 F...m pulseaudio
   /dev/snd/controlC1:  omkar  2437 F pulseaudio
   /dev/snd/controlC0:  omkar  2437 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 23:02:53 2020
  HibernationDevice: RESUME=UUID=a4724777-054d-4174-8229-3acb0ac60ff1
  InstallationDate: Installed on 2019-10-11 (162 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=7263bc49-4bf4-4e80-9cc8-ef8379d218b5 ro quiet splash 
ivrs_ioapic[32]=00:14.0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-11-25 (116 days ago)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RG2FR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/18/2018:svnDellInc.:pnInspiron3543:pvrA10:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1868397] Re: touchpad not working

[Mark Morlino]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  New

Bug description:
  i am using dell laptop touchpad is not working on ubuntu but it was
  perfect on the window please solve the bug and help me to use my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   omkar  2437 F...m pulseaudio
   /dev/snd/controlC1:  omkar  2437 F pulseaudio
   /dev/snd/controlC0:  omkar  2437 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 23:02:53 2020
  HibernationDevice: RESUME=UUID=a4724777-054d-4174-8229-3acb0ac60ff1
  InstallationDate: Installed on 2019-10-11 (162 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=7263bc49-4bf4-4e80-9cc8-ef8379d218b5 ro quiet splash 
ivrs_ioapic[32]=00:14.0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-11-25 (116 days ago)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RG2FR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/18/2018:svnDellInc.:pnInspiron3543:pvrA10:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Colin Ian King]

Thanks for the useful feedback, I'll enable some finer grained metrics
tomorrow and see if I can pin point those longer delays.

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

Title:
  multiple long delays during kernel and userspace boot

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel messages: 2.0
  # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
  # [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 
MB/s
  #
  # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in 
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD 
-IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
  #
  # [   13.773554] localhost.localdomain sh[871]: + exit 0
  # [   21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 
'UDF Volume', timestamp 2019/12/17 00:00 (1000)
  #
  # [   24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time 
server 91.189.89.198:123 (ntp.ubuntu.com).
  # [   29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 
19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 
+. Up 25.20 seconds.

  The easiest comparison kernel-side is the systemd-analyze value:

  Grepping in the debug data:

  
  % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log 
| cut -d" " -f 7-
  Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
  Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
  Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
  Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
  Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
  Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
  Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
  Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
  Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
  Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

  foofoo % grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7-
  Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
  Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
  Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
  Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
  Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s.
  Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s.
  Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s.
  Startup finished in 7.429s (kernel) + 36.177s (userspace) = 43.606s.
  Startup finished in 9.075s (kernel) + 32.494s (userspace) = 41.570s.
  Startup finished in 7.281s (kernel) + 32.732s (userspace) = 40.013s.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1027-azure 5.0.0-1027.29~18.04.1
  ProcVersionSignature: User Name 5.0.0-1027.29~18.04.1-azure 5.0.21
  Uname: Linux 5.0.0-1027-azure x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: 

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Ryan Harper]

Ah, from the journal.log:

Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1008-azure
root=PARTUUID=1261a2c6-48ca-43ee-9b70-197f5b89b82c ro console=tty1
console=ttyS0 earlyprintk=ttyS0 panic=-1

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

Title:
  multiple long delays during kernel and userspace boot

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel messages: 2.0
  # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
  # [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 
MB/s
  #
  # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in 
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD 
-IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
  #
  # [   13.773554] localhost.localdomain sh[871]: + exit 0
  # [   21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 
'UDF Volume', timestamp 2019/12/17 00:00 (1000)
  #
  # [   24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time 
server 91.189.89.198:123 (ntp.ubuntu.com).
  # [   29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 
19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 
+. Up 25.20 seconds.

  The easiest comparison kernel-side is the systemd-analyze value:

  Grepping in the debug data:

  
  % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log 
| cut -d" " -f 7-
  Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
  Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
  Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
  Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
  Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
  Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
  Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
  Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
  Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
  Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

  foofoo % grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7-
  Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
  Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
  Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
  Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
  Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s.
  Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s.
  Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s.
  Startup finished in 7.429s (kernel) + 36.177s (userspace) = 43.606s.
  Startup finished in 9.075s (kernel) + 32.494s (userspace) = 41.570s.
  Startup finished in 7.281s (kernel) + 32.732s (userspace) = 40.013s.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1027-azure 5.0.0-1027.29~18.04.1
  ProcVersionSignature: User Name 5.0.0-1027.29~18.04.1-azure 5.0.21
  Uname: Linux 

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Ryan Harper]

None of the VMs will be using spinning disks, it's all SSD; and virtual
disks anyhow.

I would not expect much timing difference on virtual hardware; there
aren't real device or pci timing delays; though the kernel may wait for
them; however, it should be consistent.

In terms of the things that caught my eye:

# HotSpot maximum delta between kernel messages: 2.0
# [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
# [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 MB/s

# [ 5.159028] localhost.localdomain kernel: EXT4-fs (sda1): mounted filesystem 
with ordered data mode. Opts: (null)
# [ 8.385284] localhost.localdomain systemd[1]: systemd 237 running in 


[1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
 * this clock source is slow. 
Consider trying other clock sources
[3.545974] localhost.localdomain kernel: Unstable clock detected, switching 
default tracing clock to "global"
 If you want to keep using the 
local clock, then add:
   "trace_clock=local"   
 on the kernel command line


Now, I owe you a /proc/cmdline, I'll get to that.


I looked over the spreadsheet; and while they are consistent with in each type 
(no template, after templating) the total time in kernel is double in 
after-templating (according to systemd-analyze);  so I'd like to understand why 
that's the case.

% grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log | 
cut -d" " -f 7- 
Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

vs

% grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7- 
Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s.
Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s.
Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s.
Startup finished in 7.429s (kernel) + 36.177s (userspace) = 43.606s.
Startup finished in 9.075s (kernel) + 32.494s (userspace) = 41.570s.
Startup finished in 7.281s (kernel) + 32.732s (userspace) = 40.013s.

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

Title:
  multiple long delays during kernel and userspace boot

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel 

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Frank Heimes]

When I earlier looked-up the commits listed here in the bug description via 
their 'commit name', I found some but not all of them. (I prefer looking up 
commits via it's name rather than via their hash, since depending on the git 
tree they come from [upstream, ubuntu, etc.] hashes can be different).
It turned out that some of the descriptions next to the hashes above are the 
xact descriptions, other are not.

Doing another lookup in the focal master tree - now with the exact names - I 
was able to find the additional 5 commits:
$ git log --oneline --grep "ima: add support for arch specific policies"
6191706246de ima: add support for arch specific policies
$ git log --oneline --grep "ima: Implement support for module-style appended 
signatures"
39b07096364a ima: Implement support for module-style appended signatures
$ git log --oneline --grep "tpm: enhance TPM 2.0 PCR extend to support multiple 
banks"
c1f92b4b04ad tpm: enhance TPM 2.0 PCR extend to support multiple banks
$ git log --oneline --grep "tpm: add securityfs support for TPM 2.0 firmware 
event log"
4d23cc323cdb tpm: add securityfs support for TPM 2.0 firmware event log
$ git log --oneline --grep "powerpc: Enable CONFIG_KEXEC_FILE in powerpc server 
defconfigs."
500c7ab1a9db powerpc: Enable CONFIG_KEXEC_FILE in powerpc server defconfigs.

May I ask about the status of the two commits marked at tbd?
Are they ready, ideally already upstream / in 'linux-next'?

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1865293] Re: ryzen 5 3600x soft lockups

[Martin Gerdzhev]

It keeps happening on a daily basis. Even several times a day. Either a
full lock-up where the mouse can't be moved, or sometimes the mouse can
be moved, but otherwise it is completely frozen.

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

Title:
  ryzen 5 3600x soft lockups

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using ubuntu 19.10 with a ryzen 5 3600x cpu and am getting soft lockups 
with the machine unresponsive almost on a daily basis. The only fix is a hard 
reset.
  I have the latest amd64-microcode installed - 
3.20191021.1+really3.20181128.1ubuntu2, but still continues to happen.

  
  Description:  Ubuntu 19.10
  Release:  19.10

  using kernel: 
  5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2483 F pulseaudio
   /dev/snd/controlC0:  martin 2483 F pulseaudio
   /dev/snd/controlC2:  martin 2483 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-08 (87 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro acpi_enforce_resources=lax 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display

[Launchpad Bug Tracker]

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

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  systemd-backlight does not save and restore brightness for nvidia
  display

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers
  on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5%
  steps. However, after a reboot or after a shutdown, brightness level
  reverts to 100%. Please fix to is "remembers" the current brightness
  value at shutdown time, like in does Windows.

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

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

[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Confirmed

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

Title:
  systemd-backlight does not save and restore brightness for nvidia
  display

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers
  on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5%
  steps. However, after a reboot or after a shutdown, brightness level
  reverts to 100%. Please fix to is "remembers" the current brightness
  value at shutdown time, like in does Windows.

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

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

[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-backlight does not save and restore brightness for nvidia
  display

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers
  on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5%
  steps. However, after a reboot or after a shutdown, brightness level
  reverts to 100%. Please fix to is "remembers" the current brightness
  value at shutdown time, like in does Windows.

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

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

[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Confirmed

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

Title:
  systemd-backlight does not save and restore brightness for nvidia
  display

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers
  on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5%
  steps. However, after a reboot or after a shutdown, brightness level
  reverts to 100%. Please fix to is "remembers" the current brightness
  value at shutdown time, like in does Windows.

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

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

[Kernel-packages] [Bug 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display

[D]

And it's an issue with 20.04 daily builds.
Hardware is Lenovo P73 with NVIDIA RTX-5000 Q-Max.

So how can the driver be made to register the backlight device?

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

Title:
  systemd-backlight does not save and restore brightness for nvidia
  display

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers
  on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5%
  steps. However, after a reboot or after a shutdown, brightness level
  reverts to 100%. Please fix to is "remembers" the current brightness
  value at shutdown time, like in does Windows.

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

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

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

Title:
  Wifi fails to work with newer kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot Ubuntu normally with the most recent kernel image WiFi will not 
work, I will get this message, Network activation error,so I boot up Ubuntu to 
other generic kernels, 5.4.0-18 and 5.4.0-18-generic and I still receive the 
same message, finally I boot to kernel 5.2.0-15-generic and the WiFi works 
perfectly fine!
  see also bug #1867797 for info of when i booted into the 5.4.0 kernels
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   1740 F pulseaudio
   /dev/snd/controlC0:  administrator   1740 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-05 (285 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-15-generic N/A
   linux-backports-modules-5.2.0-15-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.2.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867684] Re: Wifi fails to work with newer kernels

[Ethan Lin]

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1867684

Title:
  Wifi fails to work with newer kernels

Status in linux package in Ubuntu:
  New

Bug description:
  When I boot Ubuntu normally with the most recent kernel image WiFi will not 
work, I will get this message, Network activation error,so I boot up Ubuntu to 
other generic kernels, 5.4.0-18 and 5.4.0-18-generic and I still receive the 
same message, finally I boot to kernel 5.2.0-15-generic and the WiFi works 
perfectly fine!
  see also bug #1867797 for info of when i booted into the 5.4.0 kernels
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   1740 F pulseaudio
   /dev/snd/controlC0:  administrator   1740 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-05 (285 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-15-generic N/A
   linux-backports-modules-5.2.0-15-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.2.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

On Raspbian the output of "iw reg get" matches what I saw after setting
"iw reg set US".

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

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

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

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

Here's the "iw reg get" output from a 20.04 laptop.

[ 10:58AM 10014 ]  [ bdmurray@speedy:~ ]
 $ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)

phy#0 (self-managed)
country US: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, 
NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, 
NO-160MHZ
(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5570 - 5590 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5590 - 5610 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5610 - 5630 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5630 - 5650 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, 
NO-160MHZ, PASSIVE-SCAN
(5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, 
NO-160MHZ, PASSIVE-SCAN
(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, 
NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and 

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

I managed to get my RPi4 to connect to the 802.11ac access point by
setting the regulatory domain to US - "iw reg set US". Here's a before
and after output of "iw reg get".

ubuntu@ubuntu:~$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)

ubuntu@ubuntu:~$ iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

However, this is much different than my 20.04 laptop running Ubuntu.

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

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

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

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

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

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

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

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

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

Title:
  Freeze next suspend / resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can see the screen, but everything is frozen.
  Thanks !

  Details:

  System:Host: vivi-HP-EliteBook-6930p Kernel: 4.15.0-91-generic x86_64 
bits: 64 compiler: gcc 
 v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: 
Linux Mint 19.3 Tricia 
 base: Ubuntu 18.04 bionic 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 6930p 
v: F.1A 
 serial:  Chassis: type: 10 serial:  
 Mobo: Hewlett-Packard model: 30DB v: KBC Version 87.2B serial: 
 
 BIOS: Hewlett-Packard v: 68PCU Ver. F.1A date: 12/13/2010 
  CPU:   Topology: Dual Core model: Intel Core2 Duo P8600 bits: 64 type: 
MCP arch: Penryn rev: A 
 L2 cache: 3072 KiB 
 flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 9576 
 Speed: 1054 MHz min/max: 800/2401 MHz Core speeds (MHz): 1: 1318 
2: 1332 
  Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: 
Hewlett-Packard 
 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 
 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1280x800~60Hz 
 OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 
19.2.8 
 direct render: Yes 
  Audio: Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel 
 bus ID: 00:1b.0 chip ID: 8086:293e 
 Sound Server: ALSA v: k4.15.0-91-generic 
  Network:   Device-1: Intel 82567LM Gigabit Network vendor: Hewlett-Packard 
driver: e1000e 
 v: 3.2.6-k port: 70e0 bus ID: 00:19.0 chip ID: 8086:10f5 
 IF: enp0s25 state: down mac:  
 Device-2: Intel PRO/Wireless 5100 AGN [Shiloh] Network driver: 
iwlwifi v: kernel 
 port: 7000 bus ID: 02:00.0 chip ID: 8086:4237 
 IF: wls1 state: up mac:  
  Drives:Local Storage: total: 149.05 GiB used: 54.45 GiB (36.5%) 
 ID-1: /dev/sda vendor: Seagate model: ST9160411AS size: 149.05 GiB 
speed: 3.0 Gb/s 
 serial:  
  Partition: ID-1: / size: 141.93 GiB used: 54.45 GiB (38.4%) fs: ext4 dev: 
/dev/sda1 
  Sensors:   System Temperatures: cpu: 35.0 C mobo: 24.8 C 
 Fan Speeds (RPM): N/A 
  Repos: Active apt repos in: /etc/apt/sources.list 
 1: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main
 2: deb https: 
//download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/ ./
 Active apt repos in: 
/etc/apt/sources.list.d/fingerprint-fingerprint-gui-bionic.list 
 1: deb http: 
//ppa.launchpad.net/fingerprint/fingerprint-gui/ubuntu bionic main
 Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable 
main
 No active apt repos in: 
/etc/apt/sources.list.d/jonathonf-python-3_5-bionic.list 
 Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
 1: deb http: //mint.remi.lu tricia main upstream import backport
 2: deb http: //fr.archive.ubuntu.com/ubuntu bionic main restricted 
universe multiverse
 3: deb http: //fr.archive.ubuntu.com/ubuntu bionic-updates main 
restricted universe multiverse
 4: deb http: //fr.archive.ubuntu.com/ubuntu bionic-backports main 
restricted universe multiverse
 5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main 
restricted universe multiverse
 6: deb http: //archive.canonical.com/ubuntu/ bionic partner
 Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
 1: deb [arch=amd64] https: //repo.skype.com/deb stable main
 Active apt repos in: 
/etc/apt/sources.list.d/vincent-vandevyvre-vvv-bionic.list 
 1: deb http: //ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu 
bionic main
  Info:  Processes: 197 Uptime: 8m Memory: 3.69 GiB used: 1.45 GiB (39.3%) 
Init: 

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Colin Ian King]

Some of the early kernel boot time variations occur when detecting and
spinning up devices sda and sbd and reading the partition information.
Given this is probably spinny disc media, one would expect variations of
this kind in early boot.

The other variations I can see are also due to probing of hardware,
which again is probably expected.  I'm finding it hard to see anything
really too problematic with the kernel side boot timings given that we
are dealing with H/W style variations in the boot.  If there are issues
that are glaring and I'm missing it, can you point me to them?

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

Title:
  multiple long delays during kernel and userspace boot

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel messages: 2.0
  # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
  # [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 
MB/s
  #
  # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in 
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD 
-IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
  #
  # [   13.773554] localhost.localdomain sh[871]: + exit 0
  # [   21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 
'UDF Volume', timestamp 2019/12/17 00:00 (1000)
  #
  # [   24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time 
server 91.189.89.198:123 (ntp.ubuntu.com).
  # [   29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 
19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 
+. Up 25.20 seconds.

  The easiest comparison kernel-side is the systemd-analyze value:

  Grepping in the debug data:

  
  % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log 
| cut -d" " -f 7-
  Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
  Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
  Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
  Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
  Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
  Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
  Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
  Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
  Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
  Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

  foofoo % grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7-
  Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
  Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
  Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
  Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
  Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s.
  Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s.
  Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s.
  Startup finished in 

[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Tags removed: block-proposed-trusty

** Tags removed: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Holding before Promote to Updates
- phase-changed: Thursday, 19. March 2020 22:06 UTC
+ phase: Ready for Promote to Updates
+ phase-changed: Monday, 23. March 2020 17:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Holding -- master bug not ready for release
+   promote-to-updates: Pending -- ready to copy
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1867860
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Updates
  phase-changed: Monday, 23. March 2020 17:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- ready to copy
  variant: debs

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

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

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Colin Ian King]

And also data for bug-bionic-baseline-no-templating-Standard-DS2-v2.csv
attached

** Attachment added: "Results-baseline-no-templating-Standard-DS2-v2.ods"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/1858495/+attachment/5340630/+files/Results-baseline-no-templating-Standard-DS2-v2.ods

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

Title:
  multiple long delays during kernel and userspace boot

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel messages: 2.0
  # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
  # [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 
MB/s
  #
  # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in 
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD 
-IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
  #
  # [   13.773554] localhost.localdomain sh[871]: + exit 0
  # [   21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 
'UDF Volume', timestamp 2019/12/17 00:00 (1000)
  #
  # [   24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time 
server 91.189.89.198:123 (ntp.ubuntu.com).
  # [   29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 
19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 
+. Up 25.20 seconds.

  The easiest comparison kernel-side is the systemd-analyze value:

  Grepping in the debug data:

  
  % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log 
| cut -d" " -f 7-
  Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
  Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
  Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
  Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
  Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
  Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
  Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
  Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
  Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
  Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

  foofoo % grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7-
  Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
  Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
  Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
  Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
  Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s.
  Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s.
  Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s.
  Startup finished in 7.429s (kernel) + 36.177s (userspace) = 43.606s.
  Startup finished in 9.075s (kernel) + 32.494s (userspace) = 41.570s.
  Startup finished in 7.281s (kernel) + 32.732s (userspace) = 40.013s.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: 

[Kernel-packages] [Bug 1868600] [NEW] Freeze next suspend / resume

[Bovée]

Public bug reported:

I can see the screen, but everything is frozen.
Thanks !

Details:

System:Host: vivi-HP-EliteBook-6930p Kernel: 4.15.0-91-generic x86_64 bits: 
64 compiler: gcc 
   v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: 
Linux Mint 19.3 Tricia 
   base: Ubuntu 18.04 bionic 
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 6930p v: 
F.1A 
   serial:  Chassis: type: 10 serial:  
   Mobo: Hewlett-Packard model: 30DB v: KBC Version 87.2B serial: 
 
   BIOS: Hewlett-Packard v: 68PCU Ver. F.1A date: 12/13/2010 
CPU:   Topology: Dual Core model: Intel Core2 Duo P8600 bits: 64 type: MCP 
arch: Penryn rev: A 
   L2 cache: 3072 KiB 
   flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 9576 
   Speed: 1054 MHz min/max: 800/2401 MHz Core speeds (MHz): 1: 1318 2: 
1332 
Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: 
Hewlett-Packard 
   driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 
   Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: 
fbdev,vesa 
   resolution: 1280x800~60Hz 
   OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 
19.2.8 
   direct render: Yes 
Audio: Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel 
   bus ID: 00:1b.0 chip ID: 8086:293e 
   Sound Server: ALSA v: k4.15.0-91-generic 
Network:   Device-1: Intel 82567LM Gigabit Network vendor: Hewlett-Packard 
driver: e1000e 
   v: 3.2.6-k port: 70e0 bus ID: 00:19.0 chip ID: 8086:10f5 
   IF: enp0s25 state: down mac:  
   Device-2: Intel PRO/Wireless 5100 AGN [Shiloh] Network driver: 
iwlwifi v: kernel 
   port: 7000 bus ID: 02:00.0 chip ID: 8086:4237 
   IF: wls1 state: up mac:  
Drives:Local Storage: total: 149.05 GiB used: 54.45 GiB (36.5%) 
   ID-1: /dev/sda vendor: Seagate model: ST9160411AS size: 149.05 GiB 
speed: 3.0 Gb/s 
   serial:  
Partition: ID-1: / size: 141.93 GiB used: 54.45 GiB (38.4%) fs: ext4 dev: 
/dev/sda1 
Sensors:   System Temperatures: cpu: 35.0 C mobo: 24.8 C 
   Fan Speeds (RPM): N/A 
Repos: Active apt repos in: /etc/apt/sources.list 
   1: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main
   2: deb https: 
//download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/ ./
   Active apt repos in: 
/etc/apt/sources.list.d/fingerprint-fingerprint-gui-bionic.list 
   1: deb http: //ppa.launchpad.net/fingerprint/fingerprint-gui/ubuntu 
bionic main
   Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
   1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable 
main
   No active apt repos in: 
/etc/apt/sources.list.d/jonathonf-python-3_5-bionic.list 
   Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
   1: deb http: //mint.remi.lu tricia main upstream import backport
   2: deb http: //fr.archive.ubuntu.com/ubuntu bionic main restricted 
universe multiverse
   3: deb http: //fr.archive.ubuntu.com/ubuntu bionic-updates main 
restricted universe multiverse
   4: deb http: //fr.archive.ubuntu.com/ubuntu bionic-backports main 
restricted universe multiverse
   5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main 
restricted universe multiverse
   6: deb http: //archive.canonical.com/ubuntu/ bionic partner
   Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
   1: deb [arch=amd64] https: //repo.skype.com/deb stable main
   Active apt repos in: 
/etc/apt/sources.list.d/vincent-vandevyvre-vvv-bionic.list 
   1: deb http: //ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu 
bionic main
Info:  Processes: 197 Uptime: 8m Memory: 3.69 GiB used: 1.45 GiB (39.3%) 
Init: systemd v: 237 
   runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 
client inxi: 3.0.32

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

Title:
  Freeze next suspend / resume

Status in linux package in Ubuntu:
  New

Bug description:
  I can see the screen, but everything is frozen.
  Thanks !

  Details:

  System:Host: vivi-HP-EliteBook-6930p Kernel: 4.15.0-91-generic x86_64 
bits: 64 compiler: gcc 
 v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: 
Linux Mint 19.3 Tricia 
 base: Ubuntu 18.04 bionic 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 6930p 
v: F.1A 
 serial:  Chassis: type: 10 serial:  
 Mobo: Hewlett-Packard model: 30DB v: KBC Version 87.2B serial: 
 
  

[Kernel-packages] [Bug 1864041] Please test proposed package

[Łukasz Zemczak]

Hello Francis, or anyone else affected,

Accepted ec2-hibinit-agent into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ec2
-hibinit-agent/1.0.0-0ubuntu4~18.04.4 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Committed
Status in linux-aws source package in Eoan:
  New
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: 

[Kernel-packages] [Bug 1858495] Re: multiple long delays during kernel and userspace boot

[Colin Ian King]

Hi Ryan,

I analysed the data from comment #6 using the journal.log from bug-
bionic-baseline-after-templating-Standard-DS2-v2 and collated some
notable places in the boot process and compared boots 1 through to 10.
Attached are the results as a LibreOffice Calc spread sheet.  The data
shows a little bit of timing variance (which is not surprising) but on
the whole the data looks very similar from boot to boot.  So I can't see
what's particularly wrong with the boot timings in that scenario.  Any
comments on that?

Data: see attached.

** Attachment added: "LibreOffice |Calc spread sheet of boot timings from 
provided data in comment #6"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-azure/+bug/1858495/+attachment/5340629/+files/Results-templating-Standard-DS2-v2.ods

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

Title:
  multiple long delays during kernel and userspace boot

Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  Booting some Bionic instances in Azure (gen1 machines), I see some
  large delays during kernel/userspace boot that it would be good to
  understand what's going on.  Additionally, there areas during boot
  that see delays is different for an image that's been created from a
  template vs. stock images.

  I'm attaching some data, 10 runs of the same image in a scaling set
  that run the initial boot.  Processing the journal output, looking at
  delays of over 2.0 shows some concern.

  
  [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the 
chipset. Due to workarounds for a bug,
   * this clock source is slow. 
Consider trying other clock sources
  [3.545974] localhost.localdomain kernel: Unstable clock detected, 
switching default tracing clock to "global"
   If you want to keep using the 
local clock, then add:
 "trace_clock=local"   
   on the kernel command line  
  [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  [   15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. 
Opts: discard

  
  After capturing bionic image as a template, and creating a new VM, we see new 
hot spots we didn't see before.

  
  # HotSpot maximum delta between kernel messages: 2.0
  # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization 
enabled
  # [5.919313] localhost.localdomain kernel: raid6: avx2x4   gen() 21512 
MB/s
  #
  # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in 
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD 
-IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
  #
  # [   13.773554] localhost.localdomain sh[871]: + exit 0
  # [   21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 
'UDF Volume', timestamp 2019/12/17 00:00 (1000)
  #
  # [   24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time 
server 91.189.89.198:123 (ntp.ubuntu.com).
  # [   29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 
19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 
+. Up 25.20 seconds.

  The easiest comparison kernel-side is the systemd-analyze value:

  Grepping in the debug data:

  
  % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log 
| cut -d" " -f 7-
  Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s.
  Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s.
  Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s.
  Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s.
  Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s.
  Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s.
  Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s.
  Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s.
  Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s.
  Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s.

  foofoo % grep "Startup finished.*kernel" 
bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7-
  Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s.
  Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s.
  Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s.
  Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s.
  Startup finished in 8.426s 

[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

[Łukasz Zemczak]

Hello Francis, or anyone else affected,

Accepted ec2-hibinit-agent into eoan-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ec2
-hibinit-agent/1.0.0-0ubuntu7.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: ec2-hibinit-agent (Ubuntu Eoan)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-eoan

** Changed in: ec2-hibinit-agent (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  Fix Committed
Status in linux-aws source package in Eoan:
  New
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.

  [Regression Potential]

  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.

  The workaround also adds a 2 second delay before reloading the modules
  to let things settle a bit after resuming. The 2 seconds is very short
  compared to the overall time needed resuming an instance.

  [Original Bug Text]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  A workaround is to build the xen_netfront module separately and
  restart the module and networking during the resume handler. For
  example:

  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd

  With this workaround in place, the unresponsive issue is no longer
  observed.

  To reproduce this problem:

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to 

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

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

Title:
  VFS cannot open root device "sdc"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  vfs: cannot open root device "sdc" or unknown-block(0,0): error -6
  kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

  
  this happened after upgrading the linux kernel 5.3.0-40 to 5.3.0-42

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

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

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

[Kevin Adams]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340624/+files/WifiSyslog.txt

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

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868491] RfKill.txt

[Kevin Adams]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1868491/+attachment/5340622/+files/RfKill.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/1868491

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

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

[Kevin Adams]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1868491/+attachment/5340623/+files/UdevDb.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

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

[Kevin Adams]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340613/+files/CurrentDmesg.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

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

[Kevin Adams]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340621/+files/ProcModules.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868491] ProcCpuinfo.txt

[Kevin Adams]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340618/+files/ProcCpuinfo.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/1868491

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868491] Lsusb-t.txt

[Kevin Adams]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340616/+files/Lsusb-t.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

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

[Kevin Adams]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340619/+files/ProcCpuinfoMinimal.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868491] IwConfig.txt

[Kevin Adams]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340614/+files/IwConfig.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/1868491

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

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

[Kevin Adams]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340620/+files/ProcInterrupts.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868491] Lsusb-v.txt

[Kevin Adams]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340617/+files/Lsusb-v.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/1868491

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

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

[Kevin Adams]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1868491/+attachment/5340615/+files/Lspci.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868491] Re: no sound using ubuntu 20.04 on samsung chromebook 3 celes

[Kevin Adams]

apport information

** Tags added: apport-collected

** Description changed:

  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kevin   924 F pulseaudio
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-03-23 (0 days ago)
+ InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: GOOGLE Celes
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-18-generic N/A
+  linux-backports-modules-5.4.0-18-generic  N/A
+  linux-firmware1.187
+ Tags:  focal
+ Uname: Linux 5.4.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 11/09/2018
+ dmi.bios.vendor: coreboot
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: GOOGLE
+ dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
+ dmi.product.family: Intel_Strago
+ dmi.product.name: Celes
+ dmi.product.version: 1.1
+ dmi.sys.vendor: GOOGLE

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1868491/+attachment/5340611/+files/AlsaInfo.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "F

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

[Kevin Adams]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1868491/+attachment/5340612/+files/CRDA.txt

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kevin   924 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-23 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b657 Chicony Electronics Co., Ltd 720p HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Celes
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-18-generic 
root=UUID=f529e9dc-4c58-4c1e-bc08-d8a6d26a14fa ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd11/09/2018:svnGOOGLE:pnCeles:pvr1.1:cvnGOOGLE:ct3:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Celes
  dmi.product.version: 1.1
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1868590] [NEW] VFS cannot open root device "sdc"

[wanderley gregorio barroso]

Public bug reported:

vfs: cannot open root device "sdc" or unknown-block(0,0): error -6
kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


this happened after upgrading the linux kernel 5.3.0-40 to 5.3.0-42

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

Title:
  VFS cannot open root device "sdc"

Status in linux package in Ubuntu:
  New

Bug description:
  vfs: cannot open root device "sdc" or unknown-block(0,0): error -6
  kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

  
  this happened after upgrading the linux kernel 5.3.0-40 to 5.3.0-42

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

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

[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Screen freezes : NULL pointer dereference i915_active_acquire since
  Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

[Balint Reczey]

** Description changed:

  [Impact]
  
  The xen_netfront device is sometimes unresponsive after a hibernate and
  resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance
  families, all of which are xen based, and support hibernation.
  
  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.
  
  [Test Case]
  
  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  
  [Regression Potential]
  
  The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
  the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.
+ 
+ The workaround also adds a 2 second delay before reloading the modules
+ to let things settle a bit after resuming. The 2 seconds is very short
+ compared to the overall time needed resuming an instance.
  
  [Original Bug Text]
  
  The xen_netfront device is sometimes unresponsive after a hibernate and
  resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance
  families, all of which are xen based, and support hibernation.
  
  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.
  
  A workaround is to build the xen_netfront module separately and restart
  the module and networking during the resume handler. For example:
  
  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd
  
  With this workaround in place, the unresponsive issue is no longer
  observed.
  
  To reproduce this problem:
  
  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console

[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+ The xen_netfront device is sometimes unresponsive after a hibernate and
+ resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance
+ families, all of which are xen based, and support hibernation.
+ 
+ When the issue occurrs, the instance is inaccessible without a full
+ restart. Debugging by running a process which outputs regularly to the
+ serial console shows that the instance is still running.
+ 
+ [Test Case]
+ 
+ 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
+ 2) Start a long-running process which generates messages to the serial console
+ 3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
+ 4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
+ 5) The screenshot should continue to show updates even if ssh access is no 
longer working.
+ 
+ [Regression Potential]
+ 
+ The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel 
module before restarting systemd-networkd. If the kernel module is removed (for 
example when hitting LP: #1615381) the module reloading fails and
+ the instance can not restore network connections. This is expected to a be 
very rare situation and the module reload is the best workaround the Kernel 
Team found to mitigate the original issue.
+ 
+ [Original Bug Text]
+ 
  The xen_netfront device is sometimes unresponsive after a hibernate and
  resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance
  families, all of which are xen based, and support hibernation.
  
  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.
  
  A workaround is to build the xen_netfront module separately and restart
  the module and networking during the resume handler. For example:
  
  modprobe -r xen_netfront
  modprobe xen_netfront
  systemctl restart systemd-networkd
  
  With this workaround in place, the unresponsive issue is no longer
  observed.
  
  To reproduce this problem:
  
  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) Suspend and resume the instance, continuing to refresh the console 
screenshot.
  5) The screenshot should continue to show updates even if ssh access is no 
longer working.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-0edf3b95e26a682df
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: m4.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: linux-aws 4.15.0.1058.59
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=screen
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=screen
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21
  Tags:  bionic ec2-images
  Uname: Linux 5.0.0-1025-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True

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

Title:
  xen_netfront devices unresponsive after hibernation/resume

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in ec2-hibinit-agent source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in ec2-hibinit-agent source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New
Status in ec2-hibinit-agent source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  New

Bug description:
  [Impact]

  The xen_netfront device is sometimes unresponsive after a hibernate
  and resume event. This is limited to the c4, c5, m4, m5, r4, r5
  instance families, all of which are xen based, and support
  hibernation.

  When the issue occurrs, the instance is inaccessible without a full
  restart. Debugging by running a process which outputs regularly to the
  serial console shows that the instance is still running.

  [Test Case]

  1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel 
with on-demand hibernation support enabled.
  2) Start a long-running process which generates messages to the serial console
  3) Begin observing these messages on the console (using the AWS UI or CLI  to 
grab a screenshot).
  4) 

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

[ks2k2d]

I support the conclusion by Marcel.
I have HP 450 G6 and brightness up/down generate the same scancode as mic mute.

Also, in dmesg I get:
[6.422405] hp_wmi: query 0x4 returned error 0x5
[6.433681] hp_wmi: query 0x4 returned error 0x5
[6.447825] hp_wmi: query 0xd returned error 0x5
[6.617355] hp_wmi: query 0x1b returned error 0x5

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

Title:
  hp_wmi: query 0xd returned error 0x5

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

Bug description:
  Hello,

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

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

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

[ks2k2d]

Related bug:
https://bugs.launchpad.net/ubuntu/+bug/1841039

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

Title:
  hp_wmi: query 0xd returned error 0x5

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

Bug description:
  Hello,

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

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Kernel-packages] [Bug 1868581] [NEW] [DELL][BIONIC] Freeze after docking station disconnect

[Gregor Vindry]

Public bug reported:

Problem description
---
When I disconnect my Dell Latitude 5501 laptop from its Dell WD19 docking 
station, the screens layout doesn't switch back to single-screen, and the 
system either:

* freezes immediately (desktop background still displayed, but no mouse, no 
keyboard)
* doesn't freeze. In that case, if I open a terminal and sudo poweroff, the 
screen turns black, then the system freezes.

In both cases, the only recovery method consists in a hard reset.

Hardware setup description
--
Laptop is connected to docking station via thunderbolt port. 

The WD19 docking station is connected to 2 external screens via display
ports + USB3 cables (to connect to the embedded USB3 ports on the
screens).

One of the screens is connected to a keyboard and a mouse via USB.

Technical info
--
See attached file kern.log for a disconnect (see at Mar 23 15:35:56).

The problem does not happen on older kernel 4.15.0-1073-oem, so it looks
like a regression introduced between 4.15.0-1074-oem and
4.15.0-1076-oem.

Laptop BIOS version is up-to-date (v1.6.1).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1076-oem 4.15.0-1076.86
ProcVersionSignature: Ubuntu 4.15.0-1076.86-oem 4.15.18
Uname: Linux 4.15.0-1076-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gvindry2492 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 23 15:42:42 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
InstallationDate: Installed on 2019-12-28 (86 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
MachineType: Dell Inc. Latitude 5501
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1076-oem 
root=UUID=d829dfff-8fb3-46f6-8175-92de7a872776 ro mem_sleep_default=deep quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-1076-oem N/A
 linux-backports-modules-4.15.0-1076-oem  N/A
 linux-firmware   1.173.16
SourcePackage: linux-oem
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.1
dmi.board.name: 0Y8H01
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd11/14/2019:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5501
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Relevant kern.log (see Mar 23 15:35:56)"
   https://bugs.launchpad.net/bugs/1868581/+attachment/5340593/+files/kern.log

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

Title:
  [DELL][BIONIC] Freeze after docking station disconnect

Status in linux-oem package in Ubuntu:
  New

Bug description:
  Problem description
  ---
  When I disconnect my Dell Latitude 5501 laptop from its Dell WD19 docking 
station, the screens layout doesn't switch back to single-screen, and the 
system either:

  * freezes immediately (desktop background still displayed, but no mouse, no 
keyboard)
  * doesn't freeze. In that case, if I open a terminal and sudo poweroff, the 
screen turns black, then the system freezes.

  In both cases, the only recovery method consists in a hard reset.

  Hardware setup description
  --
  Laptop is connected to docking station via thunderbolt port. 

  The WD19 docking station is connected to 2 external screens via
  display ports + USB3 cables (to connect to the embedded USB3 ports on
  the screens).

  One of the screens is connected to a keyboard and a mouse via USB.

  Technical info
  --
  See attached file kern.log for a disconnect (see at Mar 23 15:35:56).

  The problem does not happen on older kernel 4.15.0-1073-oem, so it
  looks like a regression introduced between 4.15.0-1074-oem and
  4.15.0-1076-oem.

  Laptop BIOS version is up-to-date (v1.6.1).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1076-oem 4.15.0-1076.86
  ProcVersionSignature: Ubuntu 4.15.0-1076.86-oem 4.15.18
  Uname: Linux 4.15.0-1076-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gvindry2492 F 

[Kernel-packages] [Bug 1868551] Re: Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

[Guy Baconniere]

** Summary changed:

- Dell XPS 13 : Screen freezes and Kernel Oops i915_active_acquire since Linux 
5.4
+ Screen freezes : NULL pointer dereference i915_active_acquire since Linux 5.4

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

Title:
  Screen freezes : NULL pointer dereference i915_active_acquire since
  Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

** Tags added: focal

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

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

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

[Kernel-packages] [Bug 1868491] Re: no sound using ubuntu 20.04 on samsung chromebook 3 celes

[Brian Murray]

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

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

Title:
  no sound using ubuntu 20.04 on samsung chromebook 3 celes

Status in linux package in Ubuntu:
  New

Bug description:
  00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
  00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
  00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
  00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
  00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
  00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
  00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
  02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

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

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

[Kernel-packages] [Bug 1868227] Re: Backport jitter entroy changes?

[Michael Vogt]

Setting to confirmed, this bugreport does not need an apport-collect run
:)

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

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

Title:
  Backport jitter entroy changes?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  One of our Ubuntu Core 16 devices failed to boot after a refresh
  recently [0]. After some debugging it turns out that it hangs in early
  boot because there is not enough entropy available. Snapd is using
  entropy to init it's CRNG and a change in snapd broke the boot.
  However while debugging/fixing this issue I was wondering if it would
  be possible to backport the new jitter entropy patches from kernel 5.4
  [1] to the older LTS kernels.

  Thanks,
   Michael

  
  [0] https://bugs.launchpad.net/plano/+bug/1866940 
  [1] https://lwn.net/Articles/802360/

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

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

[Kernel-packages] [Bug 1860501] Lsusb.txt

[Михаил]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1860501/+attachment/5340551/+files/Lsusb.txt

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

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1868491] [NEW] no sound using ubuntu 20.04 on samsung chromebook 3 celes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 35)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 35)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 35)
00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35)
00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 35)
00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 35)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCU (rev 35)
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

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


** Tags: bot-comment
-- 
no sound using ubuntu 20.04 on samsung chromebook 3 celes
https://bugs.launchpad.net/bugs/1868491
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Михаил]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1860501/+attachment/5340559/+files/UdevDb.txt

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

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

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

[Михаил]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1860501/+attachment/5340550/+files/Lspci.txt

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

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1860501] PulseList.txt

[Михаил]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1860501/+attachment/5340557/+files/PulseList.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/1860501

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1860501] Re: Middle-click button suddenly appears right in the middle of my touchpad

[Михаил]

apport information

** Tags added: apport-collected eoan

** Description changed:

  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.
  
  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.6
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
+  /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-06-28 (269 days ago)
+ InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ MachineType: Acer Aspire V3-551G
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-42-generic N/A
+  linux-backports-modules-5.3.0-42-generic  N/A
+  linux-firmware1.183.4
+ Tags:  eoan
+ Uname: Linux 5.3.0-42-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/24/2012
+ dmi.bios.vendor: Acer
+ dmi.bios.version: V2.02
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: VA50_CM
+ dmi.board.vendor: Acer
+ dmi.board.version: Base Board Version
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Chassis Manufacturer
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
+ dmi.product.family: Aspire
+ dmi.product.name: Aspire V3-551G
+ dmi.product.sku: Q5WV8_0696_V2.02
+ dmi.product.version: V2.02
+ dmi.sys.vendor: Acer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1860501/+attachment/5340546/+files/AlsaInfo.txt

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

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 

[Kernel-packages] [Bug 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

[Seth Forshee]

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

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

Title:
  Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
  output and input, does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 12:00:01 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1860501] ProcCpuinfo.txt

[Михаил]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1860501/+attachment/5340552/+files/ProcCpuinfo.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/1860501

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

[Seth Forshee]

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

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  

[Kernel-packages] [Bug 1860501] Re: Middle-click button suddenly appears right in the middle of my touchpad

[Михаил]

I've fixed it by executing commands

synclient RTCornerButton=0 && synclient RBCornerButton=0
synclient RTCornerButton=1 && synclient RBCornerButton=1

several times after startup, thank you.

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

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

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

[Михаил]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1860501/+attachment/5340556/+files/ProcModules.txt

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

Title:
  Middle-click button suddenly appears right in the middle of my
  touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since one of the last updates, about three days or so, I have got 
middle-click button right in the middle of my touchpad without any ability to 
disable it.
  I use taps for clicks, so it often mix up with regular left-clicks, and it is 
very annoying.

  Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 22 10:15:28 2020
  InstallationDate: Installed on 2019-06-28 (207 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mrrabbit   1411 F pulseaudio
   /dev/snd/controlC0:  mrrabbit   1411 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-28 (269 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V3-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VA50_CM
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire
  dmi.product.name: Aspire V3-551G
  dmi.product.sku: Q5WV8_0696_V2.02
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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