[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug

[You-Sheng Yang]

Upstream: https://lore.kernel.org/linux-
usb/20200224071541.117363-1-vicamo.y...@canonical.com/

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

Title:
  r8152 init may take up to 40 seconds at initialization with Dell
  WD19/WD19DC during hotplug

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  New

Bug description:
  [SRU Justification]

  [Impact]
  USB devices attached to Dell WD19/WD19DC USB Type-C dock take up to nearly one
  minutes to be ready for use.

  [Fix]
  r8152 driver init process involves several for-loops that each may take up to 
14
  seconds to exit when USB port reset occurs during hotplug. This is still
  reproducible with latest v5.6-rc mainline kernel although the fail rate is 
much
  lower since v5.5-rc7.

  [Test Case]
  Verified on Dell WD19DC.

  [Regression Potential]
  Low. Just to exit the loop early when it should have been.

  == original bug description ==

  Dell USB Type C docking WD19/WD19DC attaches additional peripherals
  as:

    /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M
    |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M
    |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, 
Driver=r8152, 5000M

  where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the
  dock.

  When hotplugging such dock with additional usb devices already
  attached on it, the probing process may reset usb 2.1 port, therefore
  r8152 ethernet device is also reset. However, in r8152 driver there
  are several  for-loops that may take up to 14 seconds during the
  initialization for each in practice, and that has to be completed
  before USB may re-enumerate devices on the bus. As a result, devices
  attached to the dock will only be available after nearly 1 minute
  after the dock is plugged in.

    [  216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface
    [  216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id
    [  258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY 
not ready
    [  258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): 
Invalid header when reading pass-thru MAC addr
    [  258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get 
ether addr fail

  This can be reproduced on all kernel versions up to latest v5.6-rc2,
  but after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or
  so while it was around 1/2.

  The time consuming for-loops are at:
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2014 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 04:07:20 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95
  InstallationDate: Installed on 2020-01-16 (37 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IwConfig:
   enp1s0no wireless extensions.

   enxd8d090035306  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. Latitude 3310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* 
+pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
   linux-backports-modules-5.0.0-1037-oem-osp1  N/A
   linux-firmware   1.173.15
  SourcePackage: linux-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.51.2[V2 AMI]
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3310
  

[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-
team/2020-February/107726.html

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ USB devices attached to Dell WD19/WD19DC USB Type-C dock take up to nearly one
+ minutes to be ready for use.
+ 
+ [Fix]
+ r8152 driver init process involves several for-loops that each may take up to 
14
+ seconds to exit when USB port reset occurs during hotplug. This is still
+ reproducible with latest v5.6-rc mainline kernel although the fail rate is 
much
+ lower since v5.5-rc7.
+ 
+ [Test Case]
+ Verified on Dell WD19DC.
+ 
+ [Regression Potential]
+ Low. Just to exit the loop early when it should have been.
+ 
+ == original bug description ==
+ 
  Dell USB Type C docking WD19/WD19DC attaches additional peripherals as:
  
    /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M
    |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M
    |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, 
Driver=r8152, 5000M
  
  where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the dock.
  
  When hotplugging such dock with additional usb devices already attached
  on it, the probing process may reset usb 2.1 port, therefore r8152
  ethernet device is also reset. However, in r8152 driver there are
  several  for-loops that may take up to 14 seconds during the
  initialization for each in practice, and that has to be completed before
  USB may re-enumerate devices on the bus. As a result, devices attached
  to the dock will only be available after nearly 1 minute after the dock
  is plugged in.
  
-   [  216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface
-   [  216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id
-   [  258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY 
not ready
-   [  258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): 
Invalid header when reading pass-thru MAC addr
-   [  258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get 
ether addr fail
+   [  216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface
+   [  216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id
+   [  258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY 
not ready
+   [  258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): 
Invalid header when reading pass-thru MAC addr
+   [  258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get 
ether addr fail
  
  This can be reproduced on all kernel versions up to latest v5.6-rc2, but
  after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or so
  while it was around 1/2.
  
  The time consuming for-loops are at:
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400
  https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2014 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 04:07:20 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95
  InstallationDate: Installed on 2020-01-16 (37 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IwConfig:
   enp1s0no wireless extensions.
  
   enxd8d090035306  no wireless extensions.
  
   lono wireless extensions.
  MachineType: Dell Inc. Latitude 3310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* 
+pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
   linux-backports-modules-5.0.0-1037-oem-osp1  N/A
   linux-firmware   1.173.15
  SourcePackage: linux-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.51.2[V2 AMI]
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: 

[Kernel-packages] [Bug 1859269] Re: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch

[Ike Panhc]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-20.04
   Status: Incomplete => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Incomplete => In Progress

** Changed in: kunpeng920
   Status: Incomplete => In Progress

** Changed in: kunpeng920/ubuntu-20.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-18.04-hwe
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
  roce patchset have merged into mainline 5.5rc6 kernel. Pls backport ubuntu 
18.04.5 kernel version
  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  RDMA/hns: Delete unnecessary callback functions for cq
  RDMA/hns: Rename the functions used inside creating cq
  RDMA/hns: Redefine the member of hns_roce_cq struct
  RDMA/hns: Redefine interfaces used in creating cq
  IB/umem: remove the dmasync argument to ib_umem_get
  RDMA/hns: Modify appropriate printings
  RDMA/hns: Fix non-standard error codes
  RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code
  RDMA/hns: Simplify doorbell initialization code
  RDMA/hns: Replace not intuitive function/macro names
  RDMA/hns: Modify fields of struct hns_roce_srq
  RDMA/hns: Delete unnecessary uar from hns_roce_cq
  RDMA/hns: Remove unnecessary structure hns_roce_sqp
  RDMA/hns: Delete unnecessary variable max_post
  RDMA/hns: Remove unsupported modify_port callback
  RDMA: Connect between the mmap entry and the umap_priv structure
  RDMA/hns: Fix build error again
  RDMA/hns: Fix memory leak on 'context' on error return path
  RDMA/hns: Bugfix for qpc/cqc timer configuration
  RDMA/hns: Fix to support 64K page for srq
  RDMA/hns: Delete BITS_PER_BYTE redefinition
  RDMA/hns: Prevent undefined behavior in hns_roce_set_user_sq_size()
  RDMA/hns: Release qp resources when failed to destroy qp
  RDMA/hns: Fix a spelling mistake in a macro
  RDMA/hns: Modify return value of restrack functions
  RDMA/hns: Modify variable/field name from vlan to vlan_id
  RDMA/hns: Fix wrong parameters when initial mtt of srq->idx_que
  RDMA/hns: remove a redundant le16_to_cpu
  RDMA/hns: Prevent memory leaks of eq->buf_list
  RDMA/hns: Correct the value of srq_desc_size
  RDMA/hns: Correct the value of HNS_ROCE_HEM_CHUNK_LEN
  RDMA/hns: Add support for reporting wc as software mode
  RDMA/hns: Bugfix for posting a wqe with sge
  RDMA/hns: Fix coding style issues
  RDMA/hns: Replace custom macros HNS_ROCE_ALIGN_UP
  RDMA/hns: Remove redundant print information
  RDMA/hns: Delete unnessary parameters in hns_roce_v2_qp_modify()
  RDMA/hns: Update the value of qp type
  RDMA/hns: Remove unused function hns_roce_init_eq_table()
  RDMA/hns: Avoid printing address of mtt page
  RDMA/hns: Simplify the calculation and usage of wqe idx for post verbs

  update 01120
  RDMA/hns: Get pf capabilities from firmware
  RDMA/hns: Add interfaces to get pf capabilities from firmware
  RDMA/hns: Remove some redundant variables related to capabilities
  RDMA/hns: Add support for extended atomic in userspace

  [Status]
  (In Progress): RDMA/hns: Delete unnecessary callback functions for cq
  (In Progress): RDMA/hns: Rename the functions used inside creating cq
  (In Progress): RDMA/hns: Redefine the member of hns_roce_cq struct
  (In Progress): RDMA/hns: Redefine interfaces used in creating cq
  (In Progress): IB/umem: remove the dmasync argument to ib_umem_get
  (In Progress): RDMA/hns: Modify appropriate printings
  (In Progress): RDMA/hns: Fix non-standard error codes
  (In Progress): RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code
  (In Progress): RDMA/hns: Simplify doorbell initialization code
  (In Progress): RDMA/hns: Replace not intuitive function/macro names
  (In Progress): RDMA/hns: Modify fields of struct hns_roce_srq
  (In Progress): RDMA/hns: Delete unnecessary uar from hns_roce_cq
  (In Progress): RDMA/hns: Remove unnecessary structure hns_roce_sqp
  (In Progress): RDMA/hns: Delete unnecessary variable max_post
  (In Progress): RDMA/hns: Remove unsupported modify_port callback
  (In Progress): RDMA: Connect 

[Kernel-packages] [Bug 1850681] Re: TREKSTOR Primebook C11B touchpad and touchscreen not working

[Kai-Heng Feng]

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

Title:
  TREKSTOR Primebook C11B touchpad and touchscreen not working

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  touchpad not working, only usb-mouse is recognized. touchscreen functionality 
not working, but that would be rather less important. Everything else is 
perfectly fine. (18.04 LTS)
  TREKSTOR Primebook C11B

  Thanks :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 18:43:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: TREKSTOR Primebook C11B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.1.2
  dmi.board.asset.tag: Default string
  dmi.board.name: Apollolake_alk_V01
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: Primebook C11B
  dmi.product.sku: CFALKWW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1864198] Re: Update kernel options CONFIG_NR_CPUS and CONFIG_NUMA_EMU for focal

[Frank Heimes]

Request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-February/thread.html#107724
changing status to 'In Progress'

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: Frank Heimes (fheimes) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Update kernel options CONFIG_NR_CPUS and CONFIG_NUMA_EMU for focal

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Following update should be applied for the kernel config with Ubuntu
  20.04

  Current:
  CONFIG_NR_CPUS=256
  CONFIG_NUMA_EMU=Y

  New
  CONFIG_NR_CPUS=512
  #CONFIG_NUMA_EMU is not set

  No change for
  CONFIG_NUMA=y

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Ike Panhc]

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

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

Status in kunpeng920:
  New
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:
  New
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [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 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error

[Ike Panhc]

** Tags removed: 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/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-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [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 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit

[Ike Panhc]

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

Title:
  [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE
  kernel branch Edit

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
   hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 
18.04.5 kernel version
  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  net: hns3: support tx-scatter-gather-fraglist feature
  net: hns3: add support for configuring VF MAC from the host
  net: hns3: add support for configuring bandwidth of VF on the host
  net: hns3: add support for setting VF trust
  net: hns3: add support for spoof check setting
  net: hns3: add support for setting VF link status on the host
  net: hns3: make array tick_array static, makes object smaller

  net: hns3: fix a wrong reset interrupt status mask
  net: hns3: cleanup of stray struct hns3_link_mode_mapping
  net: hns3: fix ETS bandwidth validation bug
  net: hns3: reallocate SSU' buffer size when pfc_en changes
  net: hns3: add compatible handling for MAC VLAN switch parameter configuration
  net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE
  net: hns3: remove unused macros
  net: hns3: Use the correct style for SPDX License Identifier
  net: hns3: cleanup byte order issues when printed
  net: hns3: cleanup some print format warning
  net: hns3: add or modify some comments
  net: hns3: optimize local variable initialization
  net: hns3: cleanup a format-truncation warning
  net: hns3: cleanup some coding style issues
  net: hns3: cleanup some magic numbers
  net: hns3: add struct netdev_queue debug info for TX timeout
  net: hns3: dump some debug information when reset fail
  treewide: Use sizeof_member() macro
  net: hns3: log and clear hardware error after reset complete
  net: hns3: do not allocate linear data for fraglist skb
  net: hns3: minor cleanup for hns3_handle_rx_bd()
  net: hns3: make struct hns3_enet_ring cacheline aligned
  net: hns3: introduce ring_to_netdev() in enet module
  net: hns3: minor optimization for barrier in IO path
  net: hns3: optimized MAC address in management table.
  net: hns3: remove struct hns3_nic_ring_data in hns3_enet module
  net: hns3: fix mis-counting IRQ vector numbers issue
    net: hns3: fix VF ID issue for setting VF VLAN
  net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx()
  net: hns3: fix for TX queue not restarted problem
   net: hns3: only print misc interrupt status when handling fails
  net: hns3: add a log for getting chain failure in 
hns3_nic_uninit_vector_data()
  net: hns3: add some VF VLAN information for command "ip link show"
  net: hns3: implement ndo_features_check ops for hns3 driver
  net: hns3: get FD rules location before dump in debugfs
  net: hns3: optimization for CMDQ uninitialization
  net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev
  net: hns3: check FE bit before calling hns3_add_frag()
  net: hns3: do not schedule the periodic task when reset fail
  net: hns3: allocate WQ with WQ_MEM_RECLAIM flag
  net: hns3: remove unnecessary work in hclgevf_main
  net: hns3: remove mailbox and reset work in hclge_main
  net: hns3: schedule hclgevf_service by using delayed workqueue
  net: hns3: refactor the notification scheme of PF reset
  net: hns3: refactor the procedure of VF FLR
  net: hns3: modify hclge_func_reset_sync_vf()'s return type to void
  net: hns3: enlarge HCLGE_RESET_WAIT_CNT
  net: hns3: refactor the precedure of PF FLR
  net: hns3: split hclgevf_reset() into preparing and rebuilding part
  net: hns3: split hclge_reset() into preparing and rebuilding part
  net: hns3: modify an unsuitable reset level for hardware error
  net: hns3: replace an unsuitable variable type in 
hclge_inform_reset_assert_to_vf()
  net: hns3: add protection when get SFP speed as 0
  net: hns3: modify the IRQ name of misc vectors
  net: hns3: modify an unsuitable log in hclge_map_ring_to_vector()
  net: hns3: modify the IRQ name of TQP vector
  net: hns3: re-organize vector handle
  net: hns3: add trace event support for HNS3 driver

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

  [Status]
  (Fix committed): net: hns3: support tx-scatter-gather-fraglist feature
  (Fix committed): net: hns3: add support for configuring VF MAC from the host
  (Fix committed): net: hns3: add support for configuring bandwidth of VF on 
the host
  (Fix committed): 

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Thiago Vincenzi Conrado]

4.15.0-54-generic did work great in the past
we moved to 5.3.0-28-generic and this bug is notable...

funny enough one of our machines was able to recover... both have the
very same OS version

Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic
5.3.0-28-generic

maybe a downgrade de to Ubuntu 18.04.2 is a "solution"

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Thiago Vincenzi Conrado]

4.15.0-54-generic is bug free
5.3.0-28-generic has the bug

funny enough one of our machines was able to recover... both have the
very same OS version

Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
5.3.0-28-generic

maybe a downgrade de to Ubuntu 18.04.2 is a "solution"

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1864413] Re: [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways

[Shrirang Bagul]

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

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

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

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

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

Title:
  [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT
  Gateways

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

Bug description:
  [Impact]
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).

  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  [Note]
  linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

  This bug is used for tracking purposes, please do not triage.

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

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

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

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

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

** Tags added: bionic

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

Title:
  [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT
  Gateways

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

Bug description:
  [Impact]
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).

  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  [Note]
  linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1864413] [NEW] [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways

[Shrirang Bagul]

Public bug reported:

[Impact]
To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

[Fixes]
Most of the patches are already upstream (either Accepted or under review) and 
being
tracked here:
https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

SAUCE patches have been tested by Canonical CE-QA (based on
Ubuntu-4.15.0-73.82).

[Regression Potential]
Low. We've carried these patches in the linux-oem (4.15.y) kernel for more than 
2 years.
Also, the impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
{ SDIO_DEVICE(0x041B, 0x9330) }.

[Note]
linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

This bug is used for tracking purposes, please do not triage.

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

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


** Tags: bionic

** Description changed:

  [Impact]
- To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways. 
+ To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.
  
  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A
  
  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).
  
  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.
  
+ [Note]
+ linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682
+ 
  This bug is used for tracking purposes, please do not triage.

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

Title:
  [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT
  Gateways

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

Bug description:
  [Impact]
  To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.

  [Fixes]
  Most of the patches are already upstream (either Accepted or under review) 
and being
  tracked here:
  https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A

  SAUCE patches have been tested by Canonical CE-QA (based on
  Ubuntu-4.15.0-73.82).

  [Regression Potential]
  Low. We've carried these patches in the linux-oem (4.15.y) kernel for more 
than 2 years.
  Also, the impact is limited to the Redpine RS9113 Wifi+BT with following 
VID/PID
  { SDIO_DEVICE(0x041B, 0x9330) }.

  [Note]
  linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

Status in alsa-driver package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions

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

[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

[Launchpad Bug Tracker]

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

Status in alsa-driver package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[Hui Wang]

Since the Apple usb NIC doesn't have this issue, it is a problem on the
driver lan78xx.c

Do you mean even without ipv6 tunnel, only setup a bridge on rpi3 to let
eth0 connect WAN and let wlan0 play a role of AP, this issue could be
reproduced?

Could you please share the detailed steps on how to setup a bridge on
the rpi3 to reproduce this issue?

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and 
network load. Happened a few times (every time) when I tried to download a 
gparted zip release (~350 MiB) directly to the SD card, and then finally when I 
tried to scp the finished download from a desktop onto RPi's card.
  Didn't collect information when it happened, but kept a copy of kern.log. 
Here's the relevant part:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  
bcm2836_arm_irqchip_handle_irq+0x74/0xe0
  Feb  4 23:42:59 rpi3 kernel: [  571.879037]  el1_irq+0x108/0x200
  Feb  4 23:42:59 

[Kernel-packages] [Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Monday, 17. February 2020 21:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  variant: debs

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

Title:
  xenial/linux: 4.4.0-175.205 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Monday, 17. February 2020 21:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1863334
trusty/linux-lts-xenial: bug 1863336
xenial/linux-aws: bug 1863311
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1863331
xenial/linux-kvm: bug 1863319
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1863304
xenial/linux/pc-kernel: bug 1863306
xenial/linux/stlouis-kernel: bug 1863307
  variant: debs

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

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

[Kernel-packages] [Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker

[Po-Hsu Lin]

4.4.0-175.205 - generic
Regression test CMPL, RTB.

56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in amd64:
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx 
(bug 1821394)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) gicv2-mmio-3p 
(bug 1828027) gicv2-mmio-up (bug 1828026) pmu on ms10-34-mcdivittB0-kernel (bug 
1751000)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_lxc - failed to fetch GPG key, probably FW issue
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, 
ubuntu_xfstests_ext4, ubuntu_xfstests_xfs
Issue to note in i386:
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in ppc64le (P8):
  ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 
320M on Xenial P8 (bug 1813863)
  ubuntu_ecryptfs - faild to fork child for file-concurrent.sh and 
directory-concurrent.sh.ext3
  ubuntu_fan_smoke_test - Failed to fetch file from http://ports.ubuntu.com 
(bug 1864140)
  ubuntu_ltp_syscalls - fallocate04, fallocate05, fsetxattr01, fdatasync03, 
fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, 
fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, 
preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, 
sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) 
fanotify10 (bug 1802454) move_pages12 (bug 1831043)
  ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) 
killed by signal 1 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

Issue to note in s390x (zVM):
  libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) 
killed by signal 1 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

Note:
  * Missing s390x KVM because of bug 1859656


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  xenial/linux: 4.4.0-175.205 -proposed tracker

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

[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working

[Daniel van Vugt]

Note that if the problem is fixed in later Ubuntu releases then it
likely would be fixed in Ubuntu 18.04.4 too:

  https://ubuntu.com/download/desktop

If you just update Ubuntu 18.04 then you won't ever get the same newer
kernel as comes with 18.04.4. So maybe the issue is already fixed-
released via the HWE kernel. You should be able to try it by:

  sudo apt install linux-generic-hwe-18.04

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

Title:
  Keychron K1 keyboard not working

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

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  

[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug

[You-Sheng Yang]

** Description changed:

- TBD
+ Dell USB Type C docking WD19/WD19DC attaches additional peripherals as:
+ 
+   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
+   |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M
+   |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M
+   |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, 
Driver=r8152, 5000M
+ 
+ where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the dock.
+ 
+ When hotplugging such dock with additional usb devices already attached
+ on it, the probing process may reset usb 2.1 port, therefore r8152
+ ethernet device is also reset. However, in r8152 driver there are
+ several  for-loops that may take up to 14 seconds during the
+ initialization for each in practice, and that has to be completed before
+ USB may re-enumerate devices on the bus. As a result, devices attached
+ to the dock will only be available after nearly 1 minute after the dock
+ is plugged in.
+ 
+ This can be reproduced on all kernel versions up to latest v5.6-rc2, but
+ after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or so
+ while it was around 1/2.
+ 
+ The time consuming for-loops are at:
+ https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206
+ https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400
+ https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  u  2014 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  2014 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 04:07:20 2020
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95
  InstallationDate: Installed on 2020-01-16 (37 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IwConfig:
-  enp1s0no wireless extensions.
-  
-  enxd8d090035306  no wireless extensions.
-  
-  lono wireless extensions.
+  enp1s0no wireless extensions.
+ 
+  enxd8d090035306  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: Dell Inc. Latitude 3310
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* 
+pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
-  linux-backports-modules-5.0.0-1037-oem-osp1  N/A
-  linux-firmware   1.173.15
+  linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
+  linux-backports-modules-5.0.0-1037-oem-osp1  N/A
+  linux-firmware   1.173.15
  SourcePackage: linux-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.51.2[V2 AMI]
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3310
  dmi.product.sku: 0A13
  dmi.sys.vendor: Dell Inc.

** Description changed:

  Dell USB Type C docking WD19/WD19DC attaches additional peripherals as:
  
-   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
-   |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M
-   |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M
-   |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, 
Driver=r8152, 5000M
+   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
+   |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M
+   |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M
+   |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, 
Driver=r8152, 5000M
  
  where usb 2-1-3 is a hub connecting all USB Type-A/C ports 

[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working

[Alejandro Mery]

good idea, 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/1814481

Title:
  Keychron K1 keyboard not working

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

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  

[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working

[Daniel van Vugt]

To ensure this bug does not become oversubscribed by other people with
other problems I have clarified this bug is only about the "Keychron K1
keyboard".

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

Title:
  Keychron K1 keyboard not working

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

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  

[Kernel-packages] [Bug 1814481] Re: bluetooth keyboard not working

[Daniel van Vugt]

Yes, sorry. I'm not sure what I was aiming for there.

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

** Summary changed:

- bluetooth keyboard not working
+ Keychron K1 keyboard not working

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

Title:
  Keychron K1 keyboard not working

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

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  

[Kernel-packages] [Bug 1814481] Re: bluetooth keyboard not working

[Alejandro Mery]

@vanvugt, shouldn't that be after actually merging the fix?

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

Title:
  bluetooth keyboard not working

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  

[Kernel-packages] [Bug 1814481] Re: bluetooth keyboard not working

[Daniel van Vugt]

** No longer affects: linux (Ubuntu Bionic)

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

Title:
  bluetooth keyboard not working

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: 

[Kernel-packages] [Bug 1864400] Re: alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal)

[Hui Wang]

** Description changed:

- This bug is for tracking purpose.
+ [Impact]
+ In the ubuntu 20.04, we plan to integrate alsa-ucm-conf-v1.2.1.2
+ or alsa-ucm-conf-v1.2.2, in the ucm2, adding a new element to
+ tell pulseaudo the number of dmics on this machine, this needs kernel
+ to export the number via component.
+ Without these 2 patches, the pulseaudio will fail to initialize
+ on Lenovo X1 Carbon since this machine has 4 dmics.
+ 
+ [Fix]
+ Backported the patches from mainline kernel v5.6-c1
+ 
+ [Test Case]
+ Install the sof-firmware v1.4.2
+ Install the master branch of alsa-ucm-conf (focal will integrate it too)
+ Install the master branch of pulseaudio (focal will integrate it too)
+ boot the kernel with these patches, check the gnome-control-center,
+ all audio function work well.
+ 
+ 
+ [Regression Risk]
+ Low, the patches are backported from upstream kernel, and I tested
+ this patch on Lenovo and Dell dmic machines. And after merging
+ these 2 patches, the kernel still could work with old firmware
+ and ucm.

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

Title:
  alsa/asoc: export the number of dmic to userspace to work with the
  latest ucm2 (focal)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  In the ubuntu 20.04, we plan to integrate alsa-ucm-conf-v1.2.1.2
  or alsa-ucm-conf-v1.2.2, in the ucm2, adding a new element to
  tell pulseaudo the number of dmics on this machine, this needs kernel
  to export the number via component.
  Without these 2 patches, the pulseaudio will fail to initialize
  on Lenovo X1 Carbon since this machine has 4 dmics.

  [Fix]
  Backported the patches from mainline kernel v5.6-c1

  [Test Case]
  Install the sof-firmware v1.4.2
  Install the master branch of alsa-ucm-conf (focal will integrate it too)
  Install the master branch of pulseaudio (focal will integrate it too)
  boot the kernel with these patches, check the gnome-control-center,
  all audio function work well.

  
  [Regression Risk]
  Low, the patches are backported from upstream kernel, and I tested
  this patch on Lenovo and Dell dmic machines. And after merging
  these 2 patches, the kernel still could work with old firmware
  and ucm.

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

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

[Kernel-packages] [Bug 1861237] Re: Audio not detected on X1 Yoga 4th

[Hui Wang]

Probably kernel-5.4.0.15 will have all needed patches for supporting sof 
driver. But the sof-firmware has not been integrated to linux-firmware. So when 
.15 kernel is ready, we could manually install the firmware and alsa-ucm-conf 
to test.
 

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

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

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

Title:
  Audio not detected on X1 Yoga 4th

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's 
not detecting audio from it at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  Package: pulseaudio 1:13.0-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 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-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  Package: pulseaudio 1:13.0-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 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

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

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

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

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

Title:
  alsa/asoc: export the number of dmic to userspace to work with the
  latest ucm2 (focal)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is for tracking purpose.

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

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

[Kernel-packages] [Bug 1864400] [NEW] alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal)

[Hui Wang]

Public bug reported:

This bug is for tracking purpose.

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


** Tags: focal

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

** Summary changed:

- alsa/asoc: export the number of dmic to userspace to work with the latest 
ucm2 
+ alsa/asoc: export the number of dmic to userspace to work with the latest 
ucm2 (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/1864400

Title:
  alsa/asoc: export the number of dmic to userspace to work with the
  latest ucm2 (focal)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is for tracking purpose.

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

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

[Kernel-packages] [Bug 1864398] Re: alsa/sof: let sof driver work with topology with volume and led control (focal)

[Hui Wang]

** Description changed:

- This bug is for tracking purpose.
+ [Impact]
+ In the ubuntu 20.04, we plan to integrate sof-firmware v1.4.2, the
+ topology of this version contains volume and led control, we need
+ to add this support in the sof driver, otherwise the sof will crash
+ when parsing the topology of v1.4.2.  After adding these patches,
+ the sof still coudl work with topology without volume and led control.
+ 
+ [Fix]
+ Backported the patches from mainline kernel v5.5-c1
+ 
+ [Test Case]
+ Install the sof-firmware v1.4.2
+ boot the kernel with these patches, sof driver initializes successfully,
+ and we could get a working sound card after booting up.
+ 
+ Install the sof-firmware v1.3.1
+ boot the kernel with these patches, sof driver initializes successfully,
+ and we could get a working sound card after booting up.
+ 
+ [Regression Risk]
+ Low, the patches are backported from upstream kernel, and I tested
+ this patch on Lenovo and Dell dmic machines.

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

Title:
  alsa/sof: let sof driver work with topology with volume and led
  control (focal)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  In the ubuntu 20.04, we plan to integrate sof-firmware v1.4.2, the
  topology of this version contains volume and led control, we need
  to add this support in the sof driver, otherwise the sof will crash
  when parsing the topology of v1.4.2.  After adding these patches,
  the sof still coudl work with topology without volume and led control.

  [Fix]
  Backported the patches from mainline kernel v5.5-c1

  [Test Case]
  Install the sof-firmware v1.4.2
  boot the kernel with these patches, sof driver initializes successfully,
  and we could get a working sound card after booting up.

  Install the sof-firmware v1.3.1
  boot the kernel with these patches, sof driver initializes successfully,
  and we could get a working sound card after booting up.

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

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

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

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

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

Title:
  alsa/sof: let sof driver work with topology with volume and led
  control (focal)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is for tracking purpose.

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

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

[Kernel-packages] [Bug 1864398] [NEW] alsa/sof: let sof driver work with topology with volume and led control (focal)

[Hui Wang]

Public bug reported:

This bug is for tracking purpose.

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


** Tags: focal

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

** Summary changed:

- alsa/sof: let sof driver work with topology with volume and led control
+ alsa/sof: let sof driver work with topology with volume and led control 
(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/1864398

Title:
  alsa/sof: let sof driver work with topology with volume and led
  control (focal)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is for tracking purpose.

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

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

[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy

[Vinson Lee]

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

Title:
  Missing mcelog userspace package in bionic - or maybe linux kernel
  config should disable mcelog_legacy

Status in linux package in Ubuntu:
  Confirmed
Status in mcelog package in Ubuntu:
  Confirmed

Bug description:
  There is no mcelog package in bionic.

  $ sudo apt install mcelog
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package mcelog is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'mcelog' has no installation candidate

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

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

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

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

Title:
  WiFi not working

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No WiFi APs are detected.  It's like the driver doesn't recognize the
  hardware.

  I tried reinstalling it, but it didn't work.

  Please fix this ASAP.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.18.1
  KDE Frameworks Version: 5.67.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-40-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: backport-iwlwifi-dkms 7906-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 18:43:16 2020
  InstallationDate: Installed on 2020-01-19 (35 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: backport-iwlwifi-dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions

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

[Kernel-packages] [Bug 1864392] Re: WiFi not working

[Jonas Gamao]

Switching back to kernel 5.3.0-29-generic worked.

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

Title:
  WiFi not working

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No WiFi APs are detected.  It's like the driver doesn't recognize the
  hardware.

  I tried reinstalling it, but it didn't work.

  Please fix this ASAP.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.18.1
  KDE Frameworks Version: 5.67.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-40-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: backport-iwlwifi-dkms 7906-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 18:43:16 2020
  InstallationDate: Installed on 2020-01-19 (35 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: backport-iwlwifi-dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions

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

[Kernel-packages] [Bug 1864392] [NEW] WiFi not working

[Jonas Gamao]

Public bug reported:

No WiFi APs are detected.  It's like the driver doesn't recognize the
hardware.

I tried reinstalling it, but it didn't work.

Please fix this ASAP.

Operating System: Kubuntu 19.10
KDE Plasma Version: 5.18.1
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-40-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: backport-iwlwifi-dkms 7906-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Feb 23 18:43:16 2020
InstallationDate: Installed on 2020-01-19 (35 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: backport-iwlwifi-dkms
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: backport-iwlwifi-dkms (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug eoan

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

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

Title:
  WiFi not working

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  No WiFi APs are detected.  It's like the driver doesn't recognize the
  hardware.

  I tried reinstalling it, but it didn't work.

  Please fix this ASAP.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.18.1
  KDE Frameworks Version: 5.67.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-40-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: backport-iwlwifi-dkms 7906-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 18:43:16 2020
  InstallationDate: Installed on 2020-01-19 (35 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: backport-iwlwifi-dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1864392/+subscriptions

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

[Kernel-packages] [Bug 1863824] ProcEnviron.txt

[Jonas Gamao]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1863824/+attachment/5330492/+files/ProcEnviron.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/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-firmware package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1863824/+subscriptions

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

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

[Jonas Gamao]

apport information

** Tags added: apport-collected focal

** Description changed:

  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

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1863824/+attachment/5330491/+files/ProcCpuinfoMinimal.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/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-firmware package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1863824/+subscriptions

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

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

[Jonas Gamao]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/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-firmware package in Ubuntu:
  New

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1863824/+subscriptions

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

[Kernel-packages] [Bug 1859380] Re: Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04

[Jonas Gamao]

Good evening,

Any updates with this bug report?

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

Title:
  Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sleep button doesn't work at all, and when I close the lid, the screen
  goes black, but there's a cursor, and it doesn't respond.  Had to
  force shut down.

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.17.5
  KDE Frameworks Version: 5.66.0
  Qt Version: 5.12.5
  Kernel Version: 5.4.0-9-generic
  OS Type: 64-bit
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 15.3 GiB of RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-desktop 1.392
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jan 12 19:24:55 2020
  InstallationDate: Installed on 2020-01-03 (9 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  IwConfig:
   wlp0s20f3  no wireless extensions.
   
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: LENOVO 20SA0002US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=d3ea3aaf-4630-491b-8315-c7efa5381fdf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 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

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

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

[Kernel-packages] [Bug 1861237] Re: Audio not detected on X1 Yoga 4th

[Jonas Gamao]

Just did the update today, and no changes.

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

Title:
  Audio not detected on X1 Yoga 4th

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's 
not detecting audio from it at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  Package: pulseaudio 1:13.0-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 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-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  Package: pulseaudio 1:13.0-3ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 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

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

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

[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle

[arno]

Thanks. I stay at 5.3.0.18 till then. Stupid question. Screen shudders
(syncing fails from time to time) after sleep/hibernate. Is this a known
issue and solved in newer 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/1853044

Title:
  5.3.0-23-generic causes fans to spin when idle

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 5.3.0-23-generic the fans in my machine don't stop
  running. They always sound like something is utilizing CPU - even with
  no applications running after boot.

  If I boot back to 5.3.0-19-generic it's fine.

  My microcode version is reported as 0xd4 and iucode-tool reports:

  iucode-tool: system has processor(s) with signature 0x000506e3

  Let me know if you need anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   2898 F pulseaudio
   /dev/snd/pcmC2D0p:   dean   2898 F...m pulseaudio
   /dev/snd/controlC0:  dean   2898 F pulseaudio
   /dev/snd/controlC1:  dean   2898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 13:03:34 2019
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (482 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

[Woodcarver]

The bug is gone on 20.04 daily (2020-02-23). Screen orientation is now
correct on my Elitebook 840 G1.

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my hardware. 
Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sharper1380 F pulseaudio
   /dev/snd/controlC1:  sharper1380 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-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/12/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.44
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG4430MGN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: D1F44AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic

[Kyle Weber]

Same here on a XPS 13 7390, 5.4.0-14-generic also.

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

Title:
  [Dell XPS 15 9575] Screen brightness stopped working with linux-
  image-5.4.0-9-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Focal Fossa 3 days ago and nothing broke. At the time,
  it was still using linux 5.3 (linux-image-5.3.0-24-generic).

  Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after
  rebooting, the screen brightness does not work anymore - neither from
  keyboard keys nor from the slider in the gnome-shell panel.

  It works again when rebooting into the previous linux-
  image-5.3.0-24-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mario  1892 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  8 20:23:31 2020
  InstallationDate: Installed on 2018-09-13 (481 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[mlx]

Sorry, got kinda stuck trying to test with a USB NIC:
https://askubuntu.com/q/1212529/325336

After disabling systemd-resolved (+ putting a public DNS IPv4 address in
resolv.conf), v6 download over the external USB NIC (Apple USB Ethernet,
05ac:1402) works fine. After switching the cable back to the built-in
NIC, the error appeared almost immediately, didn't even get to try the
v6 download.

[ 2452.471188] br0: port 3(eth1) entered disabled state
[ 3030.723594] br0: received packet on wlan0 with own address as source address 
(addr:b8:27:eb:3a:ba:a2, vlan:0)
[ 3030.860954] br0: received packet on wlan0 with own address as source address 
(addr:b8:27:eb:3a:ba:a2, vlan:0)
[ 3037.463785] br0: received packet on wlan0 with own address as source address 
(addr:b8:27:eb:3a:ba:a2, vlan:0)
[ 3228.800706] asix 1-1.3:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 3228.804385] br0: port 3(eth1) entered blocking state
[ 3228.804417] br0: port 3(eth1) entered forwarding state
[ 3293.930873] [ cut here ]
[ 3293.930958] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out
[ 3293.931102] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 
dev_watchdog+0x324/0x330
[ 3293.931109] Modules linked in: asix sit tunnel4 ip_tunnel bridge stp llc 
ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic bcm2835_v4l2(CE) ecc 
bcm2835_mmal_vchiq(CE) vc_sm_cma(CE) brcmfmac v4l2_common videobuf2_vmalloc 
brcmutil videobuf2_memops videobuf2_v4l2 cfg80211 videobuf2_common input_leds 
videodev mc spidev raspberrypi_hwmon uio_pdrv_genirq uio sch_fq_codel ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic 
fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
[ 3293.931334] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C  E 
5.3.0-1018-raspi2 #20-Ubuntu
[ 3293.931339] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
[ 3293.931348] pstate: 6045 (nZCv daif +PAN -UAO)
[ 3293.931356] pc : dev_watchdog+0x324/0x330
[ 3293.931363] lr : dev_watchdog+0x324/0x330
[ 3293.931366] sp : 1001bd60
[ 3293.931371] x29: 1001bd60 x28: 0140 
[ 3293.931380] x27:  x26:  
[ 3293.931388] x25: f2fb79363000 x24: 4f7cab129018 
[ 3293.931396] x23:  x22: 0001 
[ 3293.931404] x21: f2fb79363480 x20: 4f7cab407000 
[ 3293.931412] x19:  x18:  
[ 3293.931420] x17: 10fd8218 x16: 4f7ca9f0f060 
[ 3293.931428] x15: f2fb79228510 x14:  
[ 3293.931437] x13:  x12: 4f7cab54 
[ 3293.931445] x11: 4f7cab42d000 x10:  
[ 3293.931453] x9 : 0004 x8 : 0192 
[ 3293.931461] x7 :  x6 : 0001 
[ 3293.931468] x5 :  x4 : 0008 
[ 3293.931476] x3 : 4f7caaa15750 x2 : 0004 
[ 3293.931484] x1 : 59c84c96ab783c00 x0 :  
[ 3293.931492] Call trace:
[ 3293.931500]  dev_watchdog+0x324/0x330
[ 3293.931515]  call_timer_fn+0x3c/0x178
[ 3293.931525]  __run_timers.part.0+0x200/0x330
[ 3293.931533]  run_timer_softirq+0x40/0x78
[ 3293.931544]  __do_softirq+0x168/0x384
[ 3293.931554]  irq_exit+0xb0/0xe8
[ 3293.931564]  __handle_domain_irq+0x70/0xc0
[ 3293.931572]  bcm2836_arm_irqchip_handle_irq+0x74/0xe0
[ 3293.931579]  el1_irq+0x108/0x200
[ 3293.931590]  arch_cpu_idle+0x3c/0x1c8
[ 3293.931603]  default_idle_call+0x24/0x48
[ 3293.931615]  do_idle+0x210/0x2a0
[ 3293.931623]  cpu_startup_entry+0x2c/0x30
[ 3293.931636]  secondary_start_kernel+0x154/0x1c8
[ 3293.931641] ---[ end trace 356cf2f8b780723e ]---
[ 3734.263219] br0: port 3(eth1) entered disabled state
[ 3737.505916] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.523763] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.541622] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.559099] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.576635] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.593932] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.611136] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
[ 3737.628048] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped
...

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
 

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Thiago Vincenzi Conrado]

hey guys, we create our namespace using ip netns add.
Each nameSpace has it's ipv6 and ipv4.
We notice that the ipv6 ping continues to report, but the namespace at 
/run/netns does not exist anymore.

is it possible to find the namespace using the ipv6 info?

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

[Ken Perkins]

I've also seen this with kernel 5.3.0-40-generic (Default with 19.10 and
18.04.04 LTS). Lenovo X1 with Intel i7-10710u and AC 9560

[2.861512] iwlwifi :00:14.3: enabling device ( -> 0002)
[2.886678] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
[2.886992] iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
[2.957792] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, 
REV=0x354
[3.993914] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
[3.993992] iwlwifi :00:14.3: Start IWL Error Log Dump:
[3.993994] iwlwifi :00:14.3: Status: 0x, count: -1882382615
[3.993995] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
[3.993996] iwlwifi :00:14.3: 0xDBCE3CFD | ADVANCED_SYSASSERT  
[3.993997] iwlwifi :00:14.3: 0xBD97B500 | trm_hw_status0
[3.993998] iwlwifi :00:14.3: 0xD7117653 | trm_hw_status1
[3.993998] iwlwifi :00:14.3: 0xF5F2EB57 | branchlink2
[3.993999] iwlwifi :00:14.3: 0x9B39FEF9 | interruptlink1
[3.994000] iwlwifi :00:14.3: 0xB2A3CEE9 | interruptlink2
[3.994000] iwlwifi :00:14.3: 0xCA222955 | data1
[3.994001] iwlwifi :00:14.3: 0xF44FBCC7 | data2
[3.994002] iwlwifi :00:14.3: 0xEE8D27D9 | data3
[3.994002] iwlwifi :00:14.3: 0xAFC8456A | beacon time
[3.994003] iwlwifi :00:14.3: 0x9AB5BE48 | tsf low
[3.994004] iwlwifi :00:14.3: 0xF38BEF03 | tsf hi
[3.994004] iwlwifi :00:14.3: 0x39BDB17C | time gp1
[3.994005] iwlwifi :00:14.3: 0xC1A8E7FD | time gp2
[3.994005] iwlwifi :00:14.3: 0x4D1F50A7 | uCode revision type
[3.994006] iwlwifi :00:14.3: 0x73AEC515 | uCode version major
[3.994007] iwlwifi :00:14.3: 0x1CE1133D | uCode version minor
[3.994007] iwlwifi :00:14.3: 0x7BC1ED24 | hw version
[3.994008] iwlwifi :00:14.3: 0x79824309 | board version
[3.994009] iwlwifi :00:14.3: 0xC1BFAA89 | hcmd
[3.994009] iwlwifi :00:14.3: 0xADE45947 | isr0
[3.994010] iwlwifi :00:14.3: 0xA25E02D6 | isr1
[3.994010] iwlwifi :00:14.3: 0x833363D2 | isr2
[3.994011] iwlwifi :00:14.3: 0x1AC562DF | isr3
[3.994012] iwlwifi :00:14.3: 0xE80F3DF6 | isr4
[3.994012] iwlwifi :00:14.3: 0xE602AE3E | last cmd Id
[3.994013] iwlwifi :00:14.3: 0xC2989879 | wait_event
[3.994014] iwlwifi :00:14.3: 0x43276623 | l2p_control
[3.994014] iwlwifi :00:14.3: 0xF885020C | l2p_duration
[3.994015] iwlwifi :00:14.3: 0x80B661F2 | l2p_mhvalid
[3.994015] iwlwifi :00:14.3: 0x95039050 | l2p_addr_match
[3.994016] iwlwifi :00:14.3: 0x16C3FB52 | lmpm_pmg_sel
[3.994017] iwlwifi :00:14.3: 0x786AD9A2 | timestamp
[3.994017] iwlwifi :00:14.3: 0xFEB64616 | flow_handler
[3.994051] iwlwifi :00:14.3: Start IWL Error Log Dump:
[3.994052] iwlwifi :00:14.3: Status: 0x, count: 7
[3.994053] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
[3.994053] iwlwifi :00:14.3: 0x | umac branchlink1
[3.994054] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2
[3.994055] iwlwifi :00:14.3: 0x | umac interruptlink1
[3.994055] iwlwifi :00:14.3: 0x | umac interruptlink2
[3.994056] iwlwifi :00:14.3: 0x0003 | umac data1
[3.994056] iwlwifi :00:14.3: 0x2302 | umac data2
[3.994057] iwlwifi :00:14.3: 0x01300202 | umac data3
[3.994058] iwlwifi :00:14.3: 0x0030 | umac major
[3.994058] iwlwifi :00:14.3: 0x4FA0041F | umac minor
[3.994059] iwlwifi :00:14.3: 0x5D0F | frame pointer
[3.994060] iwlwifi :00:14.3: 0xC0887F58 | stack pointer
[3.994060] iwlwifi :00:14.3: 0x | last host cmd
[3.994061] iwlwifi :00:14.3: 0x | isr status reg
[3.994079] iwlwifi :00:14.3: Fseq Registers:
[3.994082] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE
[3.994084] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
[3.994086] iwlwifi :00:14.3: 0x2DE993BB | FSEQ_CNVIO_INIT_VERSION
[3.994088] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
[3.994090] iwlwifi :00:14.3: 0x51BA0460 | FSEQ_TOP_CONTENT_VERSION
[3.994093] iwlwifi :00:14.3: 0x0140B0CE | FSEQ_ALIVE_TOKEN
[3.994095] iwlwifi :00:14.3: 0xF7FBE573 | FSEQ_CNVI_ID
[3.994097] iwlwifi :00:14.3: 0x601005B0 | FSEQ_CNVR_ID
[3.994099] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP
[3.994104] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
[3.994108] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[3.994142] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[3.994171] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c6f, CPU2 Status: 
0x3
[3.994172] iwlwifi :00:14.3: Failed to start RT ucode: -110
[3.994174] iwlwifi :00:14.3: Firmware 

[Kernel-packages] [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown

[Leonard]

First: I solved the reboot problem. I removed the kernel parameter
"reboot=p" from /etc/default/grub.

Second: I found the following message in /var/log/syslog.1: "Feb 22
13:09:38 MSI kernel: [1.183278] ACPI: If an ACPI driver is available
for this device, you should use it instead of the native driver". Could
that be the problem? If that is the problem, how to get another ACPI
driver?

I attached the whole syslog.1 file, probably there is more useful
information for you.

Leonard

** Attachment added: "/var/log/syslog.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860800/+attachment/5330423/+files/syslog.1

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

Title:
  Ubuntu 19.10 doesn't shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello guys,

  I can't shutdown Ubuntu 19.10. When I try, the shutdown screen
  appears. The first two dots below the ubuntu logo, turn orange and
  then it freezes. Reboot works fine.

  The debug-shell is no use, because at the freeze point I can't type in
  commands.  When I press ESC to see what's going on during shutdown,
  the last message to appear ist "[Some weird number] reboot: power
  down. Last time I pressed ESC during shutdown the "weird number" was
  85.270119. I also tried to shutdown with the terminal commands "sudo
  shutdown now", "sudo shutdown -P now", "sudo shutdown -h now",
  "poweroff" and "sudo poweroff -f". All of them had the effect as
  describe above except the command "sudo poweroff -f". After I typed in
  the command, I authenticated and following messages appeared:
  "Powering off...". At this point it freezed. I could still see the
  desktop and every visible window, but I couldn't perform any actions;
  not even keyboard shortcuts worked. It also did not help to change
  'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to
  'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run
  "update-grub".

  Once the following command combo did work: "sudo swapoff -a &&
  systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't
  work any more.

  In the application "Additional Drivers" I selected the proprietary
  and tested driver of NVIDIA, but I can't to this for my WLAN-Card
  (correct word?), because the "Additional Drivers" says it's not working,
  but my WLAN works fine. I've got only Bluetooth problems. The displayed
  name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band
  Wireless-AC 7260)". I also tried to manually install a driver it didn't
  help.

   When I wake up the laptop, a black screen appears with some error
  messages, but only for a very short time so I can't make a photo of it.
  I tried once and the text was unreadable.

  I have the latest BIOS and my Computer model is MSI PX60 2QD.

  It doesn't work with Arch Linux either.

  Thanks for your help :)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leonard1724 F pulseaudio
   /dev/snd/controlC1:  leonard1724 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-18 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. PX60 2QD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-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: 11/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H6IMS.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H6
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: PX60 2QD
  dmi.product.sku: To be filled by O.E.M.
  

[Kernel-packages] [Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug

[You-Sheng Yang]

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1864284

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

Title:
  r8152 init may take up to 40 seconds at initialization with Dell
  WD19/WD19DC during hotplug

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  New

Bug description:
  TBD

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2014 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 04:07:20 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95
  InstallationDate: Installed on 2020-01-16 (37 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IwConfig:
   enp1s0no wireless extensions.
   
   enxd8d090035306  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Latitude 3310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* 
+pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
   linux-backports-modules-5.0.0-1037-oem-osp1  N/A
   linux-firmware   1.173.15
  SourcePackage: linux-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.51.2[V2 AMI]
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3310
  dmi.product.sku: 0A13
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[Hui Wang]

-1019 kernel should be in the eoan-proposed channel.

And I tried to setup the 6in4 on my host laptop, it didn't work, maybe
the ISP block the packets because of GFW of china.

And since the dwc2 also has this problem, it looks this issue has
nothing to do with usb host driver,  could you plug a different
usb->ethernet (different brand from lan78xx) and test with this
usb->ethernet, let us see if you could still reproduce the problem?

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and 
network load. Happened a few times (every time) when I tried to download a 
gparted zip release (~350 MiB) directly to the SD card, and then finally when I 
tried to scp the finished download from a desktop onto RPi's card.
  Didn't collect information when it happened, but kept a copy of kern.log. 
Here's the relevant part:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  

[Kernel-packages] [Bug 1851304] Re: BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 - can't see 5Ghz Mesh Network

[Launchpad Bug Tracker]

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

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

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

Title:
  BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 - can't see
  5Ghz Mesh Network

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Pop!_OS 19.10
  Release:  19.10

  apt-cache policy bcmwl-kernel-source 
  bcmwl-kernel-source:
Installed: 6.30.223.271+bdcom-0ubuntu5
Candidate: 6.30.223.271+bdcom-0ubuntu5
Version table:
   *** 6.30.223.271+bdcom-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected to be able to use the NIC on a Mesh Network.

  Instead only 2.4Ghz is found/connected, which perform really bad <10mbps on a 
300mbps line.
  When using a "normal" dual band router the NIC finds 5Ghz network fine also 
connects fine this, now the performance is round 300mbps. When testing other 
nic/devices on the mesh network the performance is round 300mbps - hence the 
mesh network works fine.

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

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

[Kernel-packages] [Bug 1863325] Re: bionic/linux-aws: 4.15.0-1061.65 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863350
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 21. February 2020 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1863317
bionic/linux-aws/aws-kernel: bug 1863315
xenial/linux-aws-hwe: bug 1863320
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1061.65 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1863350
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Friday, 21. February 2020 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1863317
bionic/linux-aws/aws-kernel: bug 1863315
xenial/linux-aws-hwe: bug 1863320
  variant: debs

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

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

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

[packet]

Hex dump of EDID (without ASCII representation due to line wrapping):

packet@xps:~$ cat 
/sys/devices/pci\:00/\:00\:02.0/drm/card0/card0-eDP-1/edid | hexdump
000 ff00   00ff 104d 14ad  
010 1c2a 0401 1da5 7811 de0e a350 4c54 2699
020 500f 0054  0101 0101 0101 0101 0101
030 0101 0101 0101 d04d a000 70f0 803e 2030
040 0035 a526 0010 1800 a6a4 a000 70f0 803e
050 2030 0035 a526 0010 1800  fe00 3000
060 3952 4b39 4c80 3151  3144  
070 0200 0341 0128 0012 0b00 0a01 2020 4100
080

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

[packet]

Decodes to:

packet@xps:~$ cat 
/sys/devices/pci\:00/\:00\:02.0/drm/card0/card0-eDP-1/edid | 
edid-decode 
edid-decode (hex):

00 ff ff ff ff ff ff 00 4d 10 ad 14 00 00 00 00 
2a 1c 01 04 a5 1d 11 78 0e de 50 a3 54 4c 99 26 
0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 
01 01 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20 
35 00 26 a5 10 00 00 18 a4 a6 00 a0 f0 70 3e 80 
30 20 35 00 26 a5 10 00 00 18 00 00 00 fe 00 30 
52 39 39 4b 80 4c 51 31 33 33 44 31 00 00 00 00 
00 02 41 03 28 01 12 00 00 0b 01 0a 20 20 00 41 



EDID version: 1.4
Manufacturer: SHP Model 5293 Serial Number 0
Made in week 42 of 2018
Digital display
8 bits per primary color channel
DisplayPort interface
Maximum image size: 29 cm x 17 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:4:4
Default (sRGB) color space is primary color space
First detailed timing includes the native pixel format and preferred refresh 
rate
Color Characteristics
  Red:   0.6396, 0.3291
  Green: 0.2998, 0.5996
  Blue:  0.1494, 0.0595
  White: 0.3125, 0.3281
Established Timings I & II: none
Standard Timings: none
Detailed mode: Clock 533.250 MHz, 294 mm x 165 mm
   3840 3888 3920 4000 ( 48  32  80)
   2160 2163 2168  (  3   5  54)
   -hsync -vsync
   VertFreq: 59.997 Hz, HorFreq: 133.312 kHz
Detailed mode: Clock 426.600 MHz, 294 mm x 165 mm
   3840 3888 3920 4000 ( 48  32  80)
   2160 2163 2168  (  3   5  54)
   -hsync -vsync
   VertFreq: 47.997 Hz, HorFreq: 106.650 kHz
Alphanumeric Data String: 0R99K
Manufacturer-Specified Display Descriptor (0x00): 00 00 00 02 41 03 28 01 12 00 
00 0b 01 0a 20 20  A.(...

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.0-994-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 18:51:15 2019
  DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-11-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic 
root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1

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

[packet]

@tjaalton I recently switched to Debian, it's difficult for me now to
test Ubuntu kernels. I tried on i915.enable_psr=0 on broken Debian
kernel linux-image-5.4.0-4-amd64 (5.4.19+1): Screen corruption
persisted. Let me know if you need to have it tested with an Ubuntu
kernel, I'd try Ubuntu 19.10 live usb thumbdrive then.

@kent-jclin I guess your question for EDID data was already answered. In
case it wasn't, this is what I got from /sys:

packet@xps:~$ cat 
/sys/devices/pci\:00/\:00\:02.0/drm/card0/card0-eDP-1/edid | hexdump -C
  00 ff ff ff ff ff ff 00  4d 10 ad 14 00 00 00 00  |M...|
0010  2a 1c 01 04 a5 1d 11 78  0e de 50 a3 54 4c 99 26  |*..x..P.TL.&|
0020  0f 50 54 00 00 00 01 01  01 01 01 01 01 01 01 01  |.PT.|
0030  01 01 01 01 01 01 4d d0  00 a0 f0 70 3e 80 30 20  |..Mp>.0 |
0040  35 00 26 a5 10 00 00 18  a4 a6 00 a0 f0 70 3e 80  |5.&..p>.|
0050  30 20 35 00 26 a5 10 00  00 18 00 00 00 fe 00 30  |0 5.&..0|
0060  52 39 39 4b 80 4c 51 31  33 33 44 31 00 00 00 00  |R99K.LQ133D1|
0070  00 02 41 03 28 01 12 00  00 0b 01 0a 20 20 00 41  |..A.(...  .A|
0080

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1837828] Re: alsa/sof: let legacy hda driver and sof driver co-exist

[Hui Wang]

Verified the patchset could detect the dmic automatically on the eoan
kernel -41.


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

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

Title:
  alsa/sof: let legacy hda driver and sof driver co-exist

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

Bug description:
  [Impact]
  So far, if we want the sof driver to work, we need to blacklist
  snd_hda_intel.ko, but on some paltforms with nv hdmi or amd hdmi,
  we need these two driver co-exist.

  [Fix]
  Intel sent the patches to fix this issue, although it is not merged yet,
  but I guess they will pass the review and be merged. So i backported them
  first.

  [Test Case]
  remove snd_hda_intel.ko from blacklist, the two drivers (sof and hda)
  worked well.

  [Regression Risk]
  Low. We already tested these patches on some Dell machines. and comunity
  including endlessm and goole all tested these patches.

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

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

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[mlx]

> Looks like to setup a 6in4 tunnel, I need a static public IP first

I don't think that static IP is needed to make it work at least
temporarily, I don't have a static one either, just public. You only
need to have public IP on the device you can manage - e.g. router at
home, and make sure that raspberry has a static internal address. Then,
in the router's firewall/forwarding settings, either set raspberry as
the DMZ host, or set forward anything from the remote tunnel IP to
raspberry.

That being said, if are behind a carrier NAT which you can't manage, you
won't be able to set up the tunnel.

I've just tried the switch to dwc2 driver, it didn't help. (still on
~1018 kernel).

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and 
network load. Happened a few times (every time) when I tried to download a 
gparted zip release (~350 MiB) directly to the SD card, and then finally when I 
tried to scp the finished download from a desktop onto RPi's card.
  Didn't collect information when it happened, but kept a copy of kern.log. 
Here's the relevant part:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  

[Kernel-packages] [Bug 1863978] Re: boot failing - unable to handle kernel paging request - followed by oops

[Augustin]

We are also affected on this problem on 3 Ubuntu 18.04 vms since the
kernel 5.0.0-1032-azure has been installed (automatically installed
after a reboot of the server).

The Linux vms with older kernel (that have not been restarted) are not
affected.

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

Title:
  boot failing - unable to handle kernel paging request - followed by
  oops

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  After update to Ubuntu 5.0.0-1032.34-azure 5.0.21, VM is not able to
  boot anymore.

  Keeps stuck in logging "soft lockup - CPU#xxx stuck for xxs" with
  random process (different on each startup).

  Full logs below.

  Relevant boot logs:
  (...)
  [  OK  ] Started 
/var/lib/waagent/Microsoft.…0.0.7820/scripts/enableHandler.py.
  [   14.836987] PKCS#7 signature not signed with a trusted key
  [   14.856290] PKCS#7 signature not signed with a trusted key
  [   15.123087] BUG: unable to handle kernel paging request at 3fa9
  [   15.123905] #PF error: [normal kernel read fault]
  [   15.123905] PGD 80084ab2c067 P4D 80084ab2c067 PUD 8586cb067 PMD 0 
  [   15.135982] Oops:  [#1] SMP PTI
  [   15.135982] CPU: 4 PID: 3561 Comm: microsoft-depen Tainted: P   OE 
5.0.0-1032-azure #34-Ubuntu
  [   15.135982] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   15.135982] RIP: 0010:iterate_extants+0x155/0x380 
[microsoft_dependency_agent]
  [   15.135982] Code: ab c0 4c 89 e7 e8 bb 9b 0c e8 49 8b 44 24 08 48 85 c0 74 
71 4d 8b 7c 24 08 49 83 ef 68 75 0b eb 64 49 83 ea 68 4d 89 d7 74 5b <41> 0f b7 
47 10 83 e0 f7 66 83 f8 02 75 44 41 80 bf 01 02 00 00 06
  [   15.171900] RSP: 0018:bd46489cbb10 EFLAGS: 00010216
  [   15.171900] RAX: 4001 RBX: bd46489cbb30 RCX: 
0de9
  [   15.171900] RDX: 0001 RSI: 0008 RDI: 
a9ae5280
  [   15.171900] RBP: bd46489cbb80 R08: 0001 R09: 
024f
  [   15.171900] R10: bd46489cbb98 R11:  R12: 
a9ae5280
  [   15.171900] R13: c0ab59d0 R14:  R15: 
3f99
  [   15.171900] FS:  7f365b7e1440() GS:98541dd0() 
knlGS:
  [   15.171900] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.171900] CR2: 3fa9 CR3: 00084c1c6002 CR4: 
003606e0
  [   15.171900] DR0:  DR1:  DR2: 

  [   15.171900] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   15.171900] Call Trace:
  [   15.171900]  ? bs_release+0x1b0/0x1b0 [microsoft_dependency_agent]
  [   15.171900]  bs_open+0x2fd/0x580 [microsoft_dependency_agent]
  [   15.171900]  ? bs_open+0x2fd/0x580 [microsoft_dependency_agent]
  [   15.171900]  ? bs_write+0x90/0x90 [microsoft_dependency_agent]

  (...)
  [   45.331952] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [nginx:4876]
  [   45.336115] Modules linked in: microsoft_dependency_agent(POE) 
bluechannel(POE) veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype br_netfilter bridge stp llc xt_owner iptable_security 
aufs overlay xt_conntrack xt_tcpudp iptable_filter xt_nat iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter 
nls_iso8859_1 kvm_intel kvm irqbypass serio_raw hv_balloon joydev sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel hid_generic aes_x86_64 hid_hyperv crypto_simd 
cryptd hyperv_fb glue_helper cfbfillrect pata_acpi hyperv_keyboard hid 
hv_netvsc cfbimgblt cfbcopyarea hv_utils
  [   45.395981] CPU: 2 PID: 4876 Comm: nginx Tainted: P  DOE 
5.0.0-1032-azure #34-Ubuntu
  [   45.400558] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   45.408757] RIP: 0010:hv_qlock_wait+0x25/0x60
  [   45.411928] Code: 38 be 00 5d c3 0f 1f 44 00 00 55 48 89 e5 53 65 8b 05 2f 
75 df 57 a9 00 00 10 00 75 0d 9c 5b fa 0f b6 07 40 38 c6 74 05 53 9d <5b> 5d c3 
b9 f0 00 00 40 0f 32 0f 1f 44 00 00 eb ed 48 c1 e2 20 bf
  [   45.424104] RSP: 0018:bd46493a3d60 EFLAGS: 0246 ORIG_RAX: 
ff12
  [   45.431986] RAX:  RBX: 0246 RCX: 
40f0
  [   45.437191] RDX:  RSI: 0003 RDI: 
a9ae5280
  [   45.440905] RBP: bd46493a3d68 R08: 0009 R09: 
00d8
  [   45.447992] R10:  R11:  R12: 
98541dca2000
  [   45.452055] R13: 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[mlx]

Where can I find the ~1019 kernel? The repositories are still at ~1018.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and 
network load. Happened a few times (every time) when I tried to download a 
gparted zip release (~350 MiB) directly to the SD card, and then finally when I 
tried to scp the finished download from a desktop onto RPi's card.
  Didn't collect information when it happened, but kept a copy of kern.log. 
Here's the relevant part:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  
bcm2836_arm_irqchip_handle_irq+0x74/0xe0
  Feb  4 23:42:59 rpi3 kernel: [  571.879037]  el1_irq+0x108/0x200
  Feb  4 23:42:59 rpi3 kernel: [  571.879050]  arch_cpu_idle+0x3c/0x1c8
  Feb  4 23:42:59 rpi3 kernel: [  571.879069]  default_idle_call+0x24/0x48
  Feb  4 23:42:59 rpi3 kernel: [  571.879081]  do_idle+0x210/0x2a0
  Feb  4 23:42:59 rpi3 kernel: [  571.879091]  cpu_startup_entry+0x28/0x30
  Feb  4 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[mlx]

Hi. The USB ports still work fine - I use a USB keyboard to correctly
reboot the machine when it gets stuck. My most recent replication was
with ~1017 kernel, will try the newer ones.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and 
network load. Happened a few times (every time) when I tried to download a 
gparted zip release (~350 MiB) directly to the SD card, and then finally when I 
tried to scp the finished download from a desktop onto RPi's card.
  Didn't collect information when it happened, but kept a copy of kern.log. 
Here's the relevant part:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  
bcm2836_arm_irqchip_handle_irq+0x74/0xe0
  Feb  4 23:42:59 rpi3 kernel: [  571.879037]  el1_irq+0x108/0x200
  Feb  4 23:42:59 rpi3 kernel: [  571.879050]  arch_cpu_idle+0x3c/0x1c8
  Feb  4 23:42:59 rpi3 kernel: [  571.879069]  default_idle_call+0x24/0x48
  Feb  4 23:42:59 rpi3 kernel: [  

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)

[Hui Wang]

Looks like to setup a 6in4 tunnel, I need a static public IP first, but
I don't have that IP.

And you could do a test, let us change the usb host driver, if the
problem can't be reproduced anymore, it proves it is a problem on usb
host driver.

To change the usb host driver:
add dtoverlay=dwc2 in the config.txt for RPI3B+ board.

to check if usb host driver is changed:
lsusb -t (it will show dwc2 instead of dwc_otg).

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO and
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and 
network load. Happened a few times (every time) when I tried to download a 
gparted zip release (~350 MiB) directly to the SD card, and then finally when I 
tried to scp the finished download from a desktop onto RPi's card.
  Didn't collect information when it happened, but kept a copy of kern.log. 
Here's the relevant part:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  
bcm2836_arm_irqchip_handle_irq+0x74/0xe0
  Feb  4