[Kernel-packages] [Bug 1863824] Re: ThinkPad X1 Yoga not deactivating keyboard & trackpad when going on tablet mode

[AaronMa]

Hi Jonas:

The keyboard and touchpad is controlled by BIOS/EC not in kernel drivers.
KB/Touchpad should be disabled when you flap it to tablet mode.

Looks like it is a hw relevant issue.
Could you try Windows10? if it is not disabled on Windows10, please contact 
Lenovo for warranty.

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

Title:
  ThinkPad X1 Yoga not deactivating keyboard & trackpad when going on
  tablet mode

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My 4th gen ThinkPad X1 Yoga is unusable as a tablet because it won't
  deactivate the keyboard and trackpad when I flip it to tablet mode.
  It's also the same when I try it on Kubuntu 20.04.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.18.0
  KDE Frameworks Version: 5.67.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-29-generic
  OS Type: 64-bit
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 15.3 GiB of RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: kubuntu-desktop 1.387
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 18 20:33:35 2020
  InstallationDate: Installed on 2020-01-19 (30 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: kubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (29 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  Package: linux-firmware 1.186
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamiyuki   3578 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-19 (69 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  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: Upgraded to focal on 2020-03-21 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  taliara69   1813 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: LENOVO 20SA0002US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=a29e06a9-716d-40d8-b26c-289898a3681d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  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

[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

[Sebastien Bacher]

Could try to install the 19.10's bluez version (just download the debs
and dpkg -i them) and see if that makes a difference?

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- Pa

[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD

[You-Sheng Yang]

Another round sent to upstream in
https://patchwork.freedesktop.org/series/75345/, but it fails the build
when CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not enabled.

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

Title:
  [ICL] TC port in legacy/static mode can't be detected due TCCOLD

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

Bug description:
  When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port
  can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected"

  The issue doesn't happen when SoC is not in PC10.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 5.6.0-050600rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1485 F pulseaudio
u  2075 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Vostro 14 5401
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 
root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M
  ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1043-oem-osp1 N/A
   linux-backports-modules-5.0.0-1043-oem-osp1  N/A
   linux-firmware   1.173.16
  Tags:  bionic
  Uname: Linux 5.0.0-1043-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 89.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14 5401
  dmi.product.sku: 09EA
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1869993] [NEW] Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes entire system

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have the latest updates. I have noticed today that plugging or
unplugging a usb device while the computer is on freezes the whole
computer, keyboard/mouse are completly unresponsive.

While hunting for answers as to why this occurs I stumbled upon my dmesg
log stating

[   13.356149] vboxdrv: module verification failed: signature and/or
required key missing - tainting kernel


and

[15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
[15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
[15265.066206] ata3: SError: { Handshk }


and

[15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

Hope this helps.

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


** Tags: bot-comment
-- 
Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes entire 
system
https://bugs.launchpad.net/bugs/1869993
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 1824136] Re: ubuntu_k8s_unit_tests failed with GCP

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  ubuntu_k8s_unit_tests failed with GCP

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-signed-gcp package in Ubuntu:
  New

Bug description:
  There are 3 failures found on Cosmic GCP (n1-highcpu-16)

  * k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
  * k8s.io/kubernetes/pkg/master
  * k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy 
[build failed]

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

  Error messages:

  * k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler

   --- FAIL: TestUpdateNodeWithMultiplePods (2.56s)
   taint_manager_test.go:486: Starting testcase "Pods with different toleration 
times are evicted appropriately"
   taint_manager_test.go:512: Sleeping for 499.999448ms
   taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
   taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
   taint_manager_test.go:512: Sleeping for 594.563805ms
   taint_manager_test.go:532: Failed to deleted pod pod2 after 0
   taint_manager_test.go:486: Starting testcase "Evict all pods not matching 
all taints instantly"
   taint_manager_test.go:512: Sleeping for 499.999844ms
   taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
   taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
   taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
   taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
   FAIL
   FAIL   k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
35.544s

  * k8s.io/kubernetes/pkg/master
   2019-03-21 16:02:16.793715 I | integration: launching 2444030890339279063 
(unix://localhost:24440308903392790630)
   2019-03-21 16:02:16.798460 I | etcdserver: name = 2444030890339279063
   2019-03-21 16:02:16.798550 I | etcdserver: data dir = /tmp/etcd396328703
   2019-03-21 16:02:16.798566 I | etcdserver: member dir = 
/tmp/etcd396328703/member
   2019-03-21 16:02:16.798576 I | etcdserver: heartbeat = 10ms
   2019-03-21 16:02:16.798585 I | etcdserver: election = 100ms
   2019-03-21 16:02:16.798594 I | etcdserver: snapshot count = 0
   2019-03-21 16:02:16.798635 I | etcdserver: advertise client URLs = 
unix://127.0.0.1:2100211086
   2019-03-21 16:02:16.798657 I | etcdserver: initial advertise peer URLs = 
unix://127.0.0.1:2100111086
   2019-03-21 16:02:16.798676 I | etcdserver: initial cluster = 
2444030890339279063=unix://127.0.0.1:2100111086
   2019-03-21 16:02:16.804030 I | etcdserver: starting member d951fd13cdcf6e11 
in cluster b8d26aa038f828d
   2019-03-21 16:02:16.804137 I | raft: d951fd13cdcf6e11 became follower at 
term 0
   2019-03-21 16:02:16.804164 I | raft: newRaft d951fd13cdcf6e11 [peers: [], 
term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
   2019-03-21 16:02:16.804206 I | raft: d951fd13cdcf6e11 became follower at 
term 1
   2019-03-21 16:02:16.818807 W | auth: simple token is not cryptographically 
signed
   2019-03-21 16:02:16.822703 I | etcdserver: set snapshot count to default 
10
   2019-03-21 16:02:16.822805 I | etcdserver: starting server... [version: 
3.2.13, cluster version: to_be_decided]
   2019-03-21 16:02:16.823182 I | integration: launched 2444030890339279063 
(unix://localhost:24440308903392790630)
   2019-03-21 16:02:16.825229 I | etcdserver/membership: added member 
d951fd13cdcf6e11 [unix://127.0.0.1:2100111086] to cluster b8d26aa038f828d
   2019-03-21 16:02:16.885057 I | raft: d951fd13cdcf6e11 is starting a new 
election at term 1
   2019-03-21 16:02:16.885151 I | raft: d951fd13cdcf6e11 became candidate at 
term 2
   2019-03-21 16:02:16.885168 I | raft: d951fd13cdcf6e11 received MsgVoteResp 
from d951fd13cdcf6e11 at term 2
   2019-03-21 16:02:16.885180 I | raft: d951fd13cdcf6e11 became leader at term 2
   2019-03-21 16:02:16.885187 I | raft: raft.node: d951fd13cdcf6e11 elected 
leader d951fd13cdcf6e11 at term 2
   2019-03-21 16:02:16.885759 I | etcdserver: setting up the initial cluster 
version to 3.2
   2019-03-21 16:02:16.886707 N | etcdserver/membership: set the initial 
cluster version to 3.2
   2019-03-21 16:02:16.886797 I | etcdserver/api: enabled capabilities for 
version 3.2
   2019-03-21 16:02:16.886857 I | etcdserver: published 
{Name:2444030890339279063 ClientURLs:[unix://127.0.0.1:2100211086]} to cluster 
b8d26aa038f828d
   [restful] 2019/03/

[Kernel-packages] [Bug 1869993] Re: Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes entire system

[Juhani Numminen]

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

Title:
  Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes
  entire system

Status in linux package in Ubuntu:
  New

Bug description:
  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.

  While hunting for answers as to why this occurs I stumbled upon my
  dmesg log stating

  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel

  
  and

  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }

  
  and

  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

  Hope this helps.

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

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

[Kernel-packages] [Bug 1853964] Re: [hns-1126]net: hns3: make hclge_service use delayed workqueue

[Ike Panhc]

** Tags added: ikeradar

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

Title:
  [hns-1126]net: hns3: make hclge_service use delayed workqueue

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  System crashes when setting irq affinity and turning on/off on the interfaces

  [Fix]
  net: hns3: make hclge_service use delayed workqueue

  [Test]
  Writing smp_affinity_list and turning on/off in loop

  [Regression Potential]
  This patch only for hns3. Lowest risk for other platform/driver

  "[Bug Description]
  Currently, up/down port process may concurrently operate 
timer(del_timer_sync/add_timer_on) with setting IRQ affinity, and cause system 
breaking down.

  [Steps to Reproduce]
  set misc irp affinity of PF during up/down port by follow script:
  while((1))
  do
  for i in {0..31}; do echo $i > /proc/irq/678/smp_affinity_list; done
  done
  while((1))
  do
  ifconfig eth4 down
  ifconfig eth4 up
  done

  [Actual Results]
  System break down.
  kernel call trace

  [Expected Results]
  System run normally.

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  This patch uses delayed work instead of using timers to trigger the
  hclge_serive."

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

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

[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

[Daniel van Vugt]

Worth noting bluez 5.53 worked with ALL my audio devices on focal when I
introduced it some weeks ago.

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR-

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

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

Title:
  Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes
  entire system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.

  While hunting for answers as to why this occurs I stumbled upon my
  dmesg log stating

  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel

  
  and

  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }

  
  and

  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

  Hope this helps.

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

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

[Kernel-packages] [Bug 1860320] Re: [hns3-0120]pad the short frame before sending to the hardware

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-18.04
Milestone: None => ubuntu-18.04.4-sru-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/1860320

Title:
  [hns3-0120]pad the short frame before sending to the hardware

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  The hardware can not handle short frames below or equal to 32
  bytes.

  [Impact]
  The system may hang or endless event log in /var/log/syslog

  [Fix]
  Cherry-pick or backport the upstream fix 
36c67349a1a1c88b9cf11d7ca7762ababdb38867 net: hns3: pad the short frame before 
sending to the hardware

  [Test Case]
  Send a frame less than 33 bytes.

  [Regression Risk]
  Low, the patch is only specific to the hns3 driver.

  == Original Bug Description ==

  [Bug Description]
  The hardware can not handle short frames below or equal to 32
  bytes according to the hardware user manual, and it will trigger
  a RAS error when the frame's length is below 33 bytes.

  [Steps to Reproduce]
  1.send a frame less than 33 bytes.

  [Actual Results]
  a RAS occurs

  [Expected Results]
  no RAS

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  pads the SKB when skb->len is below 33 bytes before sending it to hardware.

  net: hns3: pad the short frame before sending to the hardware

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

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

[Kernel-packages] [Bug 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.4

** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04-ga

** Changed in: kunpeng920/ubuntu-19.10
Milestone: None => ubuntu-19.10-sru-8

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

Title:
  [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Sometimes, TPM fails because SPI data error

  [Fix]
  bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error

  [Test]
  Reboot system few times and no TPM error message

  [Regression Potential]
  Only on SPI function. Already tested on focal kernel

  [Bug Description]

  Because of out-of-order execution about some CPU architecture,
  In this debug stage we find Completing spi interrupt enable ->
  prodrucing TXEI interrupt -> running "interrupt_transfer" function
  will prior to set "dw->rx and dws->rx_end" data, so this patch add
  memory barrier to enable dw->rx and dw->rx_end to be visible and
  solve to send SPI data error.
  eg:
  it will fix to this following low possibility error in testing environment
  which using SPI control to connect TPM Modules

  kernel: tpm tpm0: Operation Timed out
  kernel: tpm tpm0: tpm_relinquish_locality: : error -1

  [Steps to Reproduce]
  1) enable ima and tpm
  2)reboot this system
  3)

  [Actual Results]
  kernel: tpm tpm0: Operation Timed out
  kernel: tpm tpm0: tpm_relinquish_locality: : error -1

  [Expected Results]
  ok

  [Reproducibility]
  low probabilities

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error

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

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

[Kernel-packages] [Bug 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: ubuntu-18.04.5 => ubuntu-18.04.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/1859743

Title:
  [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64
  platform

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  No TPM eventlog information in sysfs

  [Fix]
  d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform

  [Test]
  ls -l /sys/kernel/security/tpm0/binary_bios_measurements

  [Regression Potential]
  Only affect arm64 system with TPM. Lowest risk for other platform.

  [Bug Description]

  this patch gets tpm eventlog information such as device boot status,event guid
  and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog"
  functions to get it for ARM64 platorm.

  [Steps to Reproduce]
  1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements
  2)
  3)

  [Actual Results]
  '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory

  [Expected Results]
  ok

  [Reproducibility]
  100%

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform

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

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

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

[Logix]

Any idea how to get the mic working after applyying the workaround?

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

Title:
  PCI/internal sound card not detected

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

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

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

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

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

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

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

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

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


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

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

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

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

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

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

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

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

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

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



  Probably a kernel bug.

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

  The relevant dmesg message is:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 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: Thu Feb 20 16:46:21 2020
  InstallationDate: Installed on 2019-10-07 (136 days ago)
  InstallationMedia:

[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

[Daniel van Vugt]

... and still works with all of them today. After deleting
~/.config/pulse to work around bug 1866194

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- 

[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[ramon]

Thank you for your reply and your work in general, Hui Wang! If any
testing is helpful let me know. I get the Product Name "20QES01L00" via
dmidecode but future versions will check for bios version instead,
right? Does 1.1.9-0ubuntu1.2testucm already do this? (I had the led
problem also with the -43 kernel but not with earlier ones)

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

Title:
  [SRU] add ucm to make alsa/sof driver work under PA (variants of
  Lenovo X1 Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Kernel-packages] [Bug 1853993] Re: [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device

[Andrew Cloke]

Fix available from 18.04 HWE kernel. Marking won't fix for Bionic GA
4.15 kernel.

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: ubuntu-18.04.5 => ubuntu-18.04.4

** Changed in: kunpeng920/ubuntu-18.04
   Status: In Progress => Won't Fix

** Changed in: kunpeng920/ubuntu-18.04
Milestone: ubuntu-18.04.4-sru-1 => None

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

Title:
  [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init
  device

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Disks will be lost on SAS interface reset

  [Fix]
  scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device

  [Test]
  Resetting SAS interfaces shall not lose any disks

  [Regression Potential]
  Patch only for hisi_sas. Lowest risk for other platform/driver.

  "[Steps to Reproduce]
  1. Close all the PHYS;
  2. Inject error;
  3. Open one PHY;

  [Actual Results]
  Some disk will be lost

  [Expected Results]
  No disk will be lost

  [Reproducibility]
  occasionally

  [Additional information]
  Hardware: D06 CS
  Firmware: NA
  Kernel: NA

  [Resolution]
  When init device for SAS disks, it will send TMF IO to clear disks. At that
  time TMF IO is broken by some operations such as injecting controller reset
  from HW RAs event, the TMF IO will be timeout, and at last device will be
  gone. Print is as followed:

  hisi_sas_v3_hw :74:02.0: dev[240:1] found
  ...
  hisi_sas_v3_hw :74:02.0: controller resetting...
  hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata)
  hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11
  hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11
  hisi_sas_v3_hw :74:02.0: controller reset complete
  hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done
  hisi_sas_v3_hw :74:02.0: dev[240:1] is gone
  sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d,
  error:5

  To improve the reliability, retry TMF IO max of 3 times for SAS disks which
  is the same as softreset does."

  scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device

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

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

[Kernel-packages] [Bug 1849522] [NEW] imported non-rpool/bpool zpools are not being reimported after reboot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Installed ubuntu 19.10 onto a zfs bpool/rpool.

Installed zsys.

Did a "zpool import" of my existing zfs pools.

Rebooted.

The previously imported zpools are not imported at boot!

I am currently using this hacky workaround:

https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507


I would expect that local zpools I have manually imported would re-import when 
the system is rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: zsys 0.2.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Wed Oct 23 11:40:36 2019
InstallationDate: Installed on 2019-10-19 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zsys
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: amd64 apport-bug eoan
-- 
imported non-rpool/bpool zpools are not being reimported after reboot
https://bugs.launchpad.net/bugs/1849522
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to zfs-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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire

[Guy Baconniere]

So far no crash, freeze of any kind with Linux 5.5.13 compared to the
unstability of Ubuntu 20.04 with Linux 5.4 on Dell XPS 13 with 10th
Generation Intel Core i7-10510U CPU (Comet Lake)

I guess the patches are part of Linux v5.5.12 and later
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.12/CHANGES

 Chris Wilson (1):
  drm/i915/execlists: Track active elements during dequeue

 Matt Roper (1):
  drm/i915: Handle all MCR ranges

 Caz Yokoyama (1):
  Revert "drm/i915/tgl: Add extra hdc flush workaround"

Maybe Canonical should backport those patches to 5.4 or switch to 5.5
branch before Ubuntu 20.04 General Availability?

https://lkml.org/lkml/2020/3/22/419
https://lkml.org/lkml/2020/3/19/1779

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  [ 2556.956384] R13:  R14: 7ffee39a0090 R15: 
000d
  [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat 
typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables 
iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel

[Kernel-packages] [Bug 1849522] Re: imported non-rpool/bpool zpools are not being reimported after reboot

[Didier Roche]

Thanks for your bug report! This is now fixed in zfs-linux
0.8.3-1ubuntu10 in focal.

** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)

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

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

Title:
  imported non-rpool/bpool zpools are not being reimported after reboot

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Installed ubuntu 19.10 onto a zfs bpool/rpool.

  Installed zsys.

  Did a "zpool import" of my existing zfs pools.

  Rebooted.

  The previously imported zpools are not imported at boot!

  I am currently using this hacky workaround:

  https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507

  
  I would expect that local zpools I have manually imported would re-import 
when the system is rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zsys 0.2.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 23 11:40:36 2019
  InstallationDate: Installed on 2019-10-19 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1870060] [NEW] bluetoothd never leaves dumps/crash files when it crashes

[Daniel van Vugt]

Public bug reported:

bluetoothd never leaves dumps/crash files when it crashes

And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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


** Tags: focal

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

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

Title:
  bluetoothd never leaves dumps/crash files when it crashes

Status in bluez package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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

[Kernel-packages] [Bug 1869919] Re: Kernel 5.3.0-40-generic cannot boot from PATA drive

[psl]

Package linux-modules-extra-5.3.0-28-generic was installed but package 
linux-modules-extra-5.3.0-40-generic was not installed.
I installed linux-modules-extra-5.3.0-40-generic and I can boot linux with that 
kernel, problem fixed. Thank you for the advice!

Do I need manually install linux-modules-extra-5.3.0-XX-generic each
time new kernel is installed with "apt dist-upgrade"?? If this is the
case, it is not good. I searched for package like "linux-modules-extra-
generic" or "linux-modules-extra" and I cannot see anything like that in
the repository.

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

Title:
  Kernel 5.3.0-40-generic cannot boot from PATA drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-Budgie 18.04.4 amd64
  kernel linux-image-5.3.0-40-generic

  I build a Ubuntu PC and I used PATA notebook disk (44 PIN connector,
  SSD)

  PROBLEM DESCRIPTION

  PC works fine with kernel "linux-image-5.3.0-28-generic" but when I
  try to use updated kernel "linux-image-5.3.0-40-generic", it fails to
  boot and reports it cannot find disk. I have to manually select older
  kernel in GRUB during boot process. Kernel linux-
  image-5.3.0-40-generic starts but when it tries to mount root
  partition it fails and reports it cannot find it (to have exact
  message I have to reboot PC). Are PATA disk drivers included with
  updated kernel?

  INFO

  # uname -a
  Linux fah 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  # inxi -F  # HW info
  System:Host: fah Kernel: 5.3.0-28-generic x86_64 bits: 64 Console: tty 2 
Distro: Ubuntu 18.04.4 LTS
  Machine:   Device: desktop Mobo: Gigabyte model: GA-MA78G-DS3H serial: N/A 
BIOS: Award v: F9 date: 11/16/2012
  CPU:   Dual core AMD Athlon 64 X2 3800+ (-MCP-) cache: 1024 KB
 clock speeds: max: 2000 MHz 1: 2000 MHz 2: 2000 MHz
  Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] RS780 [Radeon HD 3200]
 Card-2: NVIDIA GP106 [GeForce GTX 1060 3GB]
 Display Server: X.org 1.20.5 drivers: ati,radeon (unloaded: 
modesetting,nvidia,fbdev,vesa,nouveau)
 tty size: 114x33 Advanced Data: N/A for root out of X
  Audio: Card-1 Advanced Micro Devices [AMD/ATI] RS780 HDMI Audio [Radeon 
3000/3100 / HD 3200/3300]
 driver: snd_hda_intel
 Card-2 NVIDIA GP106 High Definition Audio Controller driver: 
snd_hda_intel
 Card-3 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) 
driver: snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k5.3.0-28-generic
  Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 
00:1f:d0:97:b9:42
  Drives:HDD Total Size: 64.0GB (32.6% used)
 ID-1: /dev/sda model: TS64GPSD320 size: 64.0GB
  Partition: ID-1: / size: 59G used: 16G (29%) fs: ext4 dev: /dev/sda1
 ID-2: swap-1 size: 1.95GB used: 0.00GB (0%) fs: swap dev: 
/dev/zram0
 ID-3: swap-2 size: 1.95GB used: 0.00GB (0%) fs: swap dev: 
/dev/zram1
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 90.0C mobo: 43.0C
 Fan Speeds (in rpm): cpu: 1956 fan-2: 0 fan-3: 0
  Info:  Processes: 216 Uptime: 11 days Memory: 2416.1/7456.3MB Init: 
systemd runlevel: 5
 Client: Shell (bash) inxi: 2.3.56
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D8p', 
'/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA78G-DS3H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=f9f74101-cc1d-4d7e-9621-9a012e09c9c8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.16
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  

[Kernel-packages] [Bug 1870060] Re: bluetoothd never leaves dumps/crash files when it crashes

[Daniel van Vugt]

** Tags added: champagne

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

Title:
  bluetoothd never leaves dumps/crash files when it crashes

Status in bluez package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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

[Kernel-packages] [Bug 1843742] Re: irda-utils ftbfs in eoan

[Matthias Klose]

** Tags added: rls-ff-incoming

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

Title:
  irda-utils ftbfs in eoan

Status in irda-utils package in Ubuntu:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
  .irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz

  gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline 
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c 
irdadump.c
  irdadump.c: In function ‘print_time’:
  irdadump.c:82:13: warning: g_string_append_printf
 82 |  g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
  irdadump.c: In function ‘print_diff_time’:
  irdadump.c:108:13: warning: g_string_append_printf
108 |  g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
  irdadump.c: In function ‘parse_irda_frame’:
  irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
  irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
  irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
  irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
  irdadump.c: In function ‘irdadump_loop’:
  irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this 
function); did you mean ‘SIOCGARP’?
286 |  if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
  irdadump.c:286:16: note: each undeclared identifier is reported only once for 
each function it appears in
  make[1]: *** [Makefile:48: irdadump.o] Error 1
  make[1]: Leaving directory '/<>/irdadump'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/1843742/+subscriptions

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

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

[Hui Wang]

@Logix,

Wait for the -46 kernel, then remove the workaround.

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

Title:
  PCI/internal sound card not detected

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

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

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

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

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

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

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

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

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


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

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

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

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

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

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

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

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

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

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



  Probably a kernel bug.

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

  The relevant dmesg message is:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 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: Thu Feb 20 16:46:21 2020
  InstallationDate: Installed on 2019-10-07 (136 days ago)
  InstallationMedia:

[Kernel-packages] [Bug 1870093] [NEW] ftbfs in focal

[Matthias Klose]

Public bug reported:

seen in the second focal test rebuild
https://launchpadlibrarian.net/471195717/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oem-5.4_5.4.0-1002.4_BUILDING.txt.gz

II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1002-oem/lib/modules/5.4.0-1002-oem/kernel/nvidia-390
copying nvidia-uvm.ko
copying nvidia.ko
copying nvidia-drm.ko
copying nvidia-modeset.ko
II: dkms-build override dkms-build--nvidia-N found, executing
II: checking gcc version ...
GCC: (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110
gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

WW: gcc version missmatch between linux and linux-restricted-modules
WW: was: gcc (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
II: adding signatures from /usr/lib/linux/5.4.0-1002-oem ...
nvidia-drm.ko: FAILED
nvidia-modeset.ko: FAILED
nvidia-uvm.ko: FAILED
nvidia.ko: FAILED
sha256sum: WARNING: 4 computed checksums did NOT match
make[1]: *** [debian/rules:129: nvidia-oem] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:82: binary] Error 2

** Affects: linux-restricted-modules-oem-5.4 (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

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

** Changed in: linux-restricted-modules-oem-5.4 (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-oem-5.4 package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpadlibrarian.net/471195717/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oem-5.4_5.4.0-1002.4_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1002-oem/lib/modules/5.4.0-1002-oem/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1002-oem ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-oem] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:82: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.4/+bug/1870093/+subscriptions

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

[Kernel-packages] [Bug 1870091] [NEW] ftbfs in focal

[Matthias Klose]

Public bug reported:

seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946775/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-azure_5.4.0-1006.6_BUILDING.txt.gz

II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1006-azure/lib/modules/5.4.0-1006-azure/kernel/nvidia-390
copying nvidia-uvm.ko
copying nvidia.ko
copying nvidia-drm.ko
copying nvidia-modeset.ko
II: dkms-build override dkms-build--nvidia-N found, executing
II: checking gcc version ...
GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

WW: gcc version missmatch between linux and linux-restricted-modules
WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
II: adding signatures from /usr/lib/linux/5.4.0-1006-azure ...
nvidia-drm.ko: FAILED
nvidia-modeset.ko: FAILED
nvidia-uvm.ko: FAILED
nvidia.ko: FAILED
sha256sum: WARNING: 4 computed checksums did NOT match
make[1]: *** [debian/rules:129: nvidia-azure] Error 1

** Affects: linux-restricted-modules-azure (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: linux-restricted-modules-azure (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-restricted-modules-azure (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-azure package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946775/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-azure_5.4.0-1006.6_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1006-azure/lib/modules/5.4.0-1006-azure/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1006-azure ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-azure] Error 1

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

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

[Kernel-packages] [Bug 1870094] [NEW] ftbfs in focal

[Matthias Klose]

Public bug reported:

seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946778/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oracle_5.4.0-1005.5_BUILDING.txt.gz

II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1005-oracle/lib/modules/5.4.0-1005-oracle/kernel/nvidia-390
copying nvidia-uvm.ko
copying nvidia.ko
copying nvidia-drm.ko
copying nvidia-modeset.ko
II: dkms-build override dkms-build--nvidia-N found, executing
II: checking gcc version ...
GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

WW: gcc version missmatch between linux and linux-restricted-modules
WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
II: adding signatures from /usr/lib/linux/5.4.0-1005-oracle ...
nvidia-drm.ko: FAILED
nvidia-modeset.ko: FAILED
nvidia-uvm.ko: FAILED
nvidia.ko: FAILED
sha256sum: WARNING: 4 computed checksums did NOT match
make[1]: *** [debian/rules:129: nvidia-oracle] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:82: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2

** Affects: linux-restricted-modules-oracle (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: linux-restricted-modules-oracle (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-restricted-modules-oracle (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-oracle package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946778/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oracle_5.4.0-1005.5_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1005-oracle/lib/modules/5.4.0-1005-oracle/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1005-oracle ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-oracle] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:82: binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oracle/+bug/1870094/+subscriptions

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

[Kernel-packages] [Bug 1870090] [NEW] ftbfs in focal

[Matthias Klose]

Public bug reported:

seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946774/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-aws_5.4.0-1005.5_BUILDING.txt.gz

copying nvidia-uvm.ko
copying nvidia.ko
copying nvidia-drm.ko
copying nvidia-modeset.ko
II: dkms-build override dkms-build--nvidia-N found, executing
II: checking gcc version ...
GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

WW: gcc version missmatch between linux and linux-restricted-modules
WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
II: adding signatures from /usr/lib/linux/5.4.0-1005-aws ...
nvidia-drm.ko: FAILED
nvidia-modeset.ko: FAILED
nvidia-uvm.ko: FAILED
nvidia.ko: FAILED
sha256sum: WARNING: 4 computed checksums did NOT match
make[1]: *** [debian/rules:129: nvidia-aws] Error 1
make[1]: Leaving directory '/<>'

** Affects: linux-restricted-modules-aws (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: linux-restricted-modules-aws (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-restricted-modules-aws (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-aws package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946774/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-aws_5.4.0-1005.5_BUILDING.txt.gz

  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1005-aws ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-aws] Error 1
  make[1]: Leaving directory '/<>'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-aws/+bug/1870090/+subscriptions

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

[Kernel-packages] [Bug 1870092] [NEW] ftbfs in focal

[Matthias Klose]

Public bug reported:

seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946776/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-gcp_5.4.0-1005.5_BUILDING.txt.gz

II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1005-gcp/lib/modules/5.4.0-1005-gcp/kernel/nvidia-390
copying nvidia-uvm.ko
copying nvidia.ko
copying nvidia-drm.ko
copying nvidia-modeset.ko
II: dkms-build override dkms-build--nvidia-N found, executing
II: checking gcc version ...
GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

WW: gcc version missmatch between linux and linux-restricted-modules
WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
II: adding signatures from /usr/lib/linux/5.4.0-1005-gcp ...
nvidia-drm.ko: FAILED
nvidia-modeset.ko: FAILED
nvidia-uvm.ko: FAILED
nvidia.ko: FAILED
sha256sum: WARNING: 4 computed checksums did NOT match
make[1]: *** [debian/rules:129: nvidia-gcp] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:82: binary] Error 2

** Affects: linux-restricted-modules-gcp (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: ftbfs rls-ff-incoming

** Changed in: linux-restricted-modules-gcp (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-restricted-modules-gcp (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-ff-incoming

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

Title:
  ftbfs in focal

Status in linux-restricted-modules-gcp package in Ubuntu:
  Confirmed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946776/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-gcp_5.4.0-1005.5_BUILDING.txt.gz

  II: dkms-build installing nvidia-390 into 
/<>/debian/linux-modules-nvidia-390-5.4.0-1005-gcp/lib/modules/5.4.0-1005-gcp/kernel/nvidia-390
  copying nvidia-uvm.ko
  copying nvidia.ko
  copying nvidia-drm.ko
  copying nvidia-modeset.ko
  II: dkms-build override dkms-build--nvidia-N found, executing
  II: checking gcc version ...
  GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
  gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0
  Copyright (C) 2019 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  WW: gcc version missmatch between linux and linux-restricted-modules
  WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306  is: gcc (Ubuntu 
9.3.0-8ubuntu1) 9.3.0
  II: adding signatures from /usr/lib/linux/5.4.0-1005-gcp ...
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  make[1]: *** [debian/rules:129: nvidia-gcp] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:82: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-gcp/+bug/1870092/+subscriptions

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

[Kernel-packages] [Bug 1830678] Re: netns_sysfs from containers test suite in LTP failed with KVM kernel

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  netns_sysfs from containers test suite in LTP failed with KVM kernel

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

Bug description:
  <<>>
  tag=netns_sysfs stime=1559024934
  cmdline="netns_sysfs.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  RTNETLINK answers: Operation not supported
  netns_sysfs 1 TBROK: failed to add a new (host) dummy device
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=1 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35
  ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18
  Uname: Linux 4.15.0-1035-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue May 28 06:22:51 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1864303] Re: Removing the e1000e module causes a crash

[Kai-Heng Feng]

Yes, that's correct.

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1864303

Title:
  Removing the e1000e module causes a crash

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a Lenovo x1 Carbon Gen5 and when it initially came out if you
  left the onboard NIC (e1000e) module loaded it would suck CPU/battery
  life so I have it removed in rc.local on boot.

  In 5.4 (also happens on 5.4.0.15.18 which I'm running from proposed
  right now), this is what happens when the module is unloaded:

  [  608.979789] e1000e :00:1f.6 enp0s31f6: removed PHC
  [  609.008352] [ cut here ]
  [  609.008353] kernel BUG at drivers/pci/msi.c:375!
  [  609.008358] invalid opcode:  [#1] SMP PTI
  [  609.008359] CPU: 0 PID: 6829 Comm: rmmod Tainted: P   O  
5.4.0-15-generic #18-Ubuntu
  [  609.008360] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET59W 
(1.44 ) 11/25/2019
  [  609.008364] RIP: 0010:free_msi_irqs+0x17d/0x1b0
  [  609.008365] Code: 84 df fe ff ff 45 31 f6 eb 11 41 83 c6 01 44 39 73 14 0f 
86 cc fe ff ff 8b 7b 10 44 01 f7 e8 ea c3 b6 ff 48 83 78 70 00 74 e0 <0f> 0b 49 
8d b5 b0 00 00 00 e8 b5 7d b7 ff e9 cd fe ff ff 49 8b 78
  [  609.008366] RSP: 0018:a7d2072f7d40 EFLAGS: 00010286
  [  609.008367] RAX: 8bc9bfb49e00 RBX: 8bc9ad69c720 RCX: 

  [  609.008368] RDX:  RSI: 0084 RDI: 
a9e65980
  [  609.008369] RBP: a7d2072f7d70 R08: 8bc9bb564db0 R09: 
8bc9bb564df8
  [  609.008369] R10:  R11: a9e65988 R12: 
8bc9cb5272c0
  [  609.008370] R13: 8bc9cb527000 R14:  R15: 
dead0100
  [  609.008371] FS:  7f188f1f9500() GS:8bc9ce20() 
knlGS:
  [  609.008372] CS:  0010 DS:  ES:  CR0: 80050033
  [  609.008373] CR2: 7f6d1a6af060 CR3: 00046d9f8006 CR4: 
003606f0
  [  609.008373] Call Trace:
  [  609.008376]  pci_disable_msi+0x100/0x130
  [  609.008385]  e1000e_reset_interrupt_capability+0x52/0x60 [e1000e]
  [  609.008389]  e1000_remove+0xc4/0x180 [e1000e]
  [  609.008391]  pci_device_remove+0x3e/0xb0
  [  609.008394]  device_release_driver_internal+0xf0/0x1d0
  [  609.008396]  driver_detach+0x4c/0x8f
  [  609.008397]  bus_remove_driver+0x5c/0xd0
  [  609.008399]  driver_unregister+0x31/0x50
  [  609.008400]  pci_unregister_driver+0x40/0x90
  [  609.008405]  e1000_exit_module+0x10/0x3c1 [e1000e]
  [  609.008407]  __x64_sys_delete_module+0x147/0x2b0
  [  609.008409]  ? exit_to_usermode_loop+0xea/0x160
  [  609.008411]  do_syscall_64+0x57/0x190
  [  609.008413]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  609.008414] RIP: 0033:0x7f188f345c9b
  [  609.008416] Code: 73 01 c3 48 8b 0d f5 71 0c 00 f7 d8 64 89 01 48 83 c8 ff 
c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c5 71 0c 00 f7 d8 64 89 01 48
  [  609.008416] RSP: 002b:7fffc8d32e68 EFLAGS: 0206 ORIG_RAX: 
00b0
  [  609.008418] RAX: ffda RBX: 561e1a391790 RCX: 
7f188f345c9b
  [  609.008419] RDX: 000a RSI: 0800 RDI: 
561e1a3917f8
  [  609.008420] RBP: 7fffc8d32ec8 R08:  R09: 

  [  609.008420] R10: 7f188f3c1ac0 R11: 0206 R12: 
7fffc8d33090
  [  609.008422] R13: 7fffc8d3474a R14: 561e1a3912a0 R15: 
561e1a391790
  [  609.008424] Modules linked in: thunderbolt rfcomm xfrm_user xfrm_algo 
l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ccm xt_comment 
xt_CHECKSUM xt_MASQUERADE ip6table_mangle ip6table_nat dummy iptable_mangle 
iptable_nat nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher 
af_alg bnep zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) 
spl(O) zlua(PO) joydev intel_rapl_msr mei_hdcp nls_iso8859_1 snd_seq_midi 
snd_seq_midi_event snd_hda_codec_hdmi snd_hda_codec_conexant 
snd_hda_codec_generic intel_rapl_common x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_hda_intel snd_rawmidi kvm snd_intel_nhlt snd_hda_codec 
intel_cstate rmi_smbus intel_rapl_perf snd_hda_core snd_hwdep iwlmvm rmi_core 
mac80211 uvcvideo input_leds videobuf2_vmalloc videobuf2_memops btusb btrtl 
snd_pcm libarc4 serio_raw snd_seq btbcm intel_wmi_thunderbolt videobuf2_v4l2 
btintel videobuf2_common wmi_bmof thinkpad_acpi bluetooth videodev nvram 
snd_seq_device ledtrig_audio
  [  609.008447]  iwlwifi mc snd_timer rtsx_pci_ms ecdh_generic ecc cfg80211 
memstick snd mei_me ucsi_acpi typec_ucsi intel_xhci_usb_role_switch mei roles 
intel_pch_thermal typec soundcore acpi_pad mac_hid nf_log_ipv6 ip6t_REJECT 
nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT 
nf_reject_ipv4 xt_LOG xt_limit xt_

[Kernel-packages] [Bug 1812194] Re: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in linux-kvm source package in Disco:
  New

Bug description:
  This test failed because of the unsuccessful attempt to add a dummy device 
with ip link command:
  # devdummy="test-dummy0"
  # ip link add name "$devdummy" type dummy
  RTNETLINK answers: Operation not supported

  
   selftests: rtnetlink.sh
   
   RTNETLINK answers: Operation not supported
   Cannot find device "test-dummy0"
   FAIL: cannot add dummy interface
   not ok 1..10 selftests: rtnetlink.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:21:02 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed

[Po-Hsu Lin]

** Tags added: sru-20200316

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

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

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

** Tags added: eoan

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

Title:
  fib related test in net from ubuntu_kernel_selftests failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-kvm source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-kvm source package in Eoan:
  New

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

[Po-Hsu Lin]

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

Title:
  msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New

Bug description:
  This test will return 1

  $ sudo ./msg_zerocopy.sh 
  ipv4 tcp -t 1
  ./msg_zerocopy: setaffinity 2
  ./msg_zerocopy: setaffinity 3
  $ echo $?
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
   crw-rw 1 root audio 116, 33 Jan 21 07:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:50:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel

[Po-Hsu Lin]

** Tags added: sru-20200316

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

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  kernel

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

Bug description:
  Test failed becuase:
 ./ip_defrag: sendto overlap: 1400: Operation not permitted

  
   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM / E-KVM

[Po-Hsu Lin]

** Summary changed:

- test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM
+ test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM 
/ E-KVM

** Tags added: 5.3 eoan sru-20200316

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

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

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with D-KVM / E-KVM

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

Bug description:
  Issue found on a AMD64 KVM node with Disco KVM kernel.

  selftests: net: test_vxlan_under_vrf.sh
  
  Error: Unknown device type.
  Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory
  Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory
  Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory
  not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11
  ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8
  Uname: Linux 5.0.0-1010-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Jul 22 05:04:42 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

[Po-Hsu Lin]

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

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

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

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

Title:
  msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux-azure source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-azure source package in Eoan:
  New

Bug description:
  This test will return 1

  $ sudo ./msg_zerocopy.sh 
  ipv4 tcp -t 1
  ./msg_zerocopy: setaffinity 2
  ./msg_zerocopy: setaffinity 3
  $ echo $?
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
   crw-rw 1 root audio 116, 33 Jan 21 07:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:50:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

[Bin Li]

Tried libasound2 packages with the 5.0.0-10477-oem-osp1 kernel in
proposed, the dmic works fine on bionic.

libasound2:1.1.3-5ubuntu0.5
libasound2-data:1.1.3-5ubuntu0.5

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

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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

[Kernel-packages] [Bug 1864698] Re: Can't change laptop-screen brightness on Dell XPS 13 9370 with kernel 5.4, but 5.3 works

[Ricardo Abreu]

Hi, I confirm that fixes it! Thanks.

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

Title:
  Can't change laptop-screen brightness on Dell XPS 13 9370 with kernel
  5.4, but 5.3 works

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

Bug description:
  === SRU Justification ===
  [Impact]
  Brightness on XPS 9370 can't be changed.

  [Fix]
  Revert the regression commit, which matches to XPS 9730's panel.
   
  [Test]
  After reverting the commit and tested an XPS 9370 at my hand, the
  backlight sysfs interface starts to work again.

  [Regression Potential]
  Low. It reverts a quirk for a specific kernel.

  === Original Bug Report ===

  I can't change the screen brightness anymore, on a Dell XPS13. Neither
  the keyboard shortcuts nor gnome's sliders work. They move, but
  brightness remains unchanged.

  I first noticed this after disconnecting an external display, but I
  have since rebooted and the problem remains.

  This on Focal. I have done a series of upgrades since the original
  installation and I know this used to work, but I can't be sure of when
  exactly it stopped working. I noticed now, but it could have arisen
  earlier. I am pretty sure it was OK on Disco.

  I attach the output of lshw. Let me know what else I can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 17:52:13 2020
  DistUpgraded: 2020-02-24 18:02:48,088 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 2019-01-21 (400 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=ae14977c-0724-4298-9c08-80ea948af070 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-02-24 (0 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: ricab-xps13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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/1864698/+subscriptions

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

[Kernel-packages] [Bug 1867885] Re: Suspend does not work on Thinkpad X1 Yoga

[Jesko]

How do I install kernel version which I do not get over the
repositories. Through updating I only got -40, -42, -45 no -43

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

Title:
  Suspend does not work on Thinkpad X1 Yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my 
Thinkpad X1 Yoga I could not wake it up from suspend anymore.
  I downgraded to 5.3.0-40-generic and it works again.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-15 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QFS10B00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic 
root=/dev/mapper/vgubuntu-root 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QFS10B00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20QFS10B00
  dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'

[Po-Hsu Lin]

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

Title:
  lxc-test-no-new-privs failed with Temporary failure resolving
  'archive.ubuntu.com'

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It seems this failure only exist in KVM instances.

FAIL: lxc-tests: lxc-test-no-new-privs (37s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ mkdir -p /etc/lxc/
+ cat
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu xenial amd64 (20190320_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
+ echo 'lxc.no_new_privs = 1'
+ lxc-start -n c1
++ lxc-info -n c1 -p -H
+ p1=8818
+ '[' 8818 '!=' -1 ']'
+ sleep 5s
+ lxc-attach -n c1 --clear-env -- apt update -y

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
+ lxc-attach -n c1 --clear-env -- apt install -y gcc make

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev 
libcc1-0
  libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 
libmpfr4
  libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages 
manpages-dev
Suggested packages:
  binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool
  flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg
  libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg
  libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc
  make-doc man-browser
The following NEW packages will be installed:
  binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev
  libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 
libmpc3
  libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make
  manpages manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.7 MB of archives.
After this operation, 102 MB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 
3.1.4-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 
1.0.3-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2
  Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils 
amd64 2.26.1-1ubuntu1~16.04.8
  Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 
0.16.1-1
  Temporary failure resolving 'archive.ubuntu.com'

  
  It's a bit weird that if I run the command manually, it looks OK
  lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
  lxc-start -n c1
  lxc-attach -n c1 --clear-env -- apt update -y
  Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
  Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
  Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 

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

[Stephen Waines]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1869993/+attachment/5344221/+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/1869993

Title:
  Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes
  entire system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.

  While hunting for answers as to why this occurs I stumbled upon my
  dmesg log stating

  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel

  
  and

  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }

  
  and

  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

  Hope this helps.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1826 F pulseaudio
   /dev/snd/controlC2:  steve  1826 F pulseaudio
   /dev/snd/controlC1:  steve  1826 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-16 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=ce2b1a08-f3b8-4886-86fb-1c67ae558f66 ro
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd09/17/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

Re: [Kernel-packages] [Bug 1869993] Missing required logs.

[Stephen Waines]

done

On 2020-04-01 4:00 a.m., Ubuntu Kernel Bot wrote:
> apport-collect 1869993

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

Title:
  Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes
  entire system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.

  While hunting for answers as to why this occurs I stumbled upon my
  dmesg log stating

  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel

  
  and

  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }

  
  and

  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

  Hope this helps.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1826 F pulseaudio
   /dev/snd/controlC2:  steve  1826 F pulseaudio
   /dev/snd/controlC1:  steve  1826 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-16 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=ce2b1a08-f3b8-4886-86fb-1c67ae558f66 ro
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd09/17/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1869993] Re: Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes entire system

[Stephen Waines]

apport information

** Tags added: apport-collected

** Description changed:

  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.
  
  While hunting for answers as to why this occurs I stumbled upon my dmesg
  log stating
  
  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel
  
  
  and
  
  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }
  
  
  and
  
  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps
  
  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.
  
  Hope this helps.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  steve  1826 F pulseaudio
+  /dev/snd/controlC2:  steve  1826 F pulseaudio
+  /dev/snd/controlC1:  steve  1826 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-03-16 (15 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
+ IwConfig:
+  enp2s0no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: To be filled by O.E.M. To be filled by O.E.M.
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=ce2b1a08-f3b8-4886-86fb-1c67ae558f66 ro
+ ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-18-generic N/A
+  linux-backports-modules-5.4.0-18-generic  N/A
+  linux-firmware1.187
+ RfKill:
+  
+ Tags:  focal
+ Uname: Linux 5.4.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/17/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 0906
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: M5A97 R2.0
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd09/17/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: To be filled by O.E.M.
+ dmi.product.sku: SKU
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: To be filled by O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1869993/+attachment/5344220/+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/1869993

Title:
  Ubuntu 20.04 Desktop clean install:Plugging or unplugging usb freezes
  entire system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the latest updates. I have noticed today that plugging or
  unplugging a usb device while the computer is on freezes the whole
  computer, keyboard/mouse are completly unresponsive.

  While hunting for answers as to why this occurs I stumbled upon my
  dmesg log stating

  [   13.356149] vboxdrv: module verification failed: signature and/or
  required key missing - tainting kernel

  
  and

  [15265.066193] ata3.00: exception Emask 0x10 SAct 0x7e00 SErr 0x40 action 
0x6 frozen
  [15265.066200] ata3.00: irq_stat 0x0800, interface fatal error
  [15265.066206] ata3: SError: { Handshk }

  
  and

  [15629.359098] ata3: limiting SATA link speed to 3.0 Gbps

  it seems to be limiting my sata 3 to 3Mbps and running at 6Mbps.

  Hope this helps.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1826 F pulseaudio
   /dev/snd/controlC2:  steve  1826 F pulseaudio
   /dev/snd/controlC1:  steve  1826 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-16 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=ce2b1a08-f3b8-4886-86f

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Carmelo Caldarella]

[Urgent!] LCD black screen with Dell Studio 1537 and ATI Mobility Radeon
HD 3450

When I turn on the laptop the screen remains black and the only way to view it 
is by connecting with the VGA interface to an external monitor, also I add that 
I can start the operating system only by adding as a parameter to the kernel:
GRUB_CMDLINE_LINUX_DEFAULT="radeon.modeset=0"

I have upgraded to:

linux-firmware 1.183.5  all  Firmware for Linux kernel
drivers

but the problem persists

** Attachment added: "2020-04-01 10.29.19 - journalctl - dell-studio-1537 - 
Ubuntu 19.10.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130/+attachment/5344222/+files/2020-04-01%2010.29.19%20-%20journalctl%20-%20dell-studio-1537%20-%20Ubuntu%2019.10.txt

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223

[Kernel-packages] [Bug 1848771]

[ferry.toth]

Closing laptop lid it goes to sleep properly (suspend led blinks).
Opening the lid again brings my direct to the boot screen.

So no change.

This is with vanilla 5.6.0 + ubuntu 'sauce' + patch in #21 above -
TCG_TPM.

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

Title:
  Reboot after resume from suspend (deep)

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes
  after resume from suspending. This is regardless the way of suspending
  (closing lid, selecting suspend from sddm, systemctl suspend).

  The journal shows:
  ferry@chromium:~$ journalctl -b -1 -e
  ..
  sddm[1106]: Message received from greeter: Suspend
  NetworkManager[836]:   manager: sleep: sleep requested (sleeping: no  
enabled: yes)
  NetworkManager[836]:   device (60:73:BC:BA:B8:68): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (60:73:BC:23:8F:3E): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (p2p-dev-wlp1s0): state change: 
disconnected -> unmanaged (reason 'sle
  NetworkManager[836]:   manager: NetworkManager state is now ASLEEP
  systemd[1]: Reached target Sleep.
  systemd[1]: Starting Suspend...
  systemd-sleep[1238]: Suspending system...
  kernel: PM: suspend entry (deep)

  On resume (keypress, open lid) resume starts but immediately crashes
  and reboots.

  The laptop is an Acer 720p Chromebook with Chromium replaced and
  working fine with Kubuntu since 5 years or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 18 18:45:53 2019
  InstallationDate: Installed on 2017-07-13 (826 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1848771]

[ferry.toth]

I disabled INTEGRITY and then TCG_TPM'in menuconfig and built kernel.

Then:
root@chromium:~# echo test_resume > /sys/power/disk
root@chromium:~# echo disk > /sys/power/state
-bash: echo: schrijffout: Geen ruimte meer over op apparaat

(that is write error: no more space on device).

It seems with this test it is trying to hybernate instead of suspend.

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

Title:
  Reboot after resume from suspend (deep)

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes
  after resume from suspending. This is regardless the way of suspending
  (closing lid, selecting suspend from sddm, systemctl suspend).

  The journal shows:
  ferry@chromium:~$ journalctl -b -1 -e
  ..
  sddm[1106]: Message received from greeter: Suspend
  NetworkManager[836]:   manager: sleep: sleep requested (sleeping: no  
enabled: yes)
  NetworkManager[836]:   device (60:73:BC:BA:B8:68): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (60:73:BC:23:8F:3E): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (p2p-dev-wlp1s0): state change: 
disconnected -> unmanaged (reason 'sle
  NetworkManager[836]:   manager: NetworkManager state is now ASLEEP
  systemd[1]: Reached target Sleep.
  systemd[1]: Starting Suspend...
  systemd-sleep[1238]: Suspending system...
  kernel: PM: suspend entry (deep)

  On resume (keypress, open lid) resume starts but immediately crashes
  and reboots.

  The laptop is an Acer 720p Chromebook with Chromium replaced and
  working fine with Kubuntu since 5 years or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 18 18:45:53 2019
  InstallationDate: Installed on 2017-07-13 (826 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1848771]

[ferry.toth]

Must we disable 'CONFIG_TCG_TPM'? Because it is auto selected:
Selected by [y]:


 
- IMA [=y] && INTEGRITY [=y] && HAS_IOMEM [=y] && !UML

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

Title:
  Reboot after resume from suspend (deep)

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes
  after resume from suspending. This is regardless the way of suspending
  (closing lid, selecting suspend from sddm, systemctl suspend).

  The journal shows:
  ferry@chromium:~$ journalctl -b -1 -e
  ..
  sddm[1106]: Message received from greeter: Suspend
  NetworkManager[836]:   manager: sleep: sleep requested (sleeping: no  
enabled: yes)
  NetworkManager[836]:   device (60:73:BC:BA:B8:68): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (60:73:BC:23:8F:3E): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (p2p-dev-wlp1s0): state change: 
disconnected -> unmanaged (reason 'sle
  NetworkManager[836]:   manager: NetworkManager state is now ASLEEP
  systemd[1]: Reached target Sleep.
  systemd[1]: Starting Suspend...
  systemd-sleep[1238]: Suspending system...
  kernel: PM: suspend entry (deep)

  On resume (keypress, open lid) resume starts but immediately crashes
  and reboots.

  The laptop is an Acer 720p Chromebook with Chromium replaced and
  working fine with Kubuntu since 5 years or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 18 18:45:53 2019
  InstallationDate: Installed on 2017-07-13 (826 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM

[Kleber Sacilotto de Souza]

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

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

Title:
  ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM

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

Bug description:
  4 tests failed:
  [11] ftrace - function glob filters   [FAIL]
  [23] Kprobe event argument syntax [FAIL]
  [36] event trigger - test histogram trigger   [FAIL]
  [51] (instance)  event trigger - test histogram trigger   [FAIL]

  With the test suite in the upstream kernel tree, 3 of these failures can be 
reproduced, except this one:
  -e -n [34] Kprobe event argument syntax
  -e[UNTESTED]


  $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests
  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/ftrace'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/ftrace'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/ftrace'
  TAP version 13
  selftests: ftracetest
  
  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] event tracing - enable/disable with event level files [PASS]
  [6] event tracing - restricts events based on pid [PASS]
  [7] event tracing - enable/disable with subsystem level files [PASS]
  [8] event tracing - enable/disable with top level files   [PASS]
  [9] ftrace - function graph filters with stack tracer [PASS]
  [10] ftrace - function graph filters  [PASS]
  [11] ftrace - function glob filters   [FAIL]
  [12] ftrace - function pid filters[PASS]
  [13] ftrace - test for function event triggers[PASS]
  [14] ftrace - function profiler with function tracing [PASS]
  [15] ftrace - test reading of set_ftrace_filter   [PASS]
  [16] ftrace - test for function traceon/off triggers  [PASS]
  [17] Test creation and deletion of trace instances while setting an event 
[PASS]
  [18] Test creation and deletion of trace instances[PASS]
  [19] Kprobe dynamic event - adding and removing   [PASS]
  [20] Kprobe dynamic event - busy event check  [PASS]
  [21] Kprobe dynamic event with arguments  [PASS]
  [22] Kprobe event string type argument[UNTESTED]
  [23] Kprobe event argument syntax [FAIL]
  [24] Kprobes event arguments with types   [PASS]
  [25] Kprobe event auto/manual naming  [PASS]
  [26] Kprobe dynamic event with function tracer[PASS]
  [27] Kprobe dynamic event - probing module[PASS]
  [28] Kretprobe dynamic event with arguments   [PASS]
  [29] Kretprobe dynamic event with maxactive   [PASS]
  [30] Register/unregister many kprobe events   [PASS]
  [31] Kprobe events - probe points [PASS]
  [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED]
  [33] event trigger - test event enable/disable trigger[PASS]
  [34] event trigger - test trigger filter  [PASS]
  [35] event trigger - test histogram modifiers [PASS]
  [36] event trigger - test histogram trigger   [FAIL]
  [37] event trigger - test multiple histogram triggers [PASS]
  [38] event trigger - test snapshot-trigger[PASS]
  [39] event trigger - test stacktrace-trigger  [PASS]
  [40] event trigger - test traceon/off trigger [PASS]
  [41] (instance)  Basic test for tracers   [PASS]
  [42] (instance)  Basic trace clock test   [PASS]
  [43] (instance)  event tracing - enable/disable with event level files
[PASS]
  [44] (instance)  event tracing - restricts events based on pid[PASS]
  [45] (instance)  event tracing - enable/disable with subsystem level files
[PASS]
  [46] (instance)  ftrace - test for function event triggers[PASS]
  [47] (instance)  ftrace - test for function traceon/off triggers  [PASS]
  [48] (instance)  event trigger - test event enable/disable trigger[PASS]
  [49] (instance)  event trigger - test trigger filter  [PASS]
  [50] (instance)  event trigger - test histogram modifiers [PASS]
  [51] (instance)  event trigger - test histogram trigger   [FAIL]
  [52] (instance)  event trigger - test multiple histogram triggers [PASS]

  # of passed:  46
  # of failed:  4
  # of unresolved:  0
  # of untested:  1
  # of unsupported:  1
  # of xfailed:  0
  # of undefined(test bug):  0
  not ok 1..1 selftests:  ftracetest [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/ftrace'
  make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests'

  ProblemType: Bug
  Dist

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[mattei mason]

I am using kubuntu 19.09 and  intel HD sound drivers with nvidia , was
working perfectly.

I tried, ubuntu 20.04 live , my sound drivers was not working. So I
thought there is driver issues with sound.


today I updated my kubuntu and I have 2 kernels

My sound drivers works,  has no problem with kernel:
5.3.0-40 (good)

Dumb Audio (no sound at all) in
5.3.0-45 (problem)

Input : intel smart sound Technology TSS
output : Realtek High Defination audio.

So now in the boot of Grub, I choose advance, then old kernel..
Sound just works fine that way.

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[knossos456]

Noting to do with the subject nor launchpad.
Please use normal Ubuntu forum for help

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact] 
  Firmware update of radeon/oland_rlc.bin breaks some radeon cards.

  [Fix]
  Revert the new firmware.

  [Regression Potential]
  Low. The old firmware has been used for a long time.

  === Original Bug Report ===

  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[mattei mason]

Additionally : I tried 5.3.0-42


My sound drivers works, has no problem with kernel:
5.3.0-40 (good)

Dumb Audio (no sound at all) in
5.3.0-42 (problem)
5.3.0-45 (problem)

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

[Hui Wang]

Thanks BinLi.

I just verified the libasoud2-1.1.9-0ubuntu1.3 for Eoan on a Lenovo X1C7
machine.

enable the pre-released updates (eoan-proposed) from software & updates
sudo apt-get update
sudo apt install linux-image-5.3.0-46-generic 
linux-modules-extra-5.3.0-46-generic
sudo apt install libasound2
reboot
run dpkg --list to check libasound2, they are all 1.1.9-0ubuntu1.3
and dmic works well on this machine, speaker also works.

Verified done on Eoan.


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

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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

[Kernel-packages] [Bug 1870060] Re: bluetoothd never leaves dumps/crash files when it crashes

[Brian Murray]

There are bluetoothd crashes in the Error Tracker but the most recent
release about which they were reported is 17.10.

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

Title:
  bluetoothd never leaves dumps/crash files when it crashes

Status in bluez package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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

[Kernel-packages] [Bug 1870060] Re: bluetoothd never leaves dumps/crash files when it crashes

[Brian Murray]

Killing bluetoothd with signall 11 on Ubuntu 18.04 LTS I was able to
create and submit a crash report to the Error Tracker.

https://errors.ubuntu.com/oops/88ed113a-7415-11ea-98e4-fa163e102db1

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

Title:
  bluetoothd never leaves dumps/crash files when it crashes

Status in bluez package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Marcelo Cerri]

Hi.

Do you know if the problem happens with other kernel versions such as
4.15 or if it didn't use to happen before?

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor

[Matthieu Clemenceau]

@Francis,

Yes, unfortunately. I just updated this morning to 5.4.0-21 #25 
I tried two different reboot without success.
Let me know if there's anything else you would need or more traces.

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

Title:
  System Display black screen on reboot or after a clean shutdown with
  USB-C Dock Monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running focal devel and the latest kernel (see proc version below)

  Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version
  9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7
  18:13:06 UTC 2020

  Dock Monitor is supported very well with multiple usb devices plugged
  on the monitor.

  However on reboot I face a black screen with no ability to enter my FDE 
password.
  Both my Laptop screen and the attached usb-c display nothing
  I have to hard power off and reboot without the USB-C monitor plugged in.

  Otherwise A reboot cycle with the usb-c unplugged works perfectly.

  Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic 
without success. I would be happy to provide much more debugging information. I 
will attach then to the launchpad Bug #
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC0:  mclemenceau   2988 F pulseaudio
   /dev/snd/controlC1:  mclemenceau   2988 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-05 (64 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-18-generic N/A
   linux-backports-modules-5.4.0-18-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.41
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2TV18AS#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache

[Mauricio Faria de Oliveira]

Hi Sebastian,

Thanks for reporting this bug.
It indeed seems related to bcache per the stack trace in the screenshot.

Could you please collect and upload a sosreport of the failing system
(w/ any kernel version.)

$ sudo sosreport --batch --case-id lp1867916

This should generate a /tmp/sosreport-* tarball, mentioned in the
output.

Thanks,
Mauricio

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
  does not boot any longer. It always crashes during boot with a kernel
  panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-88-generic N/A
   linux-backports-modules-4.15.0-88-generic  N/A
   linux-firmware 1.173.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.asset.tag: 0191525
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1870142] [NEW] Focal update: v5.4.29 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

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

mmc: core: Allow host controllers to require R1B for CMD6
mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
ACPI: PM: s2idle: Rework ACPI events synchronization
cxgb4: fix throughput drop during Tx backpressure
cxgb4: fix Txq restart check during backpressure
geneve: move debug check after netdev unregister
hsr: fix general protection fault in hsr_addr_is_self()
ipv4: fix a RCU-list lock in inet_dump_fib()
macsec: restrict to ethernet devices
mlxsw: pci: Only issue reset when system is ready
mlxsw: spectrum_mr: Fix list iteration in error path
net/bpfilter: fix dprintf usage for /dev/kmsg
net: cbs: Fix software cbs to consider packet sending time
net: dsa: Fix duplicate frames flooded by learning
net: dsa: mt7530: Change the LINK bit to reflect the link status
net: dsa: tag_8021q: replace dsa_8021q_remove_header with __skb_vlan_pop
net: ena: Add PCI shutdown handler to allow safe kexec
net: mvneta: Fix the case where the last poll did not process all rx
net/packet: tpacket_rcv: avoid a producer race condition
net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
net: phy: mdio-bcm-unimac: Fix clock handling
net: phy: mdio-mux-bcm-iproc: check clk_prepare_enable() return value
net: qmi_wwan: add support for ASKEY WWHC050
net/sched: act_ct: Fix leak of ct zone template on replace
net_sched: cls_route: remove the right filter from hashtable
net_sched: hold rtnl lock in tcindex_partial_destroy_work()
net_sched: keep alloc_hash updated after hash allocation
net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
r8169: re-enable MSI on RTL8168c
slcan: not call free_netdev before rtnl_unlock in slcan_open
tcp: also NULL skb->dev when copy was needed
tcp: ensure skb->dev is NULL before leaving TCP stack
tcp: repair: fix TCP_QUEUE_SEQ implementation
vxlan: check return value of gro_cells_init()
bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
bnxt_en: Free context memory after disabling PCI in probe error path.
bnxt_en: Reset rings if ring reservation fails during open()
net: ip_gre: Separate ERSPAN newlink / changelink callbacks
net: ip_gre: Accept IFLA_INFO_DATA-less configuration
hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
hsr: add restart routine into hsr_get_node_list()
hsr: set .netnsok flag
net/mlx5: DR, Fix postsend actions write length
net/mlx5e: Enhance ICOSQ WQE info fields
net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
net/mlx5e: Do not recover from a non-fatal syndrome
cgroup-v1: cgroup_pidlist_next should update position index
nfs: add minor version to nfs_server_key for fscache
cpupower: avoid multiple definition with gcc -fno-common
drivers/of/of_mdio.c:fix of_mdiobus_register()
cgroup1: don't call release_agent when it is ""
dt-bindings: net: FMan erratum A050385
arm64: dts: ls1043a: FMan erratum A050385
fsl/fman: detect FMan erratum A050385
drm/amd/display: update soc bb for nv14
drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
drm/exynos: Fix cleanup of IOMMU related objects
iommu/vt-d: Silence RCU-list debugging warnings
s390/qeth: don't reset default_out_queue
s390/qeth: handle error when backing RX buffer
scsi: ipr: Fix softlockup when rescanning devices in petitboot
mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
dpaa_eth: Remove unnecessary boolean expression in dpaa_get_headroom
sxgbe: Fix off by one in samsung driver strncpy size arg
net: hns3: fix "tc qdisc del" failed issue
iommu/vt-d: Fix debugfs register reads
iommu/vt-d: Populate debugfs if IOMMUs are detected
iwlwifi: mvm: fix non-ACPI function
i2c: hix5hd2: add missed clk_disable_unprepare in remove
Input: raydium_i2c_ts - fix error codes in raydium_i2c_boot_trigger()
Input: fix stale timestamp on key autorepeat events
Input: synaptics - enable RMI on HP Envy 13-ad105ng
Input: avoid BIT() macro usage in the serio.h UAPI header
IB/rdmavt: Free kernel completion queue when done
RDMA/core: Fix missing error check on dev_set_name()
gpiolib: Fix irq_disable() semantics
RDMA/nl: Do not permit empty devices nam

[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76

[Guilherme G. Piccoli]

Hi yamato, thanks for the bug report! Does your system have secureboot
enabled? Also, can you test in a recent kernel, like 4.15.0-91?

Thanks in advance,


Guilherme

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

Title:
  kdump kernel can't be loaded using kernel 4.15.0-76

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Thank you for reading this report.
  This may caused by bugs in kernel, not in kdump. If so, I will report this to 
kernel team.
  I need your comment to solve this.

  [Impact]
  * Kdump kernel can't be loaded using linux kernel 4.15.0-76.

  [Environment]
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  uname:
  Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  Secure boot is enabled.

  Versions:
  * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1
  * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4

  [Test case]
  1)After OS booted, run systemctl status kdump-tools shows these messages 
below:

  
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago
    Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
   Main PID: 895 (code=exited, status=0/SUCCESS)

  Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format 
error
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * failed to load kdump kernel
  Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service.
  

  2)Run kexec directly:
  $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic 
root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic 
/boot/vmlinuz-4.15.0-64-generic

  Then,these messages are shown:
  Cannot open /proc/kcore: Operation not permitted
  Cannot read /proc/kcore: Operation not permitted
  Cannot load /boot/vmlinuz-4.15.0-76-generic

  On dmesg, these messages are shown:
  
  [  538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7
  

  3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can
  be loaded.

  $ sudo systemctl status kdump-tools
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago
   Main PID: 832 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
     CGroup: /system.slice/kdump-tools.service

  Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 25 13:39:02 ubuntu kdump-tools[832]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 25 13:39:03 ubuntu kdump-tools[832]:  * loaded kdump kernel
  Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel
  Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service.

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

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

[Kernel-packages] [Bug 1849178] Re: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients

[Po-Hsu Lin]

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

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

Title:
  upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file
  system clients

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

Bug description:
  This is occurring with both 18.04, and 16.04 w/ HWE.

  After upgrading the linux kernel image to 4.15.0-66, logging in with a
  user that has a cephfs home directory hangs. Dmesg reports the
  following:

  [  221.239709] general protection fault:  [#1] SMP PTI
  [  221.239712] Modules linked in: ceph libceph libcrc32c fscache vboxsf(OE) 
snd_intel8x0 snd_ac97_codec crct10dif_pclmul crc32_pclmul ac97_bus 
ghash_clmulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event snd_rawmidi 
aesni_intel aes_x86_64 vboxvideo(OE) joydev snd_seq snd_seq_device snd_timer 
crypto_simd ttm glue_helper snd drm_kms_helper input_leds cryptd 
intel_rapl_perf soundcore serio_raw vboxguest(OE) drm fb_sys_fops syscopyarea 
sysfillrect sysimgblt video mac_hid sch_fq_codel parport_pc ppdev lp parport 
sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid ahci psmouse libahci 
i2c_piix4 e1000 pata_acpi
  [  221.239746] CPU: 1 PID: 1795 Comm: kworker/1:4 Tainted: GW  OE
4.15.0-66-generic #75-Ubuntu
  [  221.239748] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
  [  221.239759] Workqueue: ceph-msgr ceph_con_workfn [libceph]
  [  221.239767] RIP: 0010:kmem_cache_alloc+0x81/0x1b0
  [  221.239769] RSP: 0018:b208812d7ae0 EFLAGS: 00010202
  [  221.239770] RAX: 0efb8a01a897ba8a RBX: 0efb8a01a897bfea RCX: 
001a
  [  221.239772] RDX: 0019 RSI: 01400040 RDI: 
4929e00040d0
  [  221.239773] RBP: b208812d7b10 R08: d2087fd040d0 R09: 
88de94ad6640
  [  221.239774] R10:  R11: e3f68484 R12: 
01400040
  [  221.239775] R13: 88de962eb800 R14: 0efb8a01a897ba8a R15: 
88de962eb800
  [  221.239777] FS:  () GS:88de9fd0() 
knlGS:
  [  221.239778] CS:  0010 DS:  ES:  CR0: 80050033
  [  221.239779] CR2: 5604162106a8 CR3: c5e0a004 CR4: 
000606e0
  [  221.239782] DR0:  DR1:  DR2: 

  [  221.239783] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  221.239784] Call Trace:
  [  221.239792]  ? ceph_alloc_inode+0x1d/0x3b0 [ceph]
  [  221.239798]  ceph_alloc_inode+0x1d/0x3b0 [ceph]
  [  221.239801]  alloc_inode+0x20/0x90
  [  221.239804]  iget5_locked+0xea/0x1f0
  [  221.239809]  ? ceph_d_init+0x45/0x60 [ceph]
  [  221.239813]  ? ceph_ino_compare+0x30/0x30 [ceph]
  [  221.239817]  ? ceph_mount+0x8a0/0x8a0 [ceph]
  [  221.239822]  ceph_get_inode+0x36/0xc0 [ceph]
  [  221.239827]  ceph_readdir_prepopulate+0x4e9/0xcb0 [ceph]
  [  221.239834]  handle_reply+0x954/0xcc0 [ceph]
  [  221.239841]  dispatch+0xcf/0xb40 [ceph]
  [  221.239843]  ? __switch_to_asm+0x35/0x70
  [  221.239845]  ? __switch_to_asm+0x41/0x70
  [  221.239847]  ? __switch_to_asm+0x35/0x70
  [  221.239848]  ? __switch_to_asm+0x41/0x70
  [  221.239850]  ? __switch_to_asm+0x35/0x70
  [  221.239856]  try_read+0x64a/0x11a0 [libceph]
  [  221.239858]  ? __switch_to_asm+0x41/0x70
  [  221.239860]  ? __switch_to_asm+0x35/0x70
  [  221.239861]  ? __switch_to_asm+0x41/0x70
  [  221.239863]  ? __switch_to_asm+0x35/0x70
  [  221.239864]  ? __switch_to_asm+0x41/0x70
  [  221.239866]  ? __switch_to_asm+0x35/0x70
  [  221.239871]  ceph_con_workfn+0xda/0x610 [libceph]
  [  221.239874]  process_one_work+0x1de/0x420
  [  221.239876]  worker_thread+0x32/0x410
  [  221.239878]  kthread+0x121/0x140
  [  221.239880]  ? process_one_work+0x420/0x420
  [  221.239881]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  221.239883]  ret_from_fork+0x35/0x40
  [  221.239885] Code: f4 5b 74 49 83 78 10 00 4d 8b 30 0f 84 00 01 00 00 4d 85 
f6 0f 84 f7 00 00 00 49 63 5f 20 49 8b 3f 48 8d 4a 01 4c 89 f0 4c 01 f3 <48> 33 
1b 49 33 9f 40 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 
  [  221.239913] RIP: kmem_cache_alloc+0x81/0x1b0 RSP: b208812d7ae0
  [  221.239914] ---[ end trace 35d882be2a72b80a ]---

  This happens across all workstations on our network that are upgraded
  to this kernel.

  This issue does not exist on 4.15.0-65, and downgrading to this kernel 
returns all affected workstations to usability.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory:

[Kernel-packages] [Bug 1870060] Re: bluetoothd never leaves dumps/crash files when it crashes

[Sebastien Bacher]

It's due to the system bluetooth.service unit using ProtectSystem=full, 
commenting that line from the service and doing
$ sudo systemctl stop blueetooth.service
$ sudo systemctl daemon-reload
$ sudo systemctl start blueetooth.service

and sending the sig11 makes apport trigger

Note that systemd-coredump doesn't have this problem and register a
backtrace in the journal even with ProtectSystem in use, which suggests
it's an apport limitation

** Summary changed:

- bluetoothd never leaves dumps/crash files when it crashes
+ systemd ProtectSystem makes apport fail

** Summary changed:

- systemd ProtectSystem makes apport fail
+ systemd ProtectSystem makes apport fail (impacts bluez)

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

Title:
  systemd ProtectSystem makes apport fail (impacts bluez)

Status in bluez package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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

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

[Kernel-packages] [Bug 1869947] Re: nvme_fc patch prevents unloading of lpfc module in both BFS and non-BFS scenarios

[Jeff Lane]

** Summary changed:

- revert patch that introduces bug that prevents lpfc driver unloading
+ nvme_fc patch prevents unloading of lpfc module in both BFS and non-BFS 
scenarios

** Description changed:

  [IMPACT]
  This upstream commit:
  
- 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f nvme_fc: add module to ops
- template to allow module references
+ 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f 
+ nvme_fc: add module to ops template to allow module references
  
- was pulled into Focal as part of this bug:
- https://bugs.launchpad.net/bugs/1860125 and this commit into Focal:
+ was pulled into Focal as part of this bug: 
+ https://bugs.launchpad.net/bugs/1860125 
+ 
+ and this commit into Focal: 
  a7441301b20dc8a7772972a092968bb353b7a642
  
  This patch was added to prevent the unloading of lpfc driver when doing
  NVMe BFS booting.  Broadcom has identified that this patch introduces a
  bug that prevents unloading of lpfc driver in the non-BFS case as well.
  
  Because of this, they have asked that we revert this patch and remove it
  from our kernel, and also said that they are working on a patch upstream
  to revert this as well.  As it may not land upstream in time to meet
  kernel freeze for Focal, I'm providing a patch to revert this commit in
  Focal.
  
  [FIXES]
  To resolve, revert the following commit ID in the Focal Tree:
  a7441301b20dc8a7772972a092968bb353b7a642
  nvme_fc: add module to ops template to allow module references
  
  BugLink: https://bugs.launchpad.net/bugs/1860125
  
  [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ]
  
  In nvme-fc: it's possible to have connected active controllers
  and as no references are taken on the LLDD, the LLDD can be
  unloaded.  The controller would enter a reconnect state and as
  long as the LLDD resumed within the reconnect timeout, the
  controller would resume.  But if a namespace on the controller
  is the root device, allowing the driver to unload can be problematic.
  To reload the driver, it may require new io to the boot device,
  and as it's no longer connected we get into a catch-22 that
  eventually fails, and the system locks up.
  
  Fix this issue by taking a module reference for every connected
  controller (which is what the core layer did to the transport
  module). Reference is cleared when the controller is removed.
  
  Acked-by: Himanshu Madhani 
  Reviewed-by: Christoph Hellwig 
  Signed-off-by: James Smart 
  Signed-off-by: Keith Busch 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Paolo Pisati 
  
  An updated tree with the commit reverted can be found here:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1869947-revert-lpfc-patch
  
  [REGRESSION RISK]
  Regression risk is low as this is a new patch introduced upstream and synced 
into a development release.  The patch only exists in our tree from 
Ubuntu-5.4-5.4.0-13.16 onwards and does not affect older kernels.

** Summary changed:

- nvme_fc patch prevents unloading of lpfc module in both BFS and non-BFS 
scenarios
+ nvme_fc patch prevents unloading lpfs module in both BFS and non-BFS scenarios

** Summary changed:

- nvme_fc patch prevents unloading lpfs module in both BFS and non-BFS scenarios
+ Revert "nvme_fc: add module to ops template to allow module references"

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

Title:
  Revert "nvme_fc: add module to ops template to allow module
  references"

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [IMPACT]
  This upstream commit:

  863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f
  nvme_fc: add module to ops template to allow module references

  was pulled into Focal as part of this bug:
  https://bugs.launchpad.net/bugs/1860125

  and this commit into Focal:
  a7441301b20dc8a7772972a092968bb353b7a642

  This patch was added to prevent the unloading of lpfc driver when
  doing NVMe BFS booting.  Broadcom has identified that this patch
  introduces a bug that prevents unloading of lpfc driver in the non-BFS
  case as well.

  
  Because of this, they have asked that we revert this patch and remove it from 
our kernel. Additionally, Broadcome have also said that they are working on a  
patch upstream to revert this as well. As it may not land upstream in time to 
meet kernel freeze for Focal, I'm providing a patch
  to revert this commit directly.

  
  [FIXES]
  To resolve, revert the following commit ID in the Focal Tree:
  a7441301b20dc8a7772972a092968bb353b7a642
  nvme_fc: add module to ops template to allow module references

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

  [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ]

  In nvme-fc: it's possible to have connected active controllers
  and as no references are taken on the LLDD, the LLDD c

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

[roland]

@hui.wang and @logix2

I'm on Linux MiX 5.3.0-46-generic without the workaround.
It detects my card as: sof-skl_hda_car - sof-skl_hda_card

I had to run 'alsamixer' in the commandline, select 'capture' i.e. F4
and turn Mic Boost up and down.

And.. The mic worked only once. After one capture was complete I
couldn't get other captures to work.

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

Title:
  PCI/internal sound card not detected

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

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

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

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

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

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

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

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

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


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

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

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

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

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

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

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

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

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

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



  Probably a kernel bug.

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

  The relevant dmesg message is:

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

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

[Kernel-packages] [Bug 1869947] Re: Revert "nvme_fc: add module to ops template to allow module references"

[Jeff Lane]

** Description changed:

  [IMPACT]
  This upstream commit:
  
- 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f 
+ 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f
  nvme_fc: add module to ops template to allow module references
  
- was pulled into Focal as part of this bug: 
- https://bugs.launchpad.net/bugs/1860125 
+ was pulled into Focal as part of this bug:
+ https://bugs.launchpad.net/bugs/1860125
  
- and this commit into Focal: 
+ and this commit into Focal:
  a7441301b20dc8a7772972a092968bb353b7a642
  
  This patch was added to prevent the unloading of lpfc driver when doing
  NVMe BFS booting.  Broadcom has identified that this patch introduces a
  bug that prevents unloading of lpfc driver in the non-BFS case as well.
  
- Because of this, they have asked that we revert this patch and remove it
- from our kernel, and also said that they are working on a patch upstream
- to revert this as well.  As it may not land upstream in time to meet
- kernel freeze for Focal, I'm providing a patch to revert this commit in
- Focal.
+ 
+ Because of this, they have asked that we revert this patch and remove it from 
our kernel. Additionally, Broadcome have also said that they are working on a  
patch upstream to revert this as well. As it may not land upstream in time to 
meet kernel freeze for Focal, I'm providing a patch
+ to revert this commit directly.
+ 
  
  [FIXES]
  To resolve, revert the following commit ID in the Focal Tree:
  a7441301b20dc8a7772972a092968bb353b7a642
  nvme_fc: add module to ops template to allow module references
  
  BugLink: https://bugs.launchpad.net/bugs/1860125
  
  [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ]
  
  In nvme-fc: it's possible to have connected active controllers
  and as no references are taken on the LLDD, the LLDD can be
  unloaded.  The controller would enter a reconnect state and as
  long as the LLDD resumed within the reconnect timeout, the
  controller would resume.  But if a namespace on the controller
  is the root device, allowing the driver to unload can be problematic.
  To reload the driver, it may require new io to the boot device,
  and as it's no longer connected we get into a catch-22 that
  eventually fails, and the system locks up.
  
  Fix this issue by taking a module reference for every connected
  controller (which is what the core layer did to the transport
  module). Reference is cleared when the controller is removed.
  
  Acked-by: Himanshu Madhani 
  Reviewed-by: Christoph Hellwig 
  Signed-off-by: James Smart 
  Signed-off-by: Keith Busch 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Paolo Pisati 
  
  An updated tree with the commit reverted can be found here:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1869947-revert-lpfc-patch
  
  [REGRESSION RISK]
  Regression risk is low as this is a new patch introduced upstream and synced 
into a development release.  The patch only exists in our tree from 
Ubuntu-5.4-5.4.0-13.16 onwards and does not affect older kernels.

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

Title:
  Revert "nvme_fc: add module to ops template to allow module
  references"

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [IMPACT]
  This upstream commit:

  863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f
  nvme_fc: add module to ops template to allow module references

  was pulled into Focal as part of this bug:
  https://bugs.launchpad.net/bugs/1860125

  and this commit into Focal:
  a7441301b20dc8a7772972a092968bb353b7a642

  This patch was added to prevent the unloading of lpfc driver when
  doing NVMe BFS booting.  Broadcom has identified that this patch
  introduces a bug that prevents unloading of lpfc driver in the non-BFS
  case as well.

  
  Because of this, they have asked that we revert this patch and remove it from 
our kernel. Additionally, Broadcome have also said that they are working on a  
patch upstream to revert this as well. As it may not land upstream in time to 
meet kernel freeze for Focal, I'm providing a patch
  to revert this commit directly.

  
  [FIXES]
  To resolve, revert the following commit ID in the Focal Tree:
  a7441301b20dc8a7772972a092968bb353b7a642
  nvme_fc: add module to ops template to allow module references

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

  [ Upstream commit 863fbae929c7a5b64e96b8a3ffb34a29eefb9f8f ]

  In nvme-fc: it's possible to have connected active controllers
  and as no references are taken on the LLDD, the LLDD can be
  unloaded.  The controller would enter a reconnect state and as
  long as the LLDD resumed within the reconnect timeout, the
  controller would resume.  But if a namespace on the controller
  is the root device, allowing the driver to unload can be pr

[Kernel-packages] [Bug 1870142] Re: Focal update: v5.4.29 upstream stable release

[Kamal Mostafa]

Note:  The commit "net: Fix CONFIG_NET_CLS_ACT=n and
CONFIG_NFT_FWD_NETDEV={y, m} build" would break the wireguard dkms build
in focal.  Resolution t.b.d.

https://lists.ubuntu.com/archives/kernel-team/2020-April/108668.html

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

Title:
  Focal update: v5.4.29 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mmc: core: Allow host controllers to require R1B for CMD6
  mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
  mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
  mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
  mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
  ACPI: PM: s2idle: Rework ACPI events synchronization
  cxgb4: fix throughput drop during Tx backpressure
  cxgb4: fix Txq restart check during backpressure
  geneve: move debug check after netdev unregister
  hsr: fix general protection fault in hsr_addr_is_self()
  ipv4: fix a RCU-list lock in inet_dump_fib()
  macsec: restrict to ethernet devices
  mlxsw: pci: Only issue reset when system is ready
  mlxsw: spectrum_mr: Fix list iteration in error path
  net/bpfilter: fix dprintf usage for /dev/kmsg
  net: cbs: Fix software cbs to consider packet sending time
  net: dsa: Fix duplicate frames flooded by learning
  net: dsa: mt7530: Change the LINK bit to reflect the link status
  net: dsa: tag_8021q: replace dsa_8021q_remove_header with __skb_vlan_pop
  net: ena: Add PCI shutdown handler to allow safe kexec
  net: mvneta: Fix the case where the last poll did not process all rx
  net/packet: tpacket_rcv: avoid a producer race condition
  net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
  net: phy: mdio-bcm-unimac: Fix clock handling
  net: phy: mdio-mux-bcm-iproc: check clk_prepare_enable() return value
  net: qmi_wwan: add support for ASKEY WWHC050
  net/sched: act_ct: Fix leak of ct zone template on replace
  net_sched: cls_route: remove the right filter from hashtable
  net_sched: hold rtnl lock in tcindex_partial_destroy_work()
  net_sched: keep alloc_hash updated after hash allocation
  net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
  NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
  r8169: re-enable MSI on RTL8168c
  slcan: not call free_netdev before rtnl_unlock in slcan_open
  tcp: also NULL skb->dev when copy was needed
  tcp: ensure skb->dev is NULL before leaving TCP stack
  tcp: repair: fix TCP_QUEUE_SEQ implementation
  vxlan: check return value of gro_cells_init()
  bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
  bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
  bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
  bnxt_en: Free context memory after disabling PCI in probe error path.
  bnxt_en: Reset rings if ring reservation fails during open()
  net: ip_gre: Separate ERSPAN newlink / changelink callbacks
  net: ip_gre: Accept IFLA_INFO_DATA-less configuration
  hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
  hsr: add restart routine into hsr_get_node_list()
  hsr: set .netnsok flag
  net/mlx5: DR, Fix postsend actions write length
  net/mlx5e: Enhance ICOSQ WQE info fields
  net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
  net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
  net/mlx5e: Do not recover from a non-fatal syndrome
  cgroup-v1: cgroup_pidlist_next should update position index
  nfs: add minor version to nfs_server_key for fscache
  cpupower: avoid multiple definition with gcc -fno-common
  drivers/of/of_mdio.c:fix of_mdiobus_register()
  cgroup1: don't call release_agent when it is ""
  dt-bindings: net: FMan erratum A050385
  arm64: dts: ls1043a: FMan erratum A050385
  fsl/fman: detect FMan erratum A050385
  drm/amd/display: update soc bb for nv14
  drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
  drm/exynos: Fix cleanup of IOMMU related objects
  iommu/vt-d: Silence RCU-list debugging warnings
  s390/qeth: don't reset default_out_queue
  s390/qeth: handle error when backing RX buffer
  scsi: ipr: Fix softlockup when rescanning devices in petitboot
  mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
  dpaa_eth: Remove unnecessary boolean expression in dpaa_ge

[Kernel-packages] [Bug 1870180] [NEW] Sound output distorted with Intel Z97-HD3

[José Santos Salvador]

Public bug reported:

I get horribly cracking sound and distortion with my mb Gigabyte
Z97-HD3. This MB is using the Realtek ALC1150 Chipset. I run linux
kernel 5.5 and Ubuntu 18 and I tried all the answers from this post
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421 but it
didnt work.

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

Title:
  Sound output distorted with Intel Z97-HD3

Status in linux package in Ubuntu:
  New

Bug description:
  I get horribly cracking sound and distortion with my mb Gigabyte
  Z97-HD3. This MB is using the Realtek ALC1150 Chipset. I run linux
  kernel 5.5 and Ubuntu 18 and I tried all the answers from this post
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421 but it
  didnt work.

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

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

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

[Ubuntu Kernel Bot]

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

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 1870180

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

Title:
  Sound output distorted with Intel Z97-HD3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I get horribly cracking sound and distortion with my mb Gigabyte
  Z97-HD3. This MB is using the Realtek ALC1150 Chipset. I run linux
  kernel 5.5 and Ubuntu 18 and I tried all the answers from this post
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421 but it
  didnt work.

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

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

[Brian Murray]

@vmclark - Does this affect your ability to install or use the system at
all?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1321421] Re: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97

[José Santos Salvador]

I use Ubuntu 18 with kernel 5.5 but it didnt work

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

Title:
  8086:8ca0 Sound output distorted/unusable with Intel Z97/H97

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I get horribly cracking sound and distortion with my ne AS Rock
  Fatal1ty H97 Performance Mainboard. This MB is using PuritySound 2
  Engine powered by the Realtek ALC1150 Chipset. Here is some ALSA Info:
  http://www.alsa-
  project.org/db/?f=44b12e252a2cf7ebb75ab3e23d5cef072af6c328

  Following commit fixes this problem:
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound/+/77f07800cb456bed6e5c345e6e4e83e8eda62437

  WORKAROUND: Create a modprobe.d file with command:
  echo "options snd-hda-intel vid=8086 pid=8ca0 snoop=0" | sudo tee 
/etc/modprobe.d/fix-sound-intel97.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 20 21:03:18 2014
  InstallationDate: Installed on 2014-05-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H97 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/28/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ben1445 F pulseaudio
   /dev/snd/controlC0:  ben1445 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=f35e4cc7-52c2-4fe7-9e4b-405280ed487f
  InstallationDate: Installed on 2014-05-20 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H97 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/28/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1870180] Re: Sound output distorted with Intel Z97-HD3

[José Santos Salvador]

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

** This bug has been marked a duplicate of bug 1870185
   [Z97-HD3, Intel Haswell HDMI, Digital Out, HDMI] Sound is distorted

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

Title:
  Sound output distorted with Intel Z97-HD3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I get horribly cracking sound and distortion with my mb Gigabyte
  Z97-HD3. This MB is using the Realtek ALC1150 Chipset. I run linux
  kernel 5.5 and Ubuntu 18 and I tried all the answers from this post
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421 but it
  didnt work.

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

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

[Kernel-packages] [Bug 1870140] [NEW] Laptop freeze after unplug power-AC (USB-C)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

## Power adapter plugged in,  charging goes well

[ 1018.621820] asus_wmi: Unknown key cf pressed


## Power adapter unplugged, after few moments system freeze

[  567.444810] BUG: kernel NULL pointer dereference, address: 0080
[  567.444819] #PF: supervisor read access in kernel mode
[  567.444823] #PF: error_code(0x) - not-present page
[  567.444827] PGD 0 P4D 0 
[  567.444834] Oops:  [#1] PREEMPT SMP PTI
[  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
[  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
[  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
[  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
[  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
[  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
[  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 000efd00
[  567.444886] RDX:  RSI: 0001 RDI: 0008
[  567.444889] RBP:  R08:  R09: c9477ce0
[  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 88844685c418
[  567.444895] R13: 0001 R14: 88844685c2a8 R15: 
[  567.444900] FS:  () GS:88844ec0() 
knlGS:
[  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
[  567.444906] CR2: 0080 CR3: 0240a006 CR4: 003606f0
[  567.444909] Call Trace:
[  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
[  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
[  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
[  567.444949]  ? kmem_cache_free+0x22a/0x290
[  567.444960]  process_one_work+0x1e1/0x3d0
[  567.444968]  worker_thread+0x4a/0x3d0
[  567.444976]  kthread+0xfb/0x130
[  567.444983]  ? process_one_work+0x3d0/0x3d0
[  567.444988]  ? kthread_park+0x90/0x90
[  567.444998]  ret_from_fork+0x35/0x40
[  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
[  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
[  567.445112] CR2: 0080
[  567.445117] ---[ end trace a50cf550f0b4969a ]---
[  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
[  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
[  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
[  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 000efd00
[  567.445143] RDX:  RSI: 0001 RDI: 0008
[  567.445146] RBP:  R08:  R09: c9477ce0
[  567.445149] R10: 888443e9f218 R11: 88844edeb478 R12: 88844685c418
[  567.445152] R13: 0001 R14: 88844685c2a8 R15: 
[  567.445156] FS:  () GS:88844ec0() 
knlGS:
[  567.445159] CS:  0010 DS:  ES:  CR0: 80050033
[  567.445163] CR2: 0080 CR3: 0240a006 CR4: 003606f0

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


** Tags: asus bot-comment kernel-bug usb-c
-- 
Laptop freeze after unplug power-AC (USB-C)
https://bugs.launchpad.net/bugs/1870140
You 

[Kernel-packages] [Bug 1869996] Re: Hibernation can NOT work due to incorrect RESUME=

[Joseph Salisbury]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools

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

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

Title:
  Hibernation can NOT work due to incorrect RESUME=

Status in initramfs-tools package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
  build) these lines are missing:

  --- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
  +++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
  @@ -163,6 +163,10 @@
  ;;
  resume=*)
  RESUME="${x#resume=}"
  +   case $RESUME in
  +   UUID=*)
  +RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
  +   esac
  ;;
  resume_offset=*)
  resume_offset="${x#resume_offset=}"

  As a result, hibernation can not work: the saved state in the swap
  partition is lost and no resume happens.

  The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" kernel parameter for hibernation, due to the missing
  lines, the variable 'resume' in a later place in "/usr/share
  /initramfs-tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" rather than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-
  014f09ab0a9c". Next, in /usr/share/initramfs-tools/scripts/local-
  premount/resume:

  DEV=$(readlink "$resume")
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read -r MAJMIN < "$DEV"
  fi
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and 
then $MAJMIN is empty and
  we "exit 1", so no resume can happen!

  
  Not sure why the 4 lines are removed in Ubuntu 20.04...

  
  PS, this is my version info:

  root@localhost:~# dpkg-query -s initramfs-tools-core
  Package: initramfs-tools-core
  Status: install ok installed
  Priority: optional
  Section: utils
  Installed-Size: 271
  Maintainer: Ubuntu Developers 
  Architecture: all
  Multi-Arch: foreign
  Source: initramfs-tools
  Version: 0.136ubuntu1
  Replaces: initramfs-tools (<< 0.121~)
  Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~), initramfs-tools-bin (= 
0.136ubuntu1), klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), lz4, kmod, udev, 
coreutils (>= 8.24), logsave | e2fsprogs (<< 1.45.3-1~)
  Suggests: bash-completion
  Breaks: busybox-initramfs (<< 1:1.30.1-4ubuntu5~), initramfs-tools (<< 0.121~)
  Conffiles:
   /etc/initramfs-tools/initramfs.conf 4ec999d424d01b9ca685e65ba0f22a13
  Description: generic modular initramfs generator (core tools)
   This package contains the mkinitramfs program that can be used to
   create a bootable initramfs for a Linux kernel.  The initramfs should
   be loaded along with the kernel and is then responsible for mounting
   the root filesystem and starting the main init system.
  Original-Maintainer: Debian kernel team 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869996/+subscriptions

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

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[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/1870140

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  New

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.445143] RDX:  RSI: 0001 RDI: 
0008
  [  567.445146] RBP:  R08:  R09: 
c9477ce0
  [  567.445149] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.445152] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.445156] FS:  () GS:88844ec0(000

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[Kai-Heng Feng]

commit d16e7b62c5adcd13832c6b0ba364c3468d21b856
Author: Heikki Krogerus 
Date:   Wed Mar 11 16:00:05 2020 +0300

usb: typec: ucsi: displayport: Fix NULL pointer dereference

It has "Cc: sta...@vger.kernel.org" so every stable kernel will get the
fix soon.

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.445143] RDX:  RSI: 0001 RDI: 
0008
  [  567.445146] RBP:  R08:  R09: 
c9477ce0
  [  567.44514

[Kernel-packages] [Bug 1870189] [NEW] initramfs does not get loaded

[Joseph Salisbury]

Public bug reported:

A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.

Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.

It turns out by default, initramfs does not get loaded:

/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
  linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
  initrd/boot/initrd.img-5.6.0-050600-generic
else
  linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
  #Dexuan: here the initrd line is missing!
fi
initrdfail
}


As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots
for the 2nd time, the kernel should successfully boot up.  Next, when
the kernel boots for the 3rd time, it panics again since the userspace
program resets initrdfail to 0, and next time when the kernel boots, it
can boot up successfully -- this “panic/success/panic/success” pattern
repeats forever…


The linux-azure kernels are not affected since they have the vmbus driver and 
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.


It looks the setting may be intentional, but we should not assume a customer 
kernel must have the necessary vmbus/storage drivers built-in. 

This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 
as well?) on Azure. 
We installed a Ubuntu  20.04 VM from the .iso file from 
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub 
issue.

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

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

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

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

Title:
  initramfs does not get loaded

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

Bug description:
  A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
  20.04 by “do-release-upgrade –d”.

  Then the latest Ubuntu v5.6 kernel was installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
  reboot was performed, a panic with the v5.6 kernel occured because the
  rootfs can not be found.

  It turns out by default, initramfs does not get loaded:

  /boot/grub/grub.cfg:
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-3d2737e8-
  b95a-42bf-bac1-bb6fb4cda87f' {
  …
  if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
  else
linux /boot/vmlinuz-5.6.0-050600-generic 
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro  console=tty1 
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled 
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
  fi
  initrdfail
  }

  
  As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, 
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit 
the “fail to mount rootfs” panic and the kernel will automatically reboot….   

  Also, the “initrdfail” here marks initrdfail=1, so when the kernel
  boots for the 2nd time, the kernel should successfully boot up.  Next,
  when the kernel boots for the 3rd time, it panics again since the
  userspace program resets initrdfail to 0, and next time when the
  kernel bo

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

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[schmidt]

I use ubuntu 18.04, today I installed -46 kernel, unfortunately no sound

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[mCoRN]

This is log after i'm pligging-in USB-C universal dock station

I tested this dock with my Dell XPS 9360 (Ubuntu 19.10) and al work
properly

I can't send information using Apport, because Ubuntu freezes instantly


If you need any additional information, just ask what do you need, and i 
provide you this information =)

** Attachment added: "bugbug.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870140/+attachment/5344373/+files/bugbug.log

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[mCoRN]

Thanks for your answer,

Here is the link to the RadHat bugzilla with same issue
https://bugzilla.redhat.com/show_bug.cgi?id=1785972

It's affected on many ASUS laptops

Last comment contains useful information IMHO
"As far as I know, the issue isn't present in 4.x kernels, though I've only 
tested that in other distros. Solus is the only distro I've tested that didn't 
crash in a 5.x kernel."

I tested Solus os, and get this BUG, But solus not freeze permanently.
After you unplug power adapted, dmesg show the same error, and after 
5-10minutes touchpad and touchscreen became unavailable, new applications won't 
start, lsusb not return any output, and after 5 more minutes system freeze

If i trying to connect USB-C universal dock-station, notebook even wont
get power, dmesg show connection and after few seconds - disconnection.


** Bug watch added: Red Hat Bugzilla #1785972
   https://bugzilla.redhat.com/show_bug.cgi?id=1785972

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 008

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[mCoRN]

This is log after unplugging power supply

** Attachment added: "bug.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870140/+attachment/5344361/+files/bug.log

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.445143] RDX:  RSI: 0001 RDI: 
0008
  [  567.445146] RBP:  R08:  R09: 
c9477ce0
  [  567.445149] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.445152]

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[schmidt]

I've to revise it was to fast, I also updated pulseaudio, now I have
also no sound on the -40 kernel, argh!

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[schmidt]

installed packages

** Attachment added: "Screenshot_20200401_195341.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+attachment/5344380/+files/Screenshot_20200401_195341.png

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[schmidt]

so, now again, I restored my pc: -40 works again, -46 no sound. I put a
screenshot of installed packages with pulseaudio, it seems also some
problems.

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1870014] Re: task blocked too long

[Jerry Quinn]

On a laptop with Ubuntu 16.04, this same device behaves as expected.

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

Title:
  task blocked too long

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I plugged in the EasyCap device, then started VLC to read from it.
  Nothing worked, and I saw the following call traces from the kernel:

  
  Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB 
device number 41 using xhci_hcd
  Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor 
read/64, error -71
  Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor 
read/64, error -71
  Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power 
cycle
  Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot 
enable. Maybe the USB cable is bad?
  Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot 
enable. Maybe the USB cable is bad?
  Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to 
enumerate USB device
  Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB 
device number 44 using xhci_hcd
  Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 
altsetting 1 bulk endpoint 0x83 has invalid maxpa
  cket 256
  Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device 
found, idVendor=1b71, idProduct=3002
  Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device 
strings: Mfr=3, Product=4, SerialNumber=2
  Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007
  Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: 
fushicai
  Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 
3002
  Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai 
USBTV007 Audio-Video Grabber
  Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, 
device number 44
  Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long 
(3978 > 3967), lowering kernel.perf_event_max_sam
  ple_rate to 50250
  Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 
blocked for more than 120 seconds.
  Mar 31 23:55:36 cerberus kernel: [50024.968512]   Tainted: G  IOE 
   4.15.0-94-generic #95-Ubuntu
  Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251  
1 0x
  Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace:
  Mar 31 23:55:36 cerberus kernel: [50024.968535]  __schedule+0x24e/0x880
  Mar 31 23:55:36 cerberus kernel: [50024.968539]  schedule+0x2c/0x80
  Mar 31 23:55:36 cerberus kernel: [50024.968542]  
schedule_preempt_disabled+0xe/0x10
  Mar 31 23:55:36 cerberus kernel: [50024.968547]  
__mutex_lock.isra.5+0x276/0x4e0
  Mar 31 23:55:36 cerberus kernel: [50024.968551]  
__mutex_lock_slowpath+0x13/0x20
  Mar 31 23:55:36 cerberus kernel: [50024.968554]  ? 
__mutex_lock_slowpath+0x13/0x20
  Mar 31 23:55:36 cerberus kernel: [50024.968557]  mutex_lock+0x2f/0x40
  Mar 31 23:55:36 cerberus kernel: [50024.968569]  _vb2_fop_release+0x29/0xa0 
[videobuf2_v4l2]
  Mar 31 23:55:36 cerberus kernel: [50024.968573]  vb2_fop_release+0x31/0x40 
[videobuf2_v4l2]
  Mar 31 23:55:36 cerberus kernel: [50024.968593]  v4l2_release+0x38/0x80 
[videodev]
  Mar 31 23:55:36 cerberus kernel: [50024.968600]  __fput+0xea/0x220
  Mar 31 23:55:36 cerberus kernel: [50024.968604]  fput+0xe/0x10
  Mar 31 23:55:36 cerberus kernel: [50024.968611]  task_work_run+0x9d/0xc0
  Mar 31 23:55:36 cerberus kernel: [50024.968620]  
exit_to_usermode_loop+0xc0/0xd0
  Mar 31 23:55:36 cerberus kernel: [50024.968623]  do_syscall_64+0x121/0x130
  Mar 31 23:55:36 cerberus kernel: [50024.968630]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447
  Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 
EFLAGS: 0293 ORIG_RAX: 0003
  Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX:  RBX: 
0064 RCX: 7f6411c26447
  Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX:  RSI: 
7f63da9bd930 RDI: 0064
  Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP:  R08: 
 R09: 
  Mar 31 23:55:36 cerberus kernel: [50024.968642] R10:  R11: 
0293 R12: 7f628d4c5fa0
  Mar 31 23:55:36 cerberus kernel: [50024.968644] R13:  R14: 
7f640422d381 R15: 7f63da9bd930
  Mar 31 23:55:36 cerberus kernel: [50024.968915] INFO: task kworker/5:1:25898 
blocked for more than 120 seconds.
  Mar 31 23:55:36 cerber

[Kernel-packages] [Bug 1870208] [NEW] adding GUI to Ubuntu Server 20.04 results in no log in screen

[Jerry Clement]

Public bug reported:

apt install ubuntu-desktop on Servers with embedded Matrox G200 Graphics
Controller issue

After install/reboot there is no gdm login displayed
Editing /etc/gdm3/custom.conf to force gdm to use Xorg instead of Wayland fixed 
the issue

Ubuntu 19.10 has the same problem
Same issue found installing the Desktop Version

Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery
mode


Conclusion being - should we try to fix this?

There may already be a fix in process
https://gitlab.gnome.org/GNOME/gdm/issues/364
Here are three proposals if the above does not pan out, one of these should 
work, Number 3 is preferred
1. Fix Wayland’s support for G200
2. Rip out the broken support for Matrox G200 in Wayland
3. Convince Canonical to blacklist the G200 from Wayland during install and 
force Xorg automatically

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


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

Title:
  adding GUI to Ubuntu Server 20.04 results in no log in screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  apt install ubuntu-desktop on Servers with embedded Matrox G200
  Graphics Controller issue

  After install/reboot there is no gdm login displayed
  Editing /etc/gdm3/custom.conf to force gdm to use Xorg instead of Wayland 
fixed the issue

  Ubuntu 19.10 has the same problem
  Same issue found installing the Desktop Version

  Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery
  mode

  
  Conclusion being - should we try to fix this?

  There may already be a fix in process
  https://gitlab.gnome.org/GNOME/gdm/issues/364
  Here are three proposals if the above does not pan out, one of these should 
work, Number 3 is preferred
  1. Fix Wayland’s support for G200
  2. Rip out the broken support for Matrox G200 in Wayland
  3. Convince Canonical to blacklist the G200 from Wayland during install and 
force Xorg automatically

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

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

[Kernel-packages] [Bug 1870208] Re: adding GUI to Ubuntu Server 20.04 results in no log in screen

[Michael Reed]

** Description changed:

- apt install ubuntu-desktop on Servers with embedded Matrox G200 Graphics 
Controller issue
+ apt install ubuntu-desktop on Servers with embedded Matrox G200 Graphics
+ Controller issue
+ 
  After install/reboot there is no gdm login displayed
  Editing /etc/gdm3/custom.conf to force gdm to use Xorg instead of Wayland 
fixed the issue
+ 
  Ubuntu 19.10 has the same problem
  Same issue found installing the Desktop Version
- Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery mode
+ 
+ Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery
+ mode
+ 
+ 
  Conclusion being - should we try to fix this?
+ 
  There may already be a fix in process
  https://gitlab.gnome.org/GNOME/gdm/issues/364
  Here are three proposals if the above does not pan out, one of these should 
work, Number 3 is preferred
- 1. Fix Wayland’s support for G200 
- 2. Rip out the broken support for Matrox G200 in Wayland 
+ 1. Fix Wayland’s support for G200
+ 2. Rip out the broken support for Matrox G200 in Wayland
  3. Convince Canonical to blacklist the G200 from Wayland during install and 
force Xorg automatically

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

Title:
  adding GUI to Ubuntu Server 20.04 results in no log in screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  apt install ubuntu-desktop on Servers with embedded Matrox G200
  Graphics Controller issue

  After install/reboot there is no gdm login displayed
  Editing /etc/gdm3/custom.conf to force gdm to use Xorg instead of Wayland 
fixed the issue

  Ubuntu 19.10 has the same problem
  Same issue found installing the Desktop Version

  Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery
  mode

  
  Conclusion being - should we try to fix this?

  There may already be a fix in process
  https://gitlab.gnome.org/GNOME/gdm/issues/364
  Here are three proposals if the above does not pan out, one of these should 
work, Number 3 is preferred
  1. Fix Wayland’s support for G200
  2. Rip out the broken support for Matrox G200 in Wayland
  3. Convince Canonical to blacklist the G200 from Wayland during install and 
force Xorg automatically

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

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

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

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

Title:
  adding GUI to Ubuntu Server 20.04 results in no log in screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  apt install ubuntu-desktop on Servers with embedded Matrox G200
  Graphics Controller issue

  After install/reboot there is no gdm login displayed
  Editing /etc/gdm3/custom.conf to force gdm to use Xorg instead of Wayland 
fixed the issue

  Ubuntu 19.10 has the same problem
  Same issue found installing the Desktop Version

  Had to force the /etc/dgm3/custom.conf to use xorg from Grub recovery
  mode

  
  Conclusion being - should we try to fix this?

  There may already be a fix in process
  https://gitlab.gnome.org/GNOME/gdm/issues/364
  Here are three proposals if the above does not pan out, one of these should 
work, Number 3 is preferred
  1. Fix Wayland’s support for G200
  2. Rip out the broken support for Matrox G200 in Wayland
  3. Convince Canonical to blacklist the G200 from Wayland during install and 
force Xorg automatically

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

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

[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)

[Jack Zelig]

Today I upgraded from Linux Mint 19.2 to 19.3 (Tricia) and ran into the same 
issue. 
The PC  suspends correctly, on resume I see the Mint logo, then after some 
seconds the machine reboots. 
There's nothing obvious in the logs between suspend and the reboot.
I don't have an option in UEFI to disable TPM.
Motherboard is an MSI MAG Z390 TOMAHAWK.
Reverting to kernel 4.15.0-91 solves the issue.
I'm happy to supply further details if helpful.

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

Title:
  Reboot after resume from suspend (deep)

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes
  after resume from suspending. This is regardless the way of suspending
  (closing lid, selecting suspend from sddm, systemctl suspend).

  The journal shows:
  ferry@chromium:~$ journalctl -b -1 -e
  ..
  sddm[1106]: Message received from greeter: Suspend
  NetworkManager[836]:   manager: sleep: sleep requested (sleeping: no  
enabled: yes)
  NetworkManager[836]:   device (60:73:BC:BA:B8:68): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (60:73:BC:23:8F:3E): state change: 
disconnected -> unmanaged (reason '
  NetworkManager[836]:   device (p2p-dev-wlp1s0): state change: 
disconnected -> unmanaged (reason 'sle
  NetworkManager[836]:   manager: NetworkManager state is now ASLEEP
  systemd[1]: Reached target Sleep.
  systemd[1]: Starting Suspend...
  systemd-sleep[1238]: Suspending system...
  kernel: PM: suspend entry (deep)

  On resume (keypress, open lid) resume starts but immediately crashes
  and reboots.

  The laptop is an Acer 720p Chromebook with Chromium replaced and
  working fine with Kubuntu since 5 years or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 18 18:45:53 2019
  InstallationDate: Installed on 2017-07-13 (826 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1870142] Re: Focal update: v5.4.29 upstream stable release

[Kamal Mostafa]

Due to the wireguard breakage noted in Comment #1, the patch "net: Fix
CONFIG_NET_CLS_ACT=n and CONFIG_NFT_FWD_NETDEV={y, m} build" will be
deferred.

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

Title:
  Focal update: v5.4.29 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mmc: core: Allow host controllers to require R1B for CMD6
  mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
  mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
  mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
  mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
  ACPI: PM: s2idle: Rework ACPI events synchronization
  cxgb4: fix throughput drop during Tx backpressure
  cxgb4: fix Txq restart check during backpressure
  geneve: move debug check after netdev unregister
  hsr: fix general protection fault in hsr_addr_is_self()
  ipv4: fix a RCU-list lock in inet_dump_fib()
  macsec: restrict to ethernet devices
  mlxsw: pci: Only issue reset when system is ready
  mlxsw: spectrum_mr: Fix list iteration in error path
  net/bpfilter: fix dprintf usage for /dev/kmsg
  net: cbs: Fix software cbs to consider packet sending time
  net: dsa: Fix duplicate frames flooded by learning
  net: dsa: mt7530: Change the LINK bit to reflect the link status
  net: dsa: tag_8021q: replace dsa_8021q_remove_header with __skb_vlan_pop
  net: ena: Add PCI shutdown handler to allow safe kexec
  net: mvneta: Fix the case where the last poll did not process all rx
  net/packet: tpacket_rcv: avoid a producer race condition
  net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
  net: phy: mdio-bcm-unimac: Fix clock handling
  net: phy: mdio-mux-bcm-iproc: check clk_prepare_enable() return value
  net: qmi_wwan: add support for ASKEY WWHC050
  net/sched: act_ct: Fix leak of ct zone template on replace
  net_sched: cls_route: remove the right filter from hashtable
  net_sched: hold rtnl lock in tcindex_partial_destroy_work()
  net_sched: keep alloc_hash updated after hash allocation
  net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
  NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
  r8169: re-enable MSI on RTL8168c
  slcan: not call free_netdev before rtnl_unlock in slcan_open
  tcp: also NULL skb->dev when copy was needed
  tcp: ensure skb->dev is NULL before leaving TCP stack
  tcp: repair: fix TCP_QUEUE_SEQ implementation
  vxlan: check return value of gro_cells_init()
  bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
  bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
  bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
  bnxt_en: Free context memory after disabling PCI in probe error path.
  bnxt_en: Reset rings if ring reservation fails during open()
  net: ip_gre: Separate ERSPAN newlink / changelink callbacks
  net: ip_gre: Accept IFLA_INFO_DATA-less configuration
  hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
  hsr: add restart routine into hsr_get_node_list()
  hsr: set .netnsok flag
  net/mlx5: DR, Fix postsend actions write length
  net/mlx5e: Enhance ICOSQ WQE info fields
  net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
  net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
  net/mlx5e: Do not recover from a non-fatal syndrome
  cgroup-v1: cgroup_pidlist_next should update position index
  nfs: add minor version to nfs_server_key for fscache
  cpupower: avoid multiple definition with gcc -fno-common
  drivers/of/of_mdio.c:fix of_mdiobus_register()
  cgroup1: don't call release_agent when it is ""
  dt-bindings: net: FMan erratum A050385
  arm64: dts: ls1043a: FMan erratum A050385
  fsl/fman: detect FMan erratum A050385
  drm/amd/display: update soc bb for nv14
  drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
  drm/exynos: Fix cleanup of IOMMU related objects
  iommu/vt-d: Silence RCU-list debugging warnings
  s390/qeth: don't reset default_out_queue
  s390/qeth: handle error when backing RX buffer
  scsi: ipr: Fix softlockup when rescanning devices in petitboot
  mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
  dpaa_eth: Remove unnecessary boolean expression in dpaa_get_headroom
  sxgbe: Fix off by one in samsung driver strncpy size arg
 

[Kernel-packages] [Bug 1870140] Re: Laptop freeze after unplug power-AC (USB-C)

[mCoRN]

Ubuntu 19.-4 returs the same error

in attachment all dmesg log from livecd boot
from boot till freeze

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870140/+attachment/5344400/+files/dmesg.log

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

Title:
  Laptop freeze after unplug power-AC (USB-C)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ## Power adapter plugged in,  charging goes well

  [ 1018.621820] asus_wmi: Unknown key cf pressed

  
  ## Power adapter unplugged, after few moments system freeze

  [  567.444810] BUG: kernel NULL pointer dereference, address: 0080
  [  567.444819] #PF: supervisor read access in kernel mode
  [  567.444823] #PF: error_code(0x) - not-present page
  [  567.444827] PGD 0 P4D 0 
  [  567.444834] Oops:  [#1] PREEMPT SMP PTI
  [  567.444841] CPU: 0 PID: 2873 Comm: kworker/0:0 Not tainted 
5.5.11-151.current #1
  [  567.444845] Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS 
UX370UAR.310 04/17/2019
  [  567.444857] Workqueue: events ucsi_handle_connector_change [typec_ucsi]
  [  567.444868] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.444874] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.444878] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.444883] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.444886] RDX:  RSI: 0001 RDI: 
0008
  [  567.444889] RBP:  R08:  R09: 
c9477ce0
  [  567.444892] R10: 888443e9f218 R11: 88844edeb478 R12: 
88844685c418
  [  567.444895] R13: 0001 R14: 88844685c2a8 R15: 

  [  567.444900] FS:  () GS:88844ec0() 
knlGS:
  [  567.444903] CS:  0010 DS:  ES:  CR0: 80050033
  [  567.444906] CR2: 0080 CR3: 0240a006 CR4: 
003606f0
  [  567.444909] Call Trace:
  [  567.444921]  ucsi_unregister_altmodes+0x7b/0x90 [typec_ucsi]
  [  567.444930]  ucsi_unregister_partner.part.0+0x13/0x30 [typec_ucsi]
  [  567.444938]  ucsi_handle_connector_change+0x231/0x310 [typec_ucsi]
  [  567.444949]  ? kmem_cache_free+0x22a/0x290
  [  567.444960]  process_one_work+0x1e1/0x3d0
  [  567.444968]  worker_thread+0x4a/0x3d0
  [  567.444976]  kthread+0xfb/0x130
  [  567.444983]  ? process_one_work+0x3d0/0x3d0
  [  567.444988]  ? kthread_park+0x90/0x90
  [  567.444998]  ret_from_fork+0x35/0x40
  [  567.445006] Modules linked in: typec_displayport hidp rfcomm ccm cmac fuse 
snd_hda_codec_hdmi joydev snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio bnep intel_rapl_msr snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt 
hid_multitouch iTCO_vendor_support mei_hdcp iwlmvm intel_rapl_common 
snd_soc_core mac80211 snd_compress libarc4 x86_pkg_temp_thermal 
intel_powerclamp snd_pcm_dmaengine uvcvideo ac97_bus coretemp videobuf2_vmalloc 
videobuf2_memops i915 snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg iwlwifi 
kvm_intel videobuf2_common hid_sensor_accel_3d i2c_algo_bit videodev 
snd_hda_codec btusb hid_sensor_trigger kvm industrialio_triggered_buffer 
snd_hda_core drm_kms_helper kfifo_buf btrtl btbcm syscopyarea snd_hwdep 
sysfillrect btintel industrialio asus_nb_wmi irqbypass mc wmi_bmof asus_wmi 
evdev sysimgblt hid_sensor_iio_common bluetooth cfg80211 sparse_keymap snd_pcm 
fb_sys_fops i2c_i801 ucsi_acpi snd_timer
  [  567.445072]  typec_ucsi efivars snd soundcore spi_pxa2xx_platform mei_me 
dw_dmac rfkill thermal typec i2c_designware_platform mei i2c_designware_core 
drm elan_i2c ac tpm_tis tpm_tis_core pinctrl_sunrisepoint tpm pinctrl_intel 
rng_core asus_wireless acpi_pad button hid_sensor_hub hid_generic 
intel_ishtp_hid xhci_pci serio_raw xhci_hcd intel_ish_ipc usbcore intel_ishtp 
usb_common wmi i2c_hid hid battery video
  [  567.445112] CR2: 0080
  [  567.445117] ---[ end trace a50cf550f0b4969a ]---
  [  567.445126] RIP: 0010:ucsi_displayport_remove_partner+0xa/0x20 [typec_ucsi]
  [  567.445132] Code: 38 00 c7 43 28 00 00 00 00 48 83 c7 10 5b e9 6d cd 75 e1 
66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 48 85 ff 74 0f <48> 8b 47 
78 48 c7 00 00 00 00 00 c6 40 3d 00 c3 66 0f 1f 44 00 00
  [  567.445136] RSP: 0018:c9477df0 EFLAGS: 00010202
  [  567.445140] RAX: 0008 RBX: 88844685c418 RCX: 
000efd00
  [  567.445143] RDX:  RSI: 0001 RDI: 
0008
  [  567.445146] RBP:  R08:  R09: 
c9477ce0
  [  567.445149] R10: 888443e9f

[Kernel-packages] [Bug 1870142] Re: Focal update: v5.4.29 upstream stable release

[Kamal Mostafa]

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

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

Title:
  Focal update: v5.4.29 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mmc: core: Allow host controllers to require R1B for CMD6
  mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
  mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
  mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
  mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
  ACPI: PM: s2idle: Rework ACPI events synchronization
  cxgb4: fix throughput drop during Tx backpressure
  cxgb4: fix Txq restart check during backpressure
  geneve: move debug check after netdev unregister
  hsr: fix general protection fault in hsr_addr_is_self()
  ipv4: fix a RCU-list lock in inet_dump_fib()
  macsec: restrict to ethernet devices
  mlxsw: pci: Only issue reset when system is ready
  mlxsw: spectrum_mr: Fix list iteration in error path
  net/bpfilter: fix dprintf usage for /dev/kmsg
  net: cbs: Fix software cbs to consider packet sending time
  net: dsa: Fix duplicate frames flooded by learning
  net: dsa: mt7530: Change the LINK bit to reflect the link status
  net: dsa: tag_8021q: replace dsa_8021q_remove_header with __skb_vlan_pop
  net: ena: Add PCI shutdown handler to allow safe kexec
  net: mvneta: Fix the case where the last poll did not process all rx
  net/packet: tpacket_rcv: avoid a producer race condition
  net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
  net: phy: mdio-bcm-unimac: Fix clock handling
  net: phy: mdio-mux-bcm-iproc: check clk_prepare_enable() return value
  net: qmi_wwan: add support for ASKEY WWHC050
  net/sched: act_ct: Fix leak of ct zone template on replace
  net_sched: cls_route: remove the right filter from hashtable
  net_sched: hold rtnl lock in tcindex_partial_destroy_work()
  net_sched: keep alloc_hash updated after hash allocation
  net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
  NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
  r8169: re-enable MSI on RTL8168c
  slcan: not call free_netdev before rtnl_unlock in slcan_open
  tcp: also NULL skb->dev when copy was needed
  tcp: ensure skb->dev is NULL before leaving TCP stack
  tcp: repair: fix TCP_QUEUE_SEQ implementation
  vxlan: check return value of gro_cells_init()
  bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
  bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
  bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
  bnxt_en: Free context memory after disabling PCI in probe error path.
  bnxt_en: Reset rings if ring reservation fails during open()
  net: ip_gre: Separate ERSPAN newlink / changelink callbacks
  net: ip_gre: Accept IFLA_INFO_DATA-less configuration
  hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
  hsr: add restart routine into hsr_get_node_list()
  hsr: set .netnsok flag
  net/mlx5: DR, Fix postsend actions write length
  net/mlx5e: Enhance ICOSQ WQE info fields
  net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
  net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
  net/mlx5e: Do not recover from a non-fatal syndrome
  cgroup-v1: cgroup_pidlist_next should update position index
  nfs: add minor version to nfs_server_key for fscache
  cpupower: avoid multiple definition with gcc -fno-common
  drivers/of/of_mdio.c:fix of_mdiobus_register()
  cgroup1: don't call release_agent when it is ""
  dt-bindings: net: FMan erratum A050385
  arm64: dts: ls1043a: FMan erratum A050385
  fsl/fman: detect FMan erratum A050385
  drm/amd/display: update soc bb for nv14
  drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
  drm/exynos: Fix cleanup of IOMMU related objects
  iommu/vt-d: Silence RCU-list debugging warnings
  s390/qeth: don't reset default_out_queue
  s390/qeth: handle error when backing RX buffer
  scsi: ipr: Fix softlockup when rescanning devices in petitboot
  mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
  dpaa_eth: Remove unnecessary boolean expression in dpaa_get_headroom
  sxgbe: Fix off by one in samsung driver strncpy size arg
  net: hns3: fix "tc qdisc del" failed issue
  iommu/vt-d: Fix debugfs 

[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

[satmandu]

I'm not sure which package to file a bug report on, but I have multiple
pools, and after this last update, bpool wouldn't mount properly due to
files on /boot, and as a result update-grub updated grub.cfg with no
info about my kernels. :/

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

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

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

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

[Janos Nuspl]

I also have a problem with the microphone, it doesn't work.
I have made the workaround (dmic_detect=0) and the sound is working but there 
is no mic.
My laptop is an Acer Swift 3 with the newest Intel CPU. /The headset is working 
but from home-office, I should use the built-in mic and speaker. 
Ubuntu 18.04.4 LTS was installed onto that. 
We need a working solution with a clear description, please.
(the location of the file where we should write some option - in full form)
We must work and we are not a Linux geek knowing all of the details of kernel 
boot process etc.
If we have to install an unofficial kernel how can we do it and what will 
happen if it became an official version?

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

Title:
  PCI/internal sound card not detected

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

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

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

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

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

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

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

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

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


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

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

  ASoC: topology: Check return value for snd_soc_add_dai_link()

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

  [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ]

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

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

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

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

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

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

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



  Probably a kernel bug.

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

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HD

[Kernel-packages] [Bug 1849522] Re: imported non-rpool/bpool zpools are not being reimported after reboot

[satmandu]

I don't think this is fixed, because now grub.cfg has NO entries in it
aside from that for accessing the bios menu.

(Is this related to corresponding grub-common changes?)

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

Title:
  imported non-rpool/bpool zpools are not being reimported after reboot

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Installed ubuntu 19.10 onto a zfs bpool/rpool.

  Installed zsys.

  Did a "zpool import" of my existing zfs pools.

  Rebooted.

  The previously imported zpools are not imported at boot!

  I am currently using this hacky workaround:

  https://gist.github.com/satmandu/4da5e900c2c80c93da38c76537291507

  
  I would expect that local zpools I have manually imported would re-import 
when the system is rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zsys 0.2.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 23 11:40:36 2019
  InstallationDate: Installed on 2019-10-19 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1858618] Re: linux-aws: swapoff optimization

[Kelsey Margarete Skunberg]

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

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

Title:
  linux-aws: swapoff optimization

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws-5.0 package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-aws-5.0 source package in Bionic:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws-5.0 source package in Disco:
  Invalid
Status in linux-aws source package in Eoan:
  Fix Committed
Status in linux-aws-5.0 source package in Eoan:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-aws-5.0 source package in Focal:
  Invalid

Bug description:
  [Impact]

  When an instance in the AWS EC2 infrastructure is successfully
  hibernated and resumed we want to deactivate the swap file as fast as
  possible in order to make the instance available again for the user.
  By default the kernel doesn't really optimize swapoff performance, it
  tries to keep the whole system still usable and responsive while
  swapoff is running.

  However, in our specific use case, swapoff needs to complete as fast
  as possible, so we may want to give swapoff I/O a higher priority and
  use different heuristics in order to optimize the I/O and page
  readahead generated by swapoff.

  [Test Case]

  Run the hibernation test on the AWS EC2 instances.

  [Fix]

  Apply a more aggressive swapin readahead policy that allows to improve
  swapoff performance.

  [Regression Potential]

  Minimal, this change is only affecting the swapoff-related code and it
  has been tested extensively with positive test results. The only
  downside is that this different heuristic makes the system more
  unresponsive during swapoff, but this is not a problem in the AWS
  scenario, because (by explicit requirement) the user shouldn't be able
  to use the instance during this swapoff phase.

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

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

[Kernel-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

[gfx]

A sudo swapoff -a mid copy solved the response issue, video is playing
again...

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

[gfx]

On my desktop i5-4690 with 8gb ram copying from usb3 to disk is still
slow and blocks playing video on YouTube. Happens with dolphin and cp in
the terminal. Running kubuntu 20.04

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1831940] Re: hibernation support for linux-aws

[Kelsey Margarete Skunberg]

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

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

Title:
  hibernation support for linux-aws

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws-5.0 package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux-aws-5.0 source package in Xenial:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-aws-5.0 source package in Bionic:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws-5.0 source package in Disco:
  Invalid
Status in linux-aws source package in Eoan:
  Fix Committed
Status in linux-aws-5.0 source package in Eoan:
  New
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws-5.0 source package in Focal:
  Invalid

Bug description:
  Additional AWS-specific and mainline patches are required to support
  hibernation across the various types of AWS instances.

  The following patch sets for linux-aws-xenial and linux-aws-bionic
  provide the necessary functionality, and should only impact the
  hibernation and resume paths.

  [linux-aws-xenial]

  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  radix-tree: delete radix_tree_locate_item()
  mm: rid swapoff of quadratic complexity
  sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to 
wake_up()
  sched/wait: Avoid abort_exclusive_wait() in ___wait_event()
  sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock()
  sched/wait: Introduce init_wait_entry()
  sched/wait: Standardize wait_bit_queue naming
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  NVMe: Allow request merges
  PM / hibernate: Do not free preallocated safe pages during image restore
  PM / hibernate: Recycle safe pages after image restoration
  PM / hibernate: Simplify mark_unsafe_pages()
  UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
  UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on 
hibernate

  [linux-aws-bionic]

  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  mm: rid swapoff of quadratic complexity
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  netlink: Don't shift on 64 for ngroups

  [linux-aws-edge-bionic]

  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  PM / hibernate: memory_bm_find_bit(): Tighten node optimisation
  mm: rid swapoff of quadratic complexity
  mm: refactor swap-in logic out of shmem_getpage_gfp

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Xenial update: 4.4.215 upstream stable release

[Kelsey Margarete Skunberg]

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

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

Title:
  Xenial update: 4.4.215 upstream stable release

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

Bug description:
  
  SRU Justification

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

 4.4.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 ti