date:20210402

[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/1715866

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Expired

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1913890] Re: My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have a fingerprint sensor that worked with windows 10. Ubuntu can't even recognise it . It wont eve

[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/1913890

Title:
  My device is ASUS ViviBook x507. I installed Ubuntu 20.04 LTS. I have
  a fingerprint sensor that worked with windows 10. Ubuntu can't even
  recognise it . It wont even show up in lsusb, lspci or lshw.

Status in linux package in Ubuntu:
  Expired

Bug description:
  (base) akash@Akash-Asus:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  (base) akash@Akash-Asus:~$ ^C
  (base) akash@Akash-Asus:~$ fprintd-enroll
  list_devices failed: No devices available
  (base) akash@Akash-Asus:~$ ^C
  (base) akash@Akash-Asus:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 08)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#1 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO UART Controller #0 (rev 21)
  00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO SPI Controller #0 (rev 21)
  00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital 
IO Controller (rev 21)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI 
Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2)
  02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  (base) akash@Akash-Asus:~$ lshw
  WARNING: you should run this program as super-user.
  akash-asus  
  description: Computer
  width: 64 bits
  capabilities: smp vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 8GiB
   *-cpu
product: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
size: 1132MHz
capacity: 3400MHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 
x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 
3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
md_clear flush_l1d cpufreq
   *-pci
description: Host bridge
product: Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 08
width: 32 bits
clock: 33MHz
configuration: driver=skl_uncore
resources: irq:0
  *-display
   description: VGA compatible controller
   product: UHD Graphics 620
   vendor: Intel Corporation
   physical id: 2

[Kernel-packages] [Bug 1913947] Re: Bluetooth audio underruns, dropouts or crackling sound

[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/1913947

Title:
  Bluetooth audio underruns, dropouts or crackling sound

Status in linux package in Ubuntu:
  Expired

Bug description:
  The audio isn't in sync with video (ex. with youtube).
  Sometimes the audio is missing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simone 2131 F pulseaudio
   /dev/snd/controlC0:  simone 2131 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 15:56:52 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: CMT-SBT20
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DK.305:bd07/16/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DK_X512DK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DK_X512DK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

We now have a working solution for some models written in Python, but this is 
only a workaround.
It would be nice if someone experienced with Linux drivers could work on a 
cleaner solution.

If I could help in any way, please don't hesitate to contact me.

Mohamed.

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

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

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

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

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

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

[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot

2021-04-02 Thread Ben Wibking

(Obviously, I can't run apport-collect since it panics on boot.)

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

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

Title:
  hirsute live cd kernel panic on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a
  Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI
  Certificate Authority) enabled.

  The GRUB boot menu loads, and I continue with the default option. I
  immediately get a kernel panic (screenshot attached).

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

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

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

@magellan-2000 fixed the press and holding backspace behaviour.

I restored the use off the corner top right area to light on the
touchpad because in some application, F8 can be already use for another
use case.

Mohamed.

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

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

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

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

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

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

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

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 1922403

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: hirsute

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

Title:
  hirsute live cd kernel panic on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a
  Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI
  Certificate Authority) enabled.

  The GRUB boot menu loads, and I continue with the default option. I
  immediately get a kernel panic (screenshot attached).

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

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

[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot

2021-04-02 Thread Ben Wibking

** Summary changed:

- hirsute live cd kernel panic
+ hirsute live cd kernel panic on boot

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

Title:
  hirsute live cd kernel panic on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a
  Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI
  Certificate Authority) enabled.

  The GRUB boot menu loads, and I continue with the default option. I
  immediately get a kernel panic (screenshot attached).

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

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

[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic

2021-04-02 Thread Ben Wibking

changed to 'linux' to reflect that this is a kernel bug

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  hirsute live cd kernel panic on boot

Status in linux package in Ubuntu:
  New

Bug description:
  I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a
  Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI
  Certificate Authority) enabled.

  The GRUB boot menu loads, and I continue with the default option. I
  immediately get a kernel panic (screenshot attached).

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

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

[Kernel-packages] [Bug 1922406] [NEW] Intel AX210 Wi-Fi card does not work since updating to 1.196

2021-04-02 Thread Alberto Abrao

Public bug reported:

Running 21.04, updated daily.

Since updating the linux-firmware package yesterday, the Wireless card
does not work with current kernel (5.11.0-13).

The error message is as follows:

Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT 
ucode: -110
Apr 02 21:15:18 Lenovo-V15-eIIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

It **does** work with 5.11.0-11 (previous version)

Distro: Ubuntu 21.04 (Hirsute Hippo) 
Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL  
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020 
CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 
cache: 4 MiB

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

** Description changed:

  Running 21.04, updated daily.
  
- Since updating this package yesterday, the Wireless card does not work
- with current kernel (5.11.0-13).
+ Since updating the linux-firmware package yesterday, the Wireless card
+ does not work with current kernel (5.11.0-13).
+ 
+ The error message is as follows:
  
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
- Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1
+ Apr 02 21:15:18 Lenovo-V15-eIIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1
  
- It does work with 5.11.0-11 (previous version I had installed).
+ It **does** work with 5.11.0-11 (previous version)
+ 
+ Distro: Ubuntu 21.04 (Hirsute Hippo) 
+ Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020 
+ CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

Title:
  Intel AX210 Wi-Fi card does not work since updating to 1.196

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Running 21.04, updated daily.

  Since updating the linux-firmware package yesterday, the Wireless card
  does not work with current kernel (5.11.0-13).

  The error message is as follows:

  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting 
for PNVM load!
  Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start 
RT ucode: -110
  Apr 02 21:15:18 Lenovo-V15-eIIL kernel: iwlwifi :01:00.0: 
iwl_trans_send_cmd bad state = 1

  It **does** work with 5.11.0-11 (previous version)

  Distro: Ubuntu 21.04 (Hirsute Hippo) 
  Machine:   Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW 
date: 12/23/2020 
  CPU:   Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP 
L2 cache: 4 MiB

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

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

[Kernel-packages] [Bug 1922403] [NEW] hirsute live cd kernel panic

You have been subscribed to a public bug:

I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a
Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI
Certificate Authority) enabled.

The GRUB boot menu loads, and I continue with the default option. I
immediately get a kernel panic (screenshot attached).

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

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

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

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

@magellan-2000 I replaced the leftshift by numlock key.
It works the same way but this time enter hit do not goes up on a spreadsheet.

Also I comment the code part which enable numpad through the touchpad
right top corner, F8 seems an handier solution.

Mohamed.

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

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

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

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

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

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

[Kernel-packages] [Bug 1920549] Re: Unable to decrypt disk on boot

2021-04-02 Thread Ray McBride

To add to this, I have a password also set on grub which I can
successfully enter before this problem occurs. Issue still exists in
kernel 5.8.0-48

Thanks

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

Title:
  Unable to decrypt disk on boot

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  Good day,

  I enabled disk encryption when installing Ubuntu and it has been
  working flawlessly till kernel 5.8.0-45.51 was installed.

  I keep getting this error when entering my password: "cryptsetup
  failed, bad password or options". I was somehow able to fall back into
  some shell while booting and it seems that any characters I type show
  up as diamonds "♦", except for the numbers. I also came across this
  thread which talks about a similar problem
  https://askubuntu.com/questions/1220022/keyboard-types-only-numbers-
  while-letters-are-typed-like-diamonds

  Switching back to 5.8.0-44 fixes the issue for me.

  I'm currently on Ubuntu 20.10
  Would be happy to provide more details.

  Thanks!

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

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

[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow

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

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

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

Title:
  net/mlx5e: Add missing capability check for uplink follow

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Since older firmware may not support the uplink state setting, this
  can lead to problems.

  * Now expose firmware indication that it supports setting eswitch
  uplink state to follow the physical link.

  * If a kernel without the backport is used on an adapter which does
  not have the latest adapter firmware, the adapter silently drops
  outgoing traffic.

  * This is a regression which was introduced with kernel 5.4.0-48.

  [Fix]

  * upstream fix (as in 5.11):
    9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add 
missing capability check for uplink follow"

  * backport for focal: https://launchpadlibrarian.net/529543695/0001
  -Backport-net-mlx5e-Add-missing-capability-check-for-.patch

  * backport for groovy: https://launchpadlibrarian.net/529775887/0001
  -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch

  [Test Case]

  * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or
  20.10 on LPAR, are needed.

  * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached
  and firmware 16.29.1006 or earlier.

  * Assign an IP address to the adapters on both systems and try to ping
  one node from the other.

  * The ping will just fail with the stock Ubuntu kernels (not having
  the patch), but will succeed with kernels that incl. the patches (like
  the test builds from the PPA mentioned below).

  * Due to the lack of hardware this needs to be verified by IBM.

  [Regression Potential]

  * Undesired / erroneous behavior in case the modified if condition is
  assembled in a wrong way.

  * Again wrong behavior in case the modification of the capability bits
  in mlx5_ifc_cmd_hca_cap_bits are wrong.

  * All modification are limited to the mlx5 driver only.

  * The changes are relatively limited with effectively two lines
  removed and 4 added (three of them adjustments of the capability bits
  only).

  * The modifications were done and tested by IBM and reviewed by
  Mellanox (see LP comments),   based on a PPA test build.

  [Other]

  * The above patch/commit was upstream accepted with kernel 5.11.

  * Hence the patch is not needed for hirsute, just needs to be SRUed
  for groovy and focal.

  * The commit couldn't be cleanly cherry-picked, mainly due to changed
  context, hence the backport(s).

  __

  Expose firmware indication that it supports setting eswitch uplink state
  to follow (follow the physical link). Condition setting the eswitch
  uplink admin-state with this capability bit. Older FW may not support
  the uplink state setting.

  Available fix with kernel 5.11.
  
https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d

  Now required for Ubuntu 20.04 via backport patch.

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

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

[Kernel-packages] [Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases

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

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

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

Title:
  Fix implicit declaration warnings for kselftests/memfd test on newer
  releases

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  While debugging bug 1910277, I found that the test compilation will
  print some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;

  It's harmless but fixing this we can make the test report easier to
  read.

  [Fix]
  * 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")

  This fix can be cherry-picked into F/F-oem-5.6/G and compiled without
  any problem. Older kernel does not have this issue since they're
  missing some other commits.

  [Test Case]
  Build the memfd test in tools/testing/selftests/ with:
sudo make TARGETS=memfd

  With this fix, these warnings will be gone.

  [Where problems could occur]
  This fix is just for fixing the test case compilation, so it's not
  affecting real kernel functionality.

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

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

[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation

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

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

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

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

Title:
  Bcache bypasse writeback on caching device with fragmentation

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]
  This bug in bcache affects I/O performance on all versions of the kernel 
[correct versions affected]. It is particularly negative on ceph if used with 
bcache.

  Write I/O latency would suddenly go to around 1 second from around 10
  ms when hitting this issue and would easily be stuck there for hours
  or even days, especially bad for ceph on bcache architecture. This
  would make ceph extremely slow and make the entire cloud almost
  unusable.

  The root cause is that the dirty bucket had reached the 70 percent
  threshold, thus causing all writes to go direct to the backing HDD
  device. It might be fine if it actually had a lot of dirty data, but
  this happens when dirty data has not even reached over 10 percent, due
  to having high memory fragmentation. What makes it worse is that the
  writeback rate might be still at minimum value (8) due to the
  writeback percent not reached, so it takes ages for bcache to really
  reclaim enough dirty buckets to get itself out of this situation.

  [Fix]

  * 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
  fragmentation when update the writeback rate”

  The current way to calculate the writeback rate only considered the dirty 
sectors.
  This usually works fine when memory fragmentation is not high, but it will 
give us an unreasonably low writeback rate when we are in the situation that a 
few dirty sectors have consumed a lot of dirty buckets. In some cases, the 
dirty buckets reached  CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback)  while 
the dirty data (sectors) had not even reached the writeback_percent threshold 
(i.e., started writeback). In that situation, the writeback rate will still be 
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck 
in a non-writeback mode because of the slow writeback.

  We accelerate the rate in 3 stages with different aggressiveness:
  the first stage starts when dirty buckets percent reach above 
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
  the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
  the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).

  By default the first stage tries to writeback the amount of dirty data
  in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
  the second stage tries to writeback the amount of dirty data in one bucket
  in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
  stage tries to writeback the amount of dirty data in one bucket in
  (1 / (dirty_buckets_percent - 64)) milliseconds.

  The initial rate at each stage can be controlled by 3 configurable
  parameters:

  writeback_rate_fp_term_{low|mid|high}

  They are by default 1, 10, 1000, chosen based on testing and
  production data, detailed below.

  A. When it comes to the low stage, it is still far from the 70%
     threshold, so we only want to give it a little bit push by setting the
     term to 1, it means the initial rate will be 170 if the fragment is 6,
     it is calculated by bucket_size/fragment, this rate is very small,
     but still much more reasonable than the minimum 8.
     For a production bcache with non-heavy workload, if the cache device
     is bigger than 1 TB, it may take hours to consume 1% buckets,
     so it is very possible to reclaim enough dirty buckets in this stage,
     thus to avoid entering the next stage.

  B. If the dirty buckets ratio didn’t turn around during the first stage,
     it comes to the mid stage, then it is necessary for mid stage
     to be more aggressive than low stage, so the initial rate is chosen
     to be 10 times more than the low stage, which means 1700 as the initial
     rate if the fragment is 6. This is a normal rate
     we usually see for a normal workload when writeback happens
     because of writeback_percent.

  C. If the dirty buckets ratio didn't turn around during the low and mid
     stages, it comes to the third stage, and it is the last chance that
     we can turn around to avoid the horrible cutoff writeback sync issue,
     then we choose 100 times more aggressive than the mid stage, that
     means 17 as the initial rate if the fragment is 6. This is also

[Kernel-packages] [Bug 1921498] Re: [UBUNUT 21.04] s390/vtime: fix increased steal time accounting

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

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

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

Title:
  [UBUNUT 21.04] s390/vtime: fix increased steal time accounting

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The reported steal time on s390x is erroneously increasing and
  therefore broken.

  * This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1

  [Fix]

  * d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
  fix increased steal time accounting"

  [Test Case]

  * An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
  20.10 and 21.04 on LPAR, are needed.

  * The system needs to be configured as KVM host with one or more KVM
  guests.

  * Now put significant workload on the guest(s), so that the hypervisor starts 
to 'steal time'.
This can be best forced by having only very limited CPU resources for the 
hypervisor itself.

  * Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.

  * If the steal time starts ever growing (exponentially), the situation
  is broken.

  * In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.

  [Regression Potential]

  * The patch only changes the single line that calculates:
  account_steal_time

  * In case the account_steal_time calculation is still broken after the 
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).

  * But it will not further harm virtualization on s390x systems.

  * The modification is very limited with that one line change.

  * The commit got upstream accepted with 5.12-rc4.

  [Other]

  * Since the patch is needed for kernel higher than 5.1 and got upstream 
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.

  * The upstream commit can be cleanly cherry-picked from all three affected 
Ubuntu releases.
  __

  Description:   s390/vtime: fix increased steal time accounting
  Symptom:   Increased steal time values.
  Problem:   Commit 152e9b8676c6e ("s390/vtime: steal time exponential
     moving average") inadvertently changed the input value for
     account_steal_time() from "cputime_to_nsecs(steal)" to just
     "steal", resulting in broken increased steal time accounting.
  Solution:  Fix this by changing it back to "cputime_to_nsecs(steal)".
  Reproduction:  -
  Upstream-ID:   d54cb7d54877d529bc1e0e1f47a3dd082f73add3

  Stable tagged : kernel 5.1.

  Therefore only to be applyable for focal, groovy, hirsuite.

  Due to stable tag integration , only for integration checking..

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

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

[Kernel-packages] [Bug 1918723] Re: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] subsystem [8086:0034]: iwlwifi crash when running a software AC

2021-04-02 Thread Brieuc du Garay

Hello. I didn't see if there was an update, but I didn't experienced any
iwlwifi crash for days. I couldnt reproduce the bug for 4 days in a row.

I don't recall doing anything that could affect this in anyway.

---

System:Host: msi Kernel: 5.8.0-48-generic x86_64 bits: 64 compiler: N/A 
Desktop: KDE Plasma 5.18.5 
   Distro: Ubuntu 20.04.2 LTS (Focal Fossa) 


Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: 
kernel port: 5000 bus ID: 00:14.3 
   Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI driver: r8169 v: kernel 
   port: 3000 bus ID: 03:00.0

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

Title:
  Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370]
  subsystem [8086:0034]: iwlwifi crash when running a software AC

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi ! I didn't manage to find another software causing the crash. In my
  case, it's Velocidrone. I contacted the developpers but they don't
  know what happens to my system in that case.

  Everytime I execute the game, I get this in dmesg (like 90%, so you
  can ask me to reproduce the crash while running some debugging tool if
  you ask me | I don't know why sometimes it doesn't). That causes my PC
  Wifi to crash, as you can see.

  > Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver:
  iwlwifi v: kernel

  I also attached the full `journalctl` from today.

  ---

  ```
  [ 4232.602167] iwlwifi :00:14.3: Queue 11 is active on fifo 1 and stuck 
for 1 ms. SW [99, 108] HW [99, 108] FH TRB=0x0c010b06b
  [ 4232.602262] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 4232.602622] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 4232.602625] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [ 4232.602627] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0 
9000-pu-b0-jf-b0-46.ucode
  [ 4232.602630] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN
  [ 4232.602632] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0
  [ 4232.602634] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 4232.602636] iwlwifi :00:14.3: 0x004882DA | branchlink2
  [ 4232.602637] iwlwifi :00:14.3: 0x0047932A | interruptlink1
  [ 4232.602639] iwlwifi :00:14.3: 0xBDB6 | interruptlink2
  [ 4232.602641] iwlwifi :00:14.3: 0x0001ACAA | data1
  [ 4232.602643] iwlwifi :00:14.3: 0xFF00 | data2
  [ 4232.602644] iwlwifi :00:14.3: 0xF008 | data3
  [ 4232.602646] iwlwifi :00:14.3: 0x22404823 | beacon time
  [ 4232.602648] iwlwifi :00:14.3: 0xB1B50385 | tsf low
  [ 4232.602649] iwlwifi :00:14.3: 0x01BA | tsf hi
  [ 4232.602651] iwlwifi :00:14.3: 0x | time gp1
  [ 4232.602653] iwlwifi :00:14.3: 0x00D56C10 | time gp2
  [ 4232.602655] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 4232.602656] iwlwifi :00:14.3: 0x002E | uCode version major
  [ 4232.602658] iwlwifi :00:14.3: 0x6BF1DF06 | uCode version minor
  [ 4232.602660] iwlwifi :00:14.3: 0x0312 | hw version
  [ 4232.602662] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 4232.602663] iwlwifi :00:14.3: 0x0A43001C | hcmd
  [ 4232.602665] iwlwifi :00:14.3: 0x8002200A | isr0
  [ 4232.602667] iwlwifi :00:14.3: 0x | isr1
  [ 4232.602669] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 4232.602670] iwlwifi :00:14.3: 0x0041BCCD | isr3
  [ 4232.602672] iwlwifi :00:14.3: 0x | isr4
  [ 4232.602673] iwlwifi :00:14.3: 0x0074019C | last cmd Id
  [ 4232.602675] iwlwifi :00:14.3: 0x0001ACAA | wait_event
  [ 4232.602676] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 4232.602678] iwlwifi :00:14.3: 0x2020 | l2p_duration
  [ 4232.602680] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 4232.602681] iwlwifi :00:14.3: 0x0080 | l2p_addr_match
  [ 4232.602683] iwlwifi :00:14.3: 0x000D | lmpm_pmg_sel
  [ 4232.602684] iwlwifi :00:14.3: 0x08081425 | timestamp
  [ 4232.602686] iwlwifi :00:14.3: 0xD0BC | flow_handler
  [ 4232.602832] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 4232.602835] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [ 4232.602837] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST
  [ 4232.602838] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 4232.602840] iwlwifi :00:14.3: 0xC008885E | umac branchlink2
  [ 4232.602842] iwlwifi :00:14.3: 0xC00843E8 | umac interruptlink1
  [ 4232.602843] iwlwifi :00:14.3: 0xC00843E8 | umac interruptlink2
  [ 4232.602845] iwlwifi :00:14.3: 0x0100 | umac data1
  [ 4232.602846] iwlwifi :00:14.3: 0xC00843E8 | umac data2
  [ 4232.602848] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 4232.602849] iwlwifi :00:14.3: 0x002E | umac major
  [

[Kernel-packages] [Bug 1922397] Re: ADT test failure in proposed kernel 5.4.0-1037.38: virtualbox-guest-dkms-hwe is not building

** Attachment added: "linux-kvm-1037.vbox"
   
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922397/+attachment/5483640/+files/linux-kvm-1037.vbox

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

Title:
  ADT test failure in proposed kernel 5.4.0-1037.38:  virtualbox-guest-
  dkms-hwe is not building

Status in linux-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is the failure report:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210402_001931_2bea9@/log.gz

  By trying to reproduce in a VM with linux-kvm, the logs are explicit
  about the failure reason:

  DKMS make.log for virtualbox-guest-6.1.16 for kernel 5.4.0-1037-kvm (x86_64)
  Fri Apr  2 21:25:41 UTC 2021
  make: Entering directory '/usr/src/linux-headers-5.4.0-1037-kvm'
CC [M]  
/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest-linux.o
CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest.o
  [...]
   CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vbox_hgsmi.o
LD [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.o
AR  /var/lib/dkms/virtualbox-guest/6.1.16/build/built-in.a
Building modules, stage 2.
MODPOST 3 modules
  ERROR: "drm_gem_prime_export" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_release" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_eviction_valuable" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_tt_fini" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_crtc_helper_set_config" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_dev_register" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  [...]

  linux-kvm has "CONFIG_DRM" unset, so..it's expected to fail!
  The odd part here is that this seems to be the first failure; checking the 
ADT results in last kernel before current cycle (-1034), we can see the DKMS 
built never happened; I suspect this is related with the ADT command-line 
change between -1034 and -1037 - I'll attach both lines.

  For reference, this is the full log from the ADT test in -1034:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210225_192413_d067f@/log.gz

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

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

[Kernel-packages] [Bug 1922397] Re: ADT test failure in proposed kernel 5.4.0-1037.38: virtualbox-guest-dkms-hwe is not building

Another oddity: for some reason, installing virtualbox-guest-dkms-hwe
forces the kernel packages removal - I'm not sure why.

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

Title:
  ADT test failure in proposed kernel 5.4.0-1037.38:  virtualbox-guest-
  dkms-hwe is not building

Status in linux-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is the failure report:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210402_001931_2bea9@/log.gz

  By trying to reproduce in a VM with linux-kvm, the logs are explicit
  about the failure reason:

  DKMS make.log for virtualbox-guest-6.1.16 for kernel 5.4.0-1037-kvm (x86_64)
  Fri Apr  2 21:25:41 UTC 2021
  make: Entering directory '/usr/src/linux-headers-5.4.0-1037-kvm'
CC [M]  
/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest-linux.o
CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest.o
  [...]
   CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vbox_hgsmi.o
LD [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.o
AR  /var/lib/dkms/virtualbox-guest/6.1.16/build/built-in.a
Building modules, stage 2.
MODPOST 3 modules
  ERROR: "drm_gem_prime_export" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_release" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_eviction_valuable" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_tt_fini" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_crtc_helper_set_config" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_dev_register" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  [...]

  linux-kvm has "CONFIG_DRM" unset, so..it's expected to fail!
  The odd part here is that this seems to be the first failure; checking the 
ADT results in last kernel before current cycle (-1034), we can see the DKMS 
built never happened; I suspect this is related with the ADT command-line 
change between -1034 and -1037 - I'll attach both lines.

  For reference, this is the full log from the ADT test in -1034:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210225_192413_d067f@/log.gz

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

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

[Kernel-packages] [Bug 1922397] Re: ADT test failure in proposed kernel 5.4.0-1037.38: virtualbox-guest-dkms-hwe is not building

** Attachment added: "linux-kvm-1034.vbox"
   
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922397/+attachment/5483639/+files/linux-kvm-1034.vbox

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

Title:
  ADT test failure in proposed kernel 5.4.0-1037.38:  virtualbox-guest-
  dkms-hwe is not building

Status in linux-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is the failure report:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210402_001931_2bea9@/log.gz

  By trying to reproduce in a VM with linux-kvm, the logs are explicit
  about the failure reason:

  DKMS make.log for virtualbox-guest-6.1.16 for kernel 5.4.0-1037-kvm (x86_64)
  Fri Apr  2 21:25:41 UTC 2021
  make: Entering directory '/usr/src/linux-headers-5.4.0-1037-kvm'
CC [M]  
/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest-linux.o
CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest.o
  [...]
   CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vbox_hgsmi.o
LD [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.o
AR  /var/lib/dkms/virtualbox-guest/6.1.16/build/built-in.a
Building modules, stage 2.
MODPOST 3 modules
  ERROR: "drm_gem_prime_export" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_release" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_eviction_valuable" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_tt_fini" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_crtc_helper_set_config" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_dev_register" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  [...]

  linux-kvm has "CONFIG_DRM" unset, so..it's expected to fail!
  The odd part here is that this seems to be the first failure; checking the 
ADT results in last kernel before current cycle (-1034), we can see the DKMS 
built never happened; I suspect this is related with the ADT command-line 
change between -1034 and -1037 - I'll attach both lines.

  For reference, this is the full log from the ADT test in -1034:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210225_192413_d067f@/log.gz

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

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

[Kernel-packages] [Bug 1922397] [NEW] ADT test failure in proposed kernel 5.4.0-1037.38: virtualbox-guest-dkms-hwe is not building

Public bug reported:

This is the failure report:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/v/virtualbox-
hwe/20210402_001931_2bea9@/log.gz

By trying to reproduce in a VM with linux-kvm, the logs are explicit
about the failure reason:

DKMS make.log for virtualbox-guest-6.1.16 for kernel 5.4.0-1037-kvm (x86_64)
Fri Apr  2 21:25:41 UTC 2021
make: Entering directory '/usr/src/linux-headers-5.4.0-1037-kvm'
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest-linux.o
  CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest.o
[...]
 CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vbox_hgsmi.o
  LD [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.o
  AR  /var/lib/dkms/virtualbox-guest/6.1.16/build/built-in.a
  Building modules, stage 2.
  MODPOST 3 modules
ERROR: "drm_gem_prime_export" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
ERROR: "drm_release" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
ERROR: "ttm_bo_eviction_valuable" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
ERROR: "ttm_tt_fini" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
ERROR: "drm_crtc_helper_set_config" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
ERROR: "drm_dev_register" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
[...]

linux-kvm has "CONFIG_DRM" unset, so..it's expected to fail!
The odd part here is that this seems to be the first failure; checking the ADT 
results in last kernel before current cycle (-1034), we can see the DKMS built 
never happened; I suspect this is related with the ADT command-line change 
between -1034 and -1037 - I'll attach both lines.

For reference, this is the full log from the ADT test in -1034:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/v/virtualbox-
hwe/20210225_192413_d067f@/log.gz

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

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

Title:
  ADT test failure in proposed kernel 5.4.0-1037.38:  virtualbox-guest-
  dkms-hwe is not building

Status in linux-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is the failure report:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210402_001931_2bea9@/log.gz

  By trying to reproduce in a VM with linux-kvm, the logs are explicit
  about the failure reason:

  DKMS make.log for virtualbox-guest-6.1.16 for kernel 5.4.0-1037-kvm (x86_64)
  Fri Apr  2 21:25:41 UTC 2021
  make: Entering directory '/usr/src/linux-headers-5.4.0-1037-kvm'
CC [M]  
/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest-linux.o
CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxguest/VBoxGuest.o
  [...]
   CC [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vbox_hgsmi.o
LD [M]  /var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.o
AR  /var/lib/dkms/virtualbox-guest/6.1.16/build/built-in.a
Building modules, stage 2.
MODPOST 3 modules
  ERROR: "drm_gem_prime_export" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_release" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_bo_eviction_valuable" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "ttm_tt_fini" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_crtc_helper_set_config" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  ERROR: "drm_dev_register" 
[/var/lib/dkms/virtualbox-guest/6.1.16/build/vboxvideo/vboxvideo.ko] undefined!
  [...]

  linux-kvm has "CONFIG_DRM" unset, so..it's expected to fail!
  The odd part here is that this seems to be the first failure; checking the 
ADT results in last kernel before current cycle (-1034), we can see the DKMS 
built never happened; I suspect this is related with the ADT command-line 
change between -1034 and -1037 - I'll attach both lines.

  For reference, this is the full log from the ADT test in -1034:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/v/virtualbox-
  hwe/20210225_192413_d067f@/log.gz

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

-- 
Mailing list:

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

It is a goog idea to keep the F8 key because the top right area is a
little capricious in my case... not working everytime.

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

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

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

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

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

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

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

Another idea : we could add the down key after enter to do the same
thing.

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

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

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

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

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

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

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

Ok Mohamed... it's really bad luck for me :-(

I'm still happy with it but I would like to understand why there is the
need of left-shift enter and I'm sure there is a way to avoid it.

Anyway, Now I have a tool to enter number easily thanks to you and all
the previous workers who permit the numpad to work on Linux.

Like you achieved to make this work you will succeed in finding a way to
make the enter key work as usual.

But I have a new problem : sometimes, the numpad act as I'm pressing and
holding backspace ! All the text I was writing is erased...

Does anyone else have this problem ?

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

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

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

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

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

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

[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux

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

Title:
  psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
  focal/linux

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

Bug description:
  Testing failed on focal/linux 5.4.0-44.48:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz

  psock_snd.sh output:

  16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
  16:28:31 DEBUG| [stdout] # dgram
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # dgram bind
  16:28:31 DEBUG| [stdout] # tx: 128
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw bind
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw qdisc bypass
  16:28:31 DEBUG| [stdout] # tx: 142
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw vlan
  16:28:31 DEBUG| [stdout] # tx: 146
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw vnet hdr
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw csum_off
  16:28:31 DEBUG| [stdout] # tx: 152
  16:28:31 DEBUG| [stdout] # rx: 142
  16:28:31 DEBUG| [stdout] # rx: 100
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:31 DEBUG| [stdout] # raw min size
  16:28:31 DEBUG| [stdout] # tx: 42
  16:28:31 DEBUG| [stdout] # rx: 0
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw mtu size
  16:28:31 DEBUG| [stdout] # tx: 1514
  16:28:31 DEBUG| [stdout] # rx: 1472
  16:28:31 DEBUG| [stdout] # OK
  16:28:31 DEBUG| [stdout] # 
  16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails)
  16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # dgram mtu size
  16:28:32 DEBUG| [stdout] # tx: 1500
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long
  16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive)
  16:28:32 DEBUG| [stdout] # tx: 14
  16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable
  16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL)
  16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument
  16:28:32 DEBUG| [stdout] # raw gso min size
  16:28:32 DEBUG| [stdout] # tx: 1525
  16:28:32 DEBUG| [stdout] # rx: 1473
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails)
  16:28:32 DEBUG| [stdout] # tx: 1524
  16:28:32 DEBUG| [stdout] # rx: 1472
  16:28:32 DEBUG| [stdout] # OK
  16:28:32 DEBUG| [stdout] # 
  16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1

  This failure is similar to bug 1884234, however, this test didn't fail
  on ADT with focal/linux before 5.4.0-44.48.

To manage notifications about this bug go

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

@magellan-2000

I didn't found how to avoid this behavioour of this enter hit which goes up on 
a spreadsheet.
Instead of that, I just hit keyboard enter key to go normally down.

I update the repo to enable the top right touchpad area in order too
activate numpad (instead F8)

https://github.com/mohamed-badaoui/ux433-touchpad-numpad

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

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

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

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

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

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

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

I've tried this :

if value != EV_KEY.KEY_ENTER
events.append(InputEvent(EV_KEY.KEY_LEFTSHIFT, 1))
events.append(InputEvent(value, 1))
events.append(InputEvent(EV_SYN.SYN_REPORT, 0))
udev.send_events(events)

But I get a syntax error. I'm trying to fix this as soon as possible
because as a teacher, I have hundred notes to enter...

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

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

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

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

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

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

[Kernel-packages] [Bug 1915717] Re: Ubuntu 21.04, kernel feature request, TLS device offload for Bond

2021-04-02 Thread Jeff Lane

PR made for 5.11

** Summary changed:

- Ubuntu 21.04, kernel feature request, TLS device offload for Bond
+ [FEATURE] Hirsute: support TLS device offload for Bond

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

Title:
  [FEATURE] Hirsute: support TLS device offload for Bond

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

Bug description:
  The request here is to pull needed patches to support tls rx/tx
  offload for bond interfaces.

  patch set:
  4e5a73329051 net/tls: Except bond interface from some TLS checks
  153cbd137f0a net/tls: Device offload to use lowest netdevice in chain
  dc5809f9e2b6 net/bonding: Declare TLS RX device offload support
  89df6a810470 net/bonding: Implement TLS TX device offload
  f45583de361d net/bonding: Take update_features call out of XFRM funciton
  007feb87fb15 net/bonding: Implement ndo_sk_get_lower_dev
  5b99854540e3 net/bonding: Take IP hash logic into a helper
  719a402cf603 net: netdevice: Add operation ndo_sk_get_lower_dev

  https://www.spinics.net/lists/netdev/msg714607.html
  https://www.spinics.net/lists/netdev/msg714991.html

  *
  the set was originally applied to net/net-next
  (hashes above are from net-next tree cloned from 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git)

  *
  The set is cleanly applied on ubuntu-unstable branch
  (cloned from 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable)

  *
  the set is accepted to upstream v5.12 and thus not natively in 21.04

  UPDATE
  Pathches identified upstream in mainline at 5.12-rc1

  All patches pick cleanly from mainline into our 5.11 Hirsute tree

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

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

[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55

This is also failing on Focal and Focal-hwe-5.8, though the output is a
bit different. suspecting problem is related, though

Testing failed on F/linux 5.4.0-71.79:
armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/n/nvidia-graphics-drivers-390/20210330_013823_f2404@/log.gz

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

Title:
  nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure
  with linux/5.8.0-49.55

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running nvidia-
  graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether
  this is caused by the tested source or the kernel has, yet, to be
  determined.

  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz

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

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

[Kernel-packages] [Bug 1922223] Re: package kerneloops 0.12+git20140509-6ubuntu2 failed to install/upgrade: installed kerneloops package post-installation script subprocess returned error exit status

2021-04-02 Thread Steve Beattie

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

** Information type changed from Private Security to Public

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

Title:
  package kerneloops 0.12+git20140509-6ubuntu2 failed to
  install/upgrade: installed kerneloops package post-installation script
  subprocess returned error exit status 1

Status in kerneloops package in Ubuntu:
  New

Bug description:
  Kindly check

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: kerneloops 0.12+git20140509-6ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18
  Uname: Linux 4.15.0-140-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Thu Apr  1 17:59:48 2021
  ErrorMessage: installed kerneloops package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-08-11 (964 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  2.0.4
  SourcePackage: kerneloops
  Title: package kerneloops 0.12+git20140509-6ubuntu2 failed to 
install/upgrade: installed kerneloops package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2021-04-01 (0 days ago)

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

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

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

I'm waiting for your update ! That's pretty cool !

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

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

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

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

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

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

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

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 1922387

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 Groovy)
   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/1922387

Title:
  BUG: kernel NULL pointer dereference, address: 0050

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  I observed the following kernel panic with the 5.4.0-71.79-generic
  kernel while running kernel selftests:

  blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28
  [ 1672.118199] mmiotrace: Error taking CPU254 down: -28
  [ 1672.230306] mmiotrace: Error taking CPU255 down: -28
  [ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050
  [ 2503.367527] #PF: supervisor read access in kernel mode
  [ 2503.373257] #PF: error_code(0x) - not-present page
  [ 2503.378989] PGD 0 P4D 0 
  [ 2503.381812] Oops:  [#1] SMP NOPTI
  [ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G   OE 
5.4.0-71-generic #79-Ubuntu
  [ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 
0.33 01/19/2021
  [ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100
  [ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00 00 48 
8d 7d a0 e8 d0 a4 ca ff 49 89 c4 48 85 c0 74 37 49 8b 87 b8 03 00 00 <48> 8b 70 
50 48 85 f6 74 45 49 8d 7c 24 08 ba 20 00 00 00 e8 59 91
  [ 2503.432683] RSP: 0018:a8d6c0003d90 EFLAGS: 00010286
  [ 2503.438513] RAX:  RBX:  RCX: 
8100
  [ 2503.446474] RDX: 9968a228f418 RSI: 0100 RDI: 
9968a228f414
  [ 2503.454436] RBP: a8d6c0003df8 R08: 9968a228f414 R09: 
0100
  [ 2503.462394] R10: 0007 R11: 0007 R12: 
9968a228f418
  [ 2503.470353] R13: fffa R14: 0003 R15: 
9a686f9b3000
  [ 2503.478316] FS:  () GS:99690cc0() 
knlGS:
  [ 2503.487342] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2503.493752] CR2: 0050 CR3: 007e08ad6000 CR4: 
00340ef0
  [ 2503.501712] Call Trace:
  [ 2503.504438]  
  [ 2503.506682]  wb_timer_fn+0x1d6/0x3c0
  [ 2503.510672]  ? blk_stat_free_callback_rcu+0x30/0x30
  [ 2503.516112]  blk_stat_timer_fn+0x134/0x140
  [ 2503.520683]  call_timer_fn+0x32/0x130
  [ 2503.524768]  __run_timers.part.0+0x180/0x280
  [ 2503.529535]  ? trace_event_raw_event_softirq+0x5d/0xa0
  [ 2503.535267]  run_timer_softirq+0x2a/0x50
  [ 2503.539644]  __do_softirq+0xe1/0x2d6
  [ 2503.543629]  irq_exit+0xae/0xb0
  [ 2503.547132]  smp_apic_timer_interrupt+0x7b/0x140
  [ 2503.552280]  apic_timer_interrupt+0xf/0x20
  [ 2503.556848]  
  [ 2503.559187] RIP: 0010:native_safe_halt+0xe/0x10
  [ 2503.564239] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 
2d 66 dd 52 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d 56 dd 52 00 fb f4  90 0f 
1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 cd cd 63 ff 65
  [ 2503.585191] RSP: 0018:94803e18 EFLAGS: 0202 ORIG_RAX: 
ff13
  [ 2503.593635] RAX: 0001e7c0 RBX: 996849080de8 RCX: 
00149022
  [ 2503.601595] RDX: 00149022 RSI:  RDI: 
948c5ba0
  [ 2503.609556] RBP: 94803e38 R08: 02a8 R09: 
9968a228f000
  [ 2503.617516] R10:  R11: 0002 R12: 

  [ 2503.625475] R13:  R14:  R15: 

  [ 2503.633440]  ? default_idle+0x20/0x140
  [ 2503.637623]  arch_cpu_idle+0x15/0x20
  [ 2503.641608]  default_idle_call+0x23/0x30
  [ 2503.645984]  do_idle+0x1fb/0x270
  [ 2503.649583]  cpu_startup_entry+0x20/0x30
  [ 2503.653960]  rest_init+0xae/0xb0
  [ 2503.657563]  arch_call_rest_init+0xe/0x1b
  [ 2503.662025]  start_kernel+0x549/0x56a
  [ 2503.666108]  x86_64_start_reservations+0x24/0x26
  [ 2503.671258]  x86_64_start_kernel+0x75/0x79
  [ 2503.675828]  secondary_startup_64+0xa4/0xb0
  [ 2503.680493] Modules linked in: sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp 
ip6table_nat iptable_nat xt_nat nf_nat algif_hash af_alg ip6table_filter 
xt_conntrack

[Kernel-packages] [Bug 1921966] Re: nvidia-graphics-drivers-390 390.141-0ubuntu0.20.10.1 ADT test failure on groovy and focal

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

** This bug has been marked a duplicate of bug 1922099
   nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with 
linux/5.8.0-49.55

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

Title:
  nvidia-graphics-drivers-390 390.141-0ubuntu0.20.10.1 ADT test failure
  on groovy and focal

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Testing failed on G/linux 5.8.0-49.55:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz

  Testing failed on F/linux 5.4.0-71.79:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/armhf/n/nvidia-graphics-drivers-390/20210330_013823_f2404@/log.gz


  Output on G/linux (note different than F/linux and F/hwe-5.8):


  dpkg: dependency problems prevent removal of dkms:
   nvidia-dkms-390 depends on dkms.

  dpkg: error processing package dkms (--remove):
   dependency problems - not removing
  I: Package nvidia-headless-no-dkms-390 has no dkms.conf, skipping
  Errors were encountered while processing:
   dkms
  autopkgtest [22:24:35]: test dkms-autopkgtest: ---]
  autopkgtest [22:24:37]: test dkms-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -
  dkms-autopkgtest FAIL non-zero exit status 1
  autopkgtest [22:24:40]:  summary
  dkms-autopkgtest FAIL non-zero exit status 1



  
  Output on F/linux, which is similar on F/hwe-5.8:

  
  Setting up nvidia-kernel-source-390 (390.141-0ubuntu0.20.04.1) ...
  Setting up nvidia-dkms-390 (390.141-0ubuntu0.20.04.1) ...
  update-initramfs: deferring update (trigger activated)
  update-initramfs: Generating /boot/initrd.img-4.15.0-135-generic
  W: missing /lib/modules/4.15.0-135-generic
  W: Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.15.0-135-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  cat: 
/var/tmp/mkinitramfs_GqBPlJ/lib/modules/4.15.0-135-generic/modules.builtin: No 
such file or directory
  find: ‘/var/tmp/mkinitramfs_GqBPlJ/lib/modules/4.15.0-135-generic/kernel’: No 
such file or directory
  depmod: WARNING: could not open modules.order at 
/var/tmp/mkinitramfs_GqBPlJ/lib/modules/4.15.0-135-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin at 
/var/tmp/mkinitramfs_GqBPlJ/lib/modules/4.15.0-135-generic: No such file or 
directory
  Loading new nvidia-390.141 DKMS files...
  It is likely that 4.15.0-135-generic belongs to a chroot's host
  Building for 5.4.0-71-generic
  Building for architecture armhf
  Building initial module for 5.4.0-71-generic
  Error! Bad return status for module build on kernel: 5.4.0-71-generic (armhf)
  Consult /var/lib/dkms/nvidia/390.141/build/make.log for more information.
  dpkg: error processing package nvidia-dkms-390 (--configure):
   installed nvidia-dkms-390 package post-installation script subprocess 
returned error exit status 10
  Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
  Processing triggers for initramfs-tools (0.136ubuntu6.4) ...
  update-initramfs: Generating /boot/initrd.img-5.4.0-71-generic
  Errors were encountered while processing:
   nvidia-dkms-390
  autopkgtest [01:38:04]: test dkms-autopkgtest: ---]
  autopkgtest [01:38:06]: test dkms-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -
  dkms-autopkgtest FAIL non-zero exit status 1
  autopkgtest [01:38:09]:  summary
  dkms-autopkgtest FAIL non-zero exit status 1

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

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

[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55

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

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

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

Title:
  nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure
  with linux/5.8.0-49.55

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running nvidia-
  graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether
  this is caused by the tested source or the kernel has, yet, to be
  determined.

  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz

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

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

[Kernel-packages] [Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050

2021-04-02 Thread Francis Ginther

This panic occurred while running the ubuntu_kernel_selftests suite. The
last bit of logs are:

13:33:20 DEBUG| [stdout] # selftests: ftrace: ftracetest
13:33:20 DEBUG| [stdout] # === Ftrace unit tests ===
13:33:28 DEBUG| [stdout] # [1] Basic trace file check [PASS]
13:37:04 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
13:39:48 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
13:39:56 DEBUG| [stdout] # [4] Basic event tracing check [PASS]
13:40:04 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS]
13:40:20 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS]
13:40:35 DEBUG| [stdout] # [7] trace_pipe and trace_marker [PASS]
13:40:51 DEBUG| [stdout] # [8] Generic dynamic event - add/remove kprobe events 
[PASS]
13:41:07 DEBUG| [stdout] # [9] Generic dynamic event - add/remove synthetic 
events [PASS]
13:41:14 DEBUG| [stdout] # [10] Generic dynamic event - selective clear 
(compatibility) [PASS]
13:41:22 DEBUG| [stdout] # [11] Generic dynamic event - generic clear event 
[PASS]
13:41:46 DEBUG| [stdout] # [12] event tracing - enable/disable with event level 
files [PASS]
13:42:17 DEBUG| [stdout] # [13] event tracing - restricts events based on pid 
[PASS]
13:42:41 DEBUG| [stdout] # [14] event tracing - enable/disable with subsystem 
level files [PASS]
13:43:05 DEBUG| [stdout] # [15] event tracing - enable/disable with top level 
files [PASS]
13:43:14 DEBUG| [stdout] # [16] Test trace_printk from module [PASS]
13:43:56 DEBUG| [stdout] # [17] ftrace - function graph filters with stack 
tracer [PASS]
13:44:29 DEBUG| [stdout] # [18] ftrace - function graph filters [PASS]
13:45:49 DEBUG| [stdout] # [19] ftrace - function pid filters [PASS]
13:46:06 DEBUG| [stdout] # [20] ftrace - stacktrace filter command [PASS]
13:46:38 DEBUG| [stdout] # [21] ftrace - function trace with cpumask [PASS]
13:47:13 DEBUG| [stdout] # [22] ftrace - test for function event triggers [PASS]
13:47:21 DEBUG| [stdout] # [23] ftrace - function trace on module [PASS]
13:47:31 DEBUG| [stdout] # [24] ftrace - function profiling [PASS]
13:48:07 DEBUG| [stdout] # [25] ftrace - function profiler with function 
tracing [PASS]
13:48:25 DEBUG| [stdout] # [26] ftrace - test reading of set_ftrace_filter 
[PASS]
 END OF MESSAGES 

This job was run twice. The prior run also hung before completing, but
we don't have a console log for that time period, so it's unclear if it
also panic'd. It's last messages were:

04:44:27 DEBUG| [stdout] # selftests: timers: nsleep-lat
04:44:48 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME [OK]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC [OK]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_RAW [UNSUPPORTED]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_COARSE [UNSUPPORTED]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_COARSE [UNSUPPORTED]
04:45:30 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME [OK]
04:45:52 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_ALARM [OK]
04:46:13 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME_ALARM [OK]
04:46:34 DEBUG| [stdout] # nsleep latency CLOCK_TAI [OK]
04:46:34 DEBUG| [stdout] # # Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
04:46:34 DEBUG| [stdout] ok 3 selftests: timers: nsleep-lat
04:46:34 DEBUG| [stdout] # selftests: timers: set-timer-lat

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

Title:
  BUG: kernel NULL pointer dereference, address: 0050

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

Bug description:
  I observed the following kernel panic with the 5.4.0-71.79-generic
  kernel while running kernel selftests:

  blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28
  [ 1672.118199] mmiotrace: Error taking CPU254 down: -28
  [ 1672.230306] mmiotrace: Error taking CPU255 down: -28
  [ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050
  [ 2503.367527] #PF: supervisor read access in kernel mode
  [ 2503.373257] #PF: error_code(0x) - not-present page
  [ 2503.378989] PGD 0 P4D 0 
  [ 2503.381812] Oops:  [#1] SMP NOPTI
  [ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G   OE 
5.4.0-71-generic #79-Ubuntu
  [ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 
0.33 01/19/2021
  [ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100
  [ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00 00 48 
8d 7d a0 e8 d0 a4 ca ff 49 89 c4 48 85 c0 74 37 49 8b 87 b8 03 00 00 <48> 8b 70 
50 48 85 f6 74 45 49 8d 7c 24 08 ba 20 00 00 00 e8 59 91
  [ 2503.432683] RSP: 0018:a8d6c0003d90 EFLAGS: 00010286
  [ 2503.438513] RAX:  RBX:  RCX: 
8100
  [ 2503.446474] RDX: 9968a228f418 RSI:

[Kernel-packages] [Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050

2021-04-02 Thread Francis Ginther

This panic occurred while running the ubuntu_kernel_selftests suite. The
last bit of logs are:

13:33:20 DEBUG| [stdout] # selftests: ftrace: ftracetest
13:33:20 DEBUG| [stdout] # === Ftrace unit tests ===
13:33:28 DEBUG| [stdout] # [1] Basic trace file check   [PASS]
13:37:04 DEBUG| [stdout] # [2] Basic test for tracers   [PASS]
13:39:48 DEBUG| [stdout] # [3] Basic trace clock test   [PASS]
13:39:56 DEBUG| [stdout] # [4] Basic event tracing check[PASS]
13:40:04 DEBUG| [stdout] # [5] Change the ringbuffer size   [PASS]
13:40:20 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS]
13:40:35 DEBUG| [stdout] # [7] trace_pipe and trace_marker  [PASS]
13:40:51 DEBUG| [stdout] # [8] Generic dynamic event - add/remove kprobe events 
[PASS]
13:41:07 DEBUG| [stdout] # [9] Generic dynamic event - add/remove synthetic 
events  [PASS]
13:41:14 DEBUG| [stdout] # [10] Generic dynamic event - selective clear 
(compatibility) [PASS]
13:41:22 DEBUG| [stdout] # [11] Generic dynamic event - generic clear event 
[PASS]
13:41:46 DEBUG| [stdout] # [12] event tracing - enable/disable with event level 
files   [PASS]
13:42:17 DEBUG| [stdout] # [13] event tracing - restricts events based on pid   
[PASS]
13:42:41 DEBUG| [stdout] # [14] event tracing - enable/disable with subsystem 
level files   [PASS]
13:43:05 DEBUG| [stdout] # [15] event tracing - enable/disable with top level 
files [PASS]
13:43:14 DEBUG| [stdout] # [16] Test trace_printk from module   [PASS]
13:43:56 DEBUG| [stdout] # [17] ftrace - function graph filters with stack 
tracer   [PASS]
13:44:29 DEBUG| [stdout] # [18] ftrace - function graph filters [PASS]
13:45:49 DEBUG| [stdout] # [19] ftrace - function pid filters   [PASS]
13:46:06 DEBUG| [stdout] # [20] ftrace - stacktrace filter command  [PASS]
13:46:38 DEBUG| [stdout] # [21] ftrace - function trace with cpumask[PASS]
13:47:13 DEBUG| [stdout] # [22] ftrace - test for function event triggers   
[PASS]
13:47:21 DEBUG| [stdout] # [23] ftrace - function trace on module   [PASS]
13:47:31 DEBUG| [stdout] # [24] ftrace - function profiling [PASS]
13:48:07 DEBUG| [stdout] # [25] ftrace - function profiler with function 
tracing[PASS]
13:48:25 DEBUG| [stdout] # [26] ftrace - test reading of set_ftrace_filter  
[PASS]
 END OF MESSAGES 

This job was run twice. The prior run also hung before completing, but
we don't have a console log for that time period, so it's unclear if it
also panic'd. It's last messages were:

04:44:27 DEBUG| [stdout] # selftests: timers: nsleep-lat
04:44:48 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME [OK]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC[OK]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_RAW
[UNSUPPORTED]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_COARSE  
[UNSUPPORTED]
04:45:09 DEBUG| [stdout] # nsleep latency CLOCK_MONOTONIC_COARSE 
[UNSUPPORTED]
04:45:30 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME [OK]
04:45:52 DEBUG| [stdout] # nsleep latency CLOCK_REALTIME_ALARM   [OK]
04:46:13 DEBUG| [stdout] # nsleep latency CLOCK_BOOTTIME_ALARM   [OK]
04:46:34 DEBUG| [stdout] # nsleep latency CLOCK_TAI  [OK]
04:46:34 DEBUG| [stdout] # # Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
04:46:34 DEBUG| [stdout] ok 3 selftests: timers: nsleep-lat
04:46:34 DEBUG| [stdout] # selftests: timers: set-timer-lat

The job can be found here:
http://10.246.72.4:8080/view/nvidia%20a100%20-%20blanka/job/focal-linux-
generic-amd64-5.4.0-blanka-ubuntu_kernel_selftests/

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

Title:
  BUG: kernel NULL pointer dereference, address: 0050

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

Bug description:
  I observed the following kernel panic with the 5.4.0-71.79-generic
  kernel while running kernel selftests:

  blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28
  [ 1672.118199] mmiotrace: Error taking CPU254 down: -28
  [ 1672.230306] mmiotrace: Error taking CPU255 down: -28
  [ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050
  [ 2503.367527] #PF: supervisor read access in kernel mode
  [ 2503.373257] #PF: error_code(0x) - not-present page
  [ 2503.378989] PGD 0 P4D 0 
  [ 2503.381812] Oops:  [#1] SMP NOPTI
  [ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G   OE 
5.4.0-71-generic #79-Ubuntu
  [ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 
0.33 01/19/2021
  [ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100
  [ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00

[Kernel-packages] [Bug 1922387] [NEW] BUG: kernel NULL pointer dereference, address: 0000000000000050

2021-04-02 Thread dann frazier

Public bug reported:

I observed the following kernel panic with the 5.4.0-71.79-generic
kernel while running kernel selftests:

blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28
[ 1672.118199] mmiotrace: Error taking CPU254 down: -28
[ 1672.230306] mmiotrace: Error taking CPU255 down: -28
[ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050
[ 2503.367527] #PF: supervisor read access in kernel mode
[ 2503.373257] #PF: error_code(0x) - not-present page
[ 2503.378989] PGD 0 P4D 0 
[ 2503.381812] Oops:  [#1] SMP NOPTI
[ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G   OE 
5.4.0-71-generic #79-Ubuntu
[ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 
0.33 01/19/2021
[ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100
[ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00 00 48 
8d 7d a0 e8 d0 a4 ca ff 49 89 c4 48 85 c0 74 37 49 8b 87 b8 03 00 00 <48> 8b 70 
50 48 85 f6 74 45 49 8d 7c 24 08 ba 20 00 00 00 e8 59 91
[ 2503.432683] RSP: 0018:a8d6c0003d90 EFLAGS: 00010286
[ 2503.438513] RAX:  RBX:  RCX: 8100
[ 2503.446474] RDX: 9968a228f418 RSI: 0100 RDI: 9968a228f414
[ 2503.454436] RBP: a8d6c0003df8 R08: 9968a228f414 R09: 0100
[ 2503.462394] R10: 0007 R11: 0007 R12: 9968a228f418
[ 2503.470353] R13: fffa R14: 0003 R15: 9a686f9b3000
[ 2503.478316] FS:  () GS:99690cc0() 
knlGS:
[ 2503.487342] CS:  0010 DS:  ES:  CR0: 80050033
[ 2503.493752] CR2: 0050 CR3: 007e08ad6000 CR4: 00340ef0
[ 2503.501712] Call Trace:
[ 2503.504438]  
[ 2503.506682]  wb_timer_fn+0x1d6/0x3c0
[ 2503.510672]  ? blk_stat_free_callback_rcu+0x30/0x30
[ 2503.516112]  blk_stat_timer_fn+0x134/0x140
[ 2503.520683]  call_timer_fn+0x32/0x130
[ 2503.524768]  __run_timers.part.0+0x180/0x280
[ 2503.529535]  ? trace_event_raw_event_softirq+0x5d/0xa0
[ 2503.535267]  run_timer_softirq+0x2a/0x50
[ 2503.539644]  __do_softirq+0xe1/0x2d6
[ 2503.543629]  irq_exit+0xae/0xb0
[ 2503.547132]  smp_apic_timer_interrupt+0x7b/0x140
[ 2503.552280]  apic_timer_interrupt+0xf/0x20
[ 2503.556848]  
[ 2503.559187] RIP: 0010:native_safe_halt+0xe/0x10
[ 2503.564239] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 
2d 66 dd 52 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d 56 dd 52 00 fb f4  90 0f 
1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 cd cd 63 ff 65
[ 2503.585191] RSP: 0018:94803e18 EFLAGS: 0202 ORIG_RAX: 
ff13
[ 2503.593635] RAX: 0001e7c0 RBX: 996849080de8 RCX: 00149022
[ 2503.601595] RDX: 00149022 RSI:  RDI: 948c5ba0
[ 2503.609556] RBP: 94803e38 R08: 02a8 R09: 9968a228f000
[ 2503.617516] R10:  R11: 0002 R12: 
[ 2503.625475] R13:  R14:  R15: 
[ 2503.633440]  ? default_idle+0x20/0x140
[ 2503.637623]  arch_cpu_idle+0x15/0x20
[ 2503.641608]  default_idle_call+0x23/0x30
[ 2503.645984]  do_idle+0x1fb/0x270
[ 2503.649583]  cpu_startup_entry+0x20/0x30
[ 2503.653960]  rest_init+0xae/0xb0
[ 2503.657563]  arch_call_rest_init+0xe/0x1b
[ 2503.662025]  start_kernel+0x549/0x56a
[ 2503.666108]  x86_64_start_reservations+0x24/0x26
[ 2503.671258]  x86_64_start_kernel+0x75/0x79
[ 2503.675828]  secondary_startup_64+0xa4/0xb0
[ 2503.680493] Modules linked in: sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp 
ip6table_nat iptable_nat xt_nat nf_nat algif_hash af_alg ip6table_filter 
xt_conntrack nf_conntrack nf_defrag_ipv4 ip6_tables nf_defrag_ipv6 ip_vti 
ip6_vti fou6 sit ipip tunnel4 geneve act_mirred cls_basic esp6 authenc echainiv 
iptable_filter xt_policy bpfilter veth esp4_offload esp4 xfrm_user xfrm_algo 
macsec fou vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc 
ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy 
binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
amd64_edac_mod edac_mce_amd kvm_amd kvm ipmi_ssif input_leds cdc_ether usbnet 
mii ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel 
knem(OE) 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 multipath linear ses enclosure ast crct10dif_pclmul 
drm_vram_helper crc32_pclmul ttm
[ 2503.680569]  ghash_clmulni_intel aesni_intel mlx5_core(OE) crypto_simd 
pci_hyperv_intf drm_kms_helper tls syscopyarea cryptd raid0 glue_helper 
mlxfw(OE) hid_generic sysfillrect igb sysimgblt mpt3sas uas dca mdev(OE) 
fb_sys_fops raid_class i2c_algo_bit usbhid nvme scsi_transport_sas hid 
usb_storage drm mlx_compat(OE) nvme_core i2c_piix4 [last unloaded: trace_printk]
[ 2503.813546] CR2: 0050
[ 2503.817337] ---[

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

Cool ^^ It s working also for UX433 users.

Yes it s the normal behavior of Left Shift+Enter. (it goes up)
I will update the program to not use LeftShift for enter key.
Meanwhile, you can cancel this effect hitting leftshift again.

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

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

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

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

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

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

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

Just another problem I just find : in Excel, when I press enter, instead
of going to the next cell at the bottom, it goes up. Any idea ?

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

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

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

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

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

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

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

Oh Yeah! It worked like a charm !

Now the ASUS M433IA has a working numpad on Linux !

You're amazing Mohamed ! Many many thanks !

Now I wonder how to share my program with other people...

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

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

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

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

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

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

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

@magellan-2000 If you share your code, it would be easier to help you.
I tried with EV_KEY.KEY_APOSTROPHE and it prints the expected "%" symbol

Weird that it s not working for you.

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

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

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

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

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

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

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

Well here is the last KEY_CODE list :

https://elixir.bootlin.com/linux/latest/source/include/uapi/linux/input-
event-codes.h

But I didn't find the code to display the "%" symbol.

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

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

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

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

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

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

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

the key code you search for % is EV_KEY.KEY_APOSTROPHE

probably you forgot to enable it on the device, add the line
dev.enable(EV_KEY.KEY_APOSTROPHE)

hope this helps

Mohamed

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

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

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

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

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

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

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

Well I made a mistake. Equal is now working.
I just need to find the "%" symbol and it will be done !

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

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

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

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

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

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

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

where can i find the full official list of the key codes ?

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

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

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

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

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

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

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

Well... KPDOT instead of KPCOMMA does the same thing, it display "," instead of 
"."
I would like to replace the coma by the dot to avoid having to use shift + "," 
on my french keyboard to display a dot.

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

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

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

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

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

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

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

Many thanks for the list, but I think the game is not over yet !
EQUAL does not work and I get a "+" instead.
Anyway, I'm going to try to replace "," by dot since your list help me.
Many thanks Mohamed, but I still need to find the right codes for "%" and "=".

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

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

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

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

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

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

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

You can find the a of event codes:
https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h

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

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

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

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

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

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

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

and for percentage (%) try with EV_KEY.KEY_APOSTROPHE

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

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

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

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

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

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

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

or with KEY_KPEQUAL

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

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

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

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

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

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

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

for equal, test with EV_KEY.KEY_EQUAL

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

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

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

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

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

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

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

YES ! And I didn't succeed in finding the EV_KEY.KEY_ value for "%" and "=".
Can you help me please ?

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

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

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

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

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

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

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

@magellan Good news ^^
Depending on the laptop model, the touchpad keys area are a little different. 
For example on UX433 we have not  (%) key and the comma (.) key is not exactly 
at the same place.

Probably we would have to make different programs for each kind of
models

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

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

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

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

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

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

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

OK ! Here we are !
I found how to adapt the program for my laptop ! But now I have to deal with 
some keys that don't display the right character  I'm working on it and 
when it will be done I will share the adapted program !

Many thanks to all this community, you are the best !

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

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

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

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

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

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

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

2021-04-02 Thread ANDREA MATTANA

** Bug watch added: github.com/Evidlo/remarkable_mouse/issues #38
   https://github.com/Evidlo/remarkable_mouse/issues/38

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

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

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

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

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

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

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

2021-04-02 Thread ANDREA MATTANA

Synopsys DesignWare I2C adapter I2C adapter is the mine as well,

lsmod | grep i2c_dev
do not report anything...

I have libevdev (0.9) on my python3.6 installation

$ python3 ux433_touchpad_numpad.py
Traceback (most recent call last):
  File "ux433_touchpad_numpad.py", line 1, in 
from libevdev import Device, InputEvent, EV_ABS, EV_KEY, EV_LED, EV_SYN
  File "/usr/local/lib/python3.6/dist-packages/libevdev/__init__.py", line
23, in 
from .device import Device, InputAbsInfo
  File "/usr/local/lib/python3.6/dist-packages/libevdev/device.py", line
29, in 
from .event import InputEvent
  File "/usr/local/lib/python3.6/dist-packages/libevdev/event.py", line 23,
in 
from .const import EventType, EventCode
  File "/usr/local/lib/python3.6/dist-packages/libevdev/const.py", line
413, in 
_load_consts()
  File "/usr/local/lib/python3.6/dist-packages/libevdev/const.py", line
338, in _load_consts
Libevdev()  # classmethods, need to make sure it's loaded at once
  File "/usr/local/lib/python3.6/dist-packages/libevdev/_clib.py", line
395, in __init__
super(Libevdev, self).__init__()
  File "/usr/local/lib/python3.6/dist-packages/libevdev/_clib.py", line 76,
in __init__
self._load()
  File "/usr/local/lib/python3.6/dist-packages/libevdev/_clib.py", line 85,
in _load
func = getattr(cls._lib, name)
  File "/usr/lib/python3.6/ctypes/__init__.py", line 361, in __getattr__
func = self.__getitem__(name)
  File "/usr/lib/python3.6/ctypes/__init__.py", line 366, in __getitem__
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/lib/x86_64-linux-gnu/libevdev.so.2: undefined symbol:
libevdev_event_value_get_name


This is telling that  libevdev_event_value_get_name method is available
only on version 1.6.0:
https://github.com/Evidlo/remarkable_mouse/issues/38

but my pip3 cannot find that version.

Thanks,
cheers,
Andrea

Il giorno ven 2 apr 2021 alle ore 18:05 magellan <1810...@bugs.launchpad.net>
ha scritto:

> After looking to the program, it search "ELAN", "Mouse" or "AT
> Translated Set 2 keyboard" to set the detected numpad value to 1 But
> mine is like this :
>
> Synopsys DesignWare I2C adapter I2C adapter
>
> I'm going to update the program so that it detect mine. But I think the
> best solution is to bypass the detection of the numpad since people
> using the program should have on on their computer.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1823320).
> https://bugs.launchpad.net/bugs/1810183
>
> Title:
>   numpad on touchpad doesn't work in ASUS Zenbook 14
>
> Status in Linux:
>   New
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10
> alongside windows 10.
>   The numeric keypads are within the touchpad and are supposed to be
> turned on by a button on the touchpad. This works well in Windows but
> doesn't work in Ubuntu.
>   I have tried to search for any related problems/solutions online but I
> haven't been able to.
>   I will appreciate any suggestion or help.
>   Thanks,
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.10-0ubuntu13.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.10
>   InstallationDate: Installed on 2018-12-30 (4 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Package: linux (not installed)
>   Tags:  cosmic
>   Uname: Linux 4.19.11-041911-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.10-0ubuntu13.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.10
>   InstallationDate: Installed on 2018-12-30 (4 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Package: linux (not installed)
>   Tags:  cosmic
>   Uname: Linux 4.18.10-041810-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions
>


-- 

--

Andrea Mattana

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

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

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are

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

After looking to the program, it search "ELAN", "Mouse" or "AT
Translated Set 2 keyboard" to set the detected numpad value to 1 But
mine is like this :

Synopsys DesignWare I2C adapter I2C adapter

I'm going to update the program so that it detect mine. But I think the
best solution is to bypass the detection of the numpad since people
using the program should have on on their computer.

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

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

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

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

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

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

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

Same thing for me :

Can't find touchpad, code 0

I have an Asus M433IA and I have change the I2C address according to
mine :

ON:i2ctransfer -f -y 0 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00
0x0d 0x14 0x03 0x01 0xad

OFF:i2ctransfer -f -y 0 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00
0x0d 0x14 0x03 0x00 0xad

But nothing is working. F8 don't illuminate the numpad.

Hope someone will help.

Many thanks to Mohamed for sharing is work.

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

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

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

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

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

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

[Kernel-packages] [Bug 1915717] Re: Ubuntu 21.04, kernel feature request, TLS device offload for Bond

2021-04-02 Thread Jeff Lane

** Description changed:

  The request here is to pull needed patches to support tls rx/tx offload
  for bond interfaces.
  
  patch set:
  4e5a73329051 net/tls: Except bond interface from some TLS checks
  153cbd137f0a net/tls: Device offload to use lowest netdevice in chain
  dc5809f9e2b6 net/bonding: Declare TLS RX device offload support
  89df6a810470 net/bonding: Implement TLS TX device offload
  f45583de361d net/bonding: Take update_features call out of XFRM funciton
  007feb87fb15 net/bonding: Implement ndo_sk_get_lower_dev
  5b99854540e3 net/bonding: Take IP hash logic into a helper
  719a402cf603 net: netdevice: Add operation ndo_sk_get_lower_dev
  
+ Pathches upstream in mainline at 5.12-rc1
+ 
+ 
  https://www.spinics.net/lists/netdev/msg714607.html
  https://www.spinics.net/lists/netdev/msg714991.html
  
  *
- the set was originally applied to net/net-next 
+ the set was originally applied to net/net-next
  (hashes above are from net-next tree cloned from 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git)
  
  *
  The set is cleanly applied on ubuntu-unstable branch
  (cloned from 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable)
  
  *
- the set is accepted to upstream v5.12 and thus not natively in 21.04 
- 
+ the set is accepted to upstream v5.12 and thus not natively in 21.04
  
  thanks,
  Amir

** Description changed:

  The request here is to pull needed patches to support tls rx/tx offload
  for bond interfaces.
  
  patch set:
  4e5a73329051 net/tls: Except bond interface from some TLS checks
  153cbd137f0a net/tls: Device offload to use lowest netdevice in chain
  dc5809f9e2b6 net/bonding: Declare TLS RX device offload support
  89df6a810470 net/bonding: Implement TLS TX device offload
  f45583de361d net/bonding: Take update_features call out of XFRM funciton
  007feb87fb15 net/bonding: Implement ndo_sk_get_lower_dev
  5b99854540e3 net/bonding: Take IP hash logic into a helper
  719a402cf603 net: netdevice: Add operation ndo_sk_get_lower_dev
  
  Pathches upstream in mainline at 5.12-rc1
  
+ All patches pick cleanly from mainline into our 5.11 Hirsute tree
  
  https://www.spinics.net/lists/netdev/msg714607.html
  https://www.spinics.net/lists/netdev/msg714991.html
  
  *
  the set was originally applied to net/net-next
  (hashes above are from net-next tree cloned from 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git)
  
  *
  The set is cleanly applied on ubuntu-unstable branch
  (cloned from 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable)
  
  *
  the set is accepted to upstream v5.12 and thus not natively in 21.04
  
  thanks,
  Amir

** Description changed:

  The request here is to pull needed patches to support tls rx/tx offload
  for bond interfaces.
  
  patch set:
  4e5a73329051 net/tls: Except bond interface from some TLS checks
  153cbd137f0a net/tls: Device offload to use lowest netdevice in chain
  dc5809f9e2b6 net/bonding: Declare TLS RX device offload support
  89df6a810470 net/bonding: Implement TLS TX device offload
  f45583de361d net/bonding: Take update_features call out of XFRM funciton
  007feb87fb15 net/bonding: Implement ndo_sk_get_lower_dev
  5b99854540e3 net/bonding: Take IP hash logic into a helper
  719a402cf603 net: netdevice: Add operation ndo_sk_get_lower_dev
- 
- Pathches upstream in mainline at 5.12-rc1
- 
- All patches pick cleanly from mainline into our 5.11 Hirsute tree
  
  https://www.spinics.net/lists/netdev/msg714607.html
  https://www.spinics.net/lists/netdev/msg714991.html
  
  *
  the set was originally applied to net/net-next
  (hashes above are from net-next tree cloned from 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git)
  
  *
  The set is cleanly applied on ubuntu-unstable branch
  (cloned from 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable)
  
  *
  the set is accepted to upstream v5.12 and thus not natively in 21.04
  
- thanks,
- Amir
+ UPDATE
+ Pathches identified upstream in mainline at 5.12-rc1
+ 
+ All patches pick cleanly from mainline into our 5.11 Hirsute tree

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

Title:
  Ubuntu 21.04, kernel feature request, TLS device offload for Bond

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

Bug description:
  The request here is to pull needed patches to support tls rx/tx
  offload for bond interfaces.

  patch set:
  4e5a73329051 net/tls: Except bond interface from some TLS checks
  153cbd137f0a net/tls: Device offload to use lowest netdevice in chain
  dc5809f9e2b6 net/bonding: Declare TLS RX device offload support
  89df6a810470 net/bonding: Implement TLS TX device offload
  f45583de361d net/bonding: Take update_features call out of XFRM funciton
  007feb87fb15 net/bonding:

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

Do you have module i2c_dev enabled ? 
lsmod | grep i2c_dev

You should try to launch the command manually and see if you have any debug logs
/usr/bin/python3 /usr/bin/ux433_touchpad_numpad.py

Hope this helps.

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

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

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

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

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

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

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

2021-04-02 Thread ANDREA MATTANA

I have the same laptop, I have changed the i2c address in the python code
according to my i2c address where the on/off command works but the service
installed after the reboot doesn't work.
What's wrong?
When my laptop (Ubuntu 18.04) starts has the function key enabled (the blue
led is on), I also tried to turn off (fnct+esc) and pressed F8 but nothing
changed.
Same result disconnecting the second HDMI monitor.
Cheers,
Andrea

Il giorno ven 2 apr 2021 alle ore 15:40 Badaoui Mohamed <
1810...@bugs.launchpad.net> ha scritto:

> I just adapted the solution offered on Reddit
> (
> https://www.reddit.com/r/linuxhardware/comments/f2vdad/a_service_handling_touchpad_numpad_switching_for/
> )
>
> for my Asus UX433 laptop and it works fine.
>
> Source code:
> https://github.com/mohamed-badaoui/ux433-touchpad-numpad
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1823320).
> https://bugs.launchpad.net/bugs/1810183
>
> Title:
>   numpad on touchpad doesn't work in ASUS Zenbook 14
>
> Status in Linux:
>   New
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10
> alongside windows 10.
>   The numeric keypads are within the touchpad and are supposed to be
> turned on by a button on the touchpad. This works well in Windows but
> doesn't work in Ubuntu.
>   I have tried to search for any related problems/solutions online but I
> haven't been able to.
>   I will appreciate any suggestion or help.
>   Thanks,
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.10-0ubuntu13.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.10
>   InstallationDate: Installed on 2018-12-30 (4 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Package: linux (not installed)
>   Tags:  cosmic
>   Uname: Linux 4.19.11-041911-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.10-0ubuntu13.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.10
>   InstallationDate: Installed on 2018-12-30 (4 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   Package: linux (not installed)
>   Tags:  cosmic
>   Uname: Linux 4.18.10-041810-generic x86_64
>   UnreportableReason: The running kernel is not an Ubuntu kernel
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions
>


-- 

--

Andrea Mattana

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

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

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

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

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

-- 
Mailing list:

[Kernel-packages] [Bug 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71

2021-04-02 Thread Tim Gardner

Patches submitted:

https://lists.ubuntu.com/archives/kernel-team/2021-April/118727.html
https://lists.ubuntu.com/archives/kernel-team/2021-April/118765.html

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

Title:
  Security-Fix Xen XSA 371 for Kernel 5.4.0-71

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [SRU Justification]

  See [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html). commit
  871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error
  handling in xen_blkbk_map()") introduced a security vulnerability.

  Original Commit:
  871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error handling in 
xen_blkbk_map()")

  New commit with security fix:
  a846738f8c3788d846ed1f587270d2f2e3d32432 ("xen-blkback: don't leak persistent 
grants from xen_blkbk_map()")

  [Test Plan]
  none

  [Where problems could occur]
  Unknown

  [Other Info]
  - http://xenbits.xen.org/xsa/advisory-371.html
  - http://xenbits.xen.org/xsa/xsa371-linux.patch
  - http://xenbits.xen.org/xsa/advisory-365.html
  - http://xenbits.xen.org/xsa/xsa365-linux.patch

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

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

[Kernel-packages] [Bug 1922372] Re: i915 doesn't support some high pixel clock 4k * 60Hz monitors

2021-04-02 Thread jeremyszu

** Changed in: oem-priority
   Status: In Progress => Triaged

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

Title:
  i915 doesn't support some high pixel clock 4k * 60Hz monitors

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Some 4K monitors can not display as maximum resolution from i915
  graphic.

   * In some 4k monitors, it's support higher pixel clock

  The following is the case I have:

  Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168
   +hsync -vsync

  Which will be dropped because the mode rate is greater than i915 maximum data 
rate.
  kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline "3840x2160": 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0x9
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH

  The BDB version of Intel vBIOS is 237
  kernel: i915 :00:02.0: [drm:intel_bios_init [i915]] VBT signature "$VBT 
TIGERLAKE  ", BDB version 237

  In old i915 parsing rule (for greater than v216), the common rate is decoded 
as 16200
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000

  Since the Intel updated the parsing rule (for greater then 230). the common 
rate is up to 54
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000, 27,
   54

  There are 4 lanes support.
  i915 :00:02.0: [drm:intel_dp_link_train_phy [i915]] [CONNECTOR:184:DP-2] 
Link
  Training passed at link rate = 162000, lane count = 4, at DPRX

  In this monitor, the max rate (max_link_clock * max_lanes) is:
  162000 * 4 = 648000  # if using old parsing rule (> 210)
  54 * 4 = 216 # if using updated parsing rule (> 230)

  the maximum mode rate is
  DIV_ROUND_UP(pixel_clock * bpp, 8);

  the bpp here is minimum bpp, which is 6 * 3 = 18
  ...
   max bpc: 12
    range: (6, 12)
  ...
  thus:
  533250 * 18 + 8 - 1 / 8 = 1199813 # this is maximum mode rate of this monitor.

  [Fix]

   * It needs to use the updated parsing table (intel BDB table version
  > 230) for supporting high pixel clock monitors.

  [Test Plan]

   * Steps to reproduce
    1. Connect a high pixel clock monitor (533KHz in my case) to i915 graphic 
which vbios version is v237 (In my case:
   ModelName "U2879G6"
   VendorName "AOC"

    2. Check the display setting, expect a 3840*2160*60Hz option but
  there is not 3840*2160*60Hz option.

   * if upgrade drm debugging level then you will see the modeline be dropped 
because of high clock.
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH

   * after applying the change, the resolution work good.

  [Where problems could occur]

   * This change considered the backward compatibility, which will check
  the BDB version before applying different parsing rule.

   * From software perspective, the monitor will show nothing if Intel
  vBIOS using BDB > 230 with undefined dp_max_link_rate field.

   * Otherwise, it looks quite ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1922372/+subscriptions

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

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

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 1922372

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

Title:
  i915 doesn't support some high pixel clock 4k * 60Hz monitors

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Some 4K monitors can not display as maximum resolution from i915
  graphic.

   * In some 4k monitors, it's support higher pixel clock

  The following is the case I have:

  Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168
   +hsync -vsync

  Which will be dropped because the mode rate is greater than i915 maximum data 
rate.
  kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline "3840x2160": 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0x9
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH

  The BDB version of Intel vBIOS is 237
  kernel: i915 :00:02.0: [drm:intel_bios_init [i915]] VBT signature "$VBT 
TIGERLAKE  ", BDB version 237

  In old i915 parsing rule (for greater than v216), the common rate is decoded 
as 16200
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000

  Since the Intel updated the parsing rule (for greater then 230). the common 
rate is up to 54
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000, 27,
   54

  There are 4 lanes support.
  i915 :00:02.0: [drm:intel_dp_link_train_phy [i915]] [CONNECTOR:184:DP-2] 
Link
  Training passed at link rate = 162000, lane count = 4, at DPRX

  In this monitor, the max rate (max_link_clock * max_lanes) is:
  162000 * 4 = 648000  # if using old parsing rule (> 210)
  54 * 4 = 216 # if using updated parsing rule (> 230)

  the maximum mode rate is
  DIV_ROUND_UP(pixel_clock * bpp, 8);

  the bpp here is minimum bpp, which is 6 * 3 = 18
  ...
   max bpc: 12
    range: (6, 12)
  ...
  thus:
  533250 * 18 + 8 - 1 / 8 = 1199813 # this is maximum mode rate of this monitor.

  [Fix]

   * It needs to use the updated parsing table (intel BDB table version
  > 230) for supporting high pixel clock monitors.

  [Test Plan]

   * Steps to reproduce
    1. Connect a high pixel clock monitor (533KHz in my case) to i915 graphic 
which vbios version is v237 (In my case:
   ModelName "U2879G6"
   VendorName "AOC"

    2. Check the display setting, expect a 3840*2160*60Hz option but
  there is not 3840*2160*60Hz option.

   * if upgrade drm debugging level then you will see the modeline be dropped 
because of high clock.
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH

   * after applying the change, the resolution work good.

  [Where problems could occur]

   * This change considered the backward compatibility, which will check
  the BDB version before applying different parsing rule.

   * From software perspective, the monitor will show nothing if Intel
  vBIOS using BDB > 230 with undefined dp_max_link_rate field.

   * Otherwise, it looks quite ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1922372/+subscriptions

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

[Kernel-packages] [Bug 1922372] Re: i915 doesn't support some high pixel clock 4k * 60Hz monitors

2021-04-02 Thread jeremyszu

** Description changed:

  [Impact]
  
-  * Some 4K monitors can not display as maximum resolution from i915
+  * Some 4K monitors can not display as maximum resolution from i915
  graphic.
  
-  * In some 4k monitors, it's support higher pixel clock
+  * In some 4k monitors, it's support higher pixel clock
  
  The following is the case I have:
  
  Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 
  +hsync -vsync
  
  Which will be dropped because the mode rate is greater than i915 maximum data 
rate.
  kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline "3840x2160": 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0x9
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH
  
  The BDB version of Intel vBIOS is 237
  kernel: i915 :00:02.0: [drm:intel_bios_init [i915]] VBT signature "$VBT 
TIGERLAKE  ", BDB version 237
  
  In old i915 parsing rule (for greater than v216), the common rate is decoded 
as 16200
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000
  
  Since the Intel updated the parsing rule (for greater then 230). the common 
rate is up to 54
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000, 27,
-  54
+  54
  
  There are 4 lanes support.
- i915 :00:02.0: [drm:intel_dp_link_train_phy [i915]] [CONNECTOR:184:DP-2] 
Link 
+ i915 :00:02.0: [drm:intel_dp_link_train_phy [i915]] [CONNECTOR:184:DP-2] 
Link
  Training passed at link rate = 162000, lane count = 4, at DPRX
  
  In this monitor, the max rate (max_link_clock * max_lanes) is:
  162000 * 4 = 648000  # if using old parsing rule (> 210)
- 54 * 4 = 216 # if using updated parsing rule (> 230) 
+ 54 * 4 = 216 # if using updated parsing rule (> 230)
  
  the maximum mode rate is
  DIV_ROUND_UP(pixel_clock * bpp, 8);
  
  the bpp here is minimum bpp, which is 6 * 3 = 18
  ...
-   max bpc: 12 
-   range: (6, 12)
+  max bpc: 12
+   range: (6, 12)
  ...
  thus:
  533250 * 18 + 8 - 1 / 8 = 1199813 # this is maximum mode rate of this monitor.
  
- Therefore, we need to use the updated parsing table (intel BDB table
- version > 230) for supporting high pixel clock monitors.
- 
+ [Fix]
+ It needs to use the updated parsing table (intel BDB table version > 230) for 
supporting high pixel clock monitors.
  
  [Test Plan]
  
-  * Steps to reproduce
-   1. Connect a high pixel clock monitor (533KHz in my case) to i915 graphic 
which vbios version is v237 (In my case:
-   ModelName "U2879G6"
-   VendorName "AOC"
+  * Steps to reproduce
+   1. Connect a high pixel clock monitor (533KHz in my case) to i915 graphic 
which vbios version is v237 (In my case:
+  ModelName "U2879G6"
+  VendorName "AOC"
  
-   2. Check the display setting, expect a 3840*2160*60Hz option but there
+   2. Check the display setting, expect a 3840*2160*60Hz option but there
  is not 3840*2160*60Hz option.
  
-  * if upgrade drm debugging level then you will see the modeline be dropped 
because of high clock.
+  * if upgrade drm debugging level then you will see the modeline be dropped 
because of high clock.
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH
  
-  * after applying the change, the resolution work good.
+  * after applying the change, the resolution work good.
  
  [Where problems could occur]
  
-  * This change considered the backward compatibility, which will check
+  * This change considered the backward compatibility, which will check
  the BDB version before applying different parsing rule.
  
-  * From software perspective, the monitor will show nothing if Intel
+  * From software perspective, the monitor will show nothing if Intel
  vBIOS using BDB > 230 with undefined dp_max_link_rate field.
  
-  * Otherwise, it looks quite ok.
+  * Otherwise, it looks quite ok.

** Description changed:

  [Impact]
  
   * Some 4K monitors can not display as maximum resolution from i915
  graphic.
  
   * In some 4k monitors, it's support higher pixel clock
  
  The following is the case I have:
  
  Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 
  +hsync -vsync
  
  Which will be dropped because the mode rate is greater than i915 maximum data 
rate.
  kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline "3840x2160": 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0x9
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH
  
  The BDB version of Intel vBIOS is 237
  kernel: i915 :00:02.0: [drm:intel_bios_init [i915]] VBT signature "$VBT 
TIGERLAKE  ", BDB version 237
  
  In old i915 parsing rule (for greater than v216), the common rate is decoded 
as 16200
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000
  
  Since the Intel updated the parsing rule (for greater then 230). the common 
rate is up to 54
  kernel: i915 :00:02.0:

[Kernel-packages] [Bug 1922372] [NEW] i915 doesn't support some high pixel clock 4k * 60Hz monitors

2021-04-02 Thread jeremyszu

Public bug reported:

[Impact]

 * Some 4K monitors can not display as maximum resolution from i915
graphic.

 * In some 4k monitors, it's support higher pixel clock

The following is the case I have:

Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 
+hsync -vsync

Which will be dropped because the mode rate is greater than i915 maximum data 
rate.
kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline "3840x2160": 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0x9
kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

The BDB version of Intel vBIOS is 237
kernel: i915 :00:02.0: [drm:intel_bios_init [i915]] VBT signature "$VBT 
TIGERLAKE  ", BDB version 237

In old i915 parsing rule (for greater than v216), the common rate is decoded as 
16200
kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000

Since the Intel updated the parsing rule (for greater then 230). the common 
rate is up to 54
kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000, 27,
 54

There are 4 lanes support.
i915 :00:02.0: [drm:intel_dp_link_train_phy [i915]] [CONNECTOR:184:DP-2] 
Link
Training passed at link rate = 162000, lane count = 4, at DPRX

In this monitor, the max rate (max_link_clock * max_lanes) is:
162000 * 4 = 648000  # if using old parsing rule (> 210)
54 * 4 = 216 # if using updated parsing rule (> 230)

the maximum mode rate is
DIV_ROUND_UP(pixel_clock * bpp, 8);

the bpp here is minimum bpp, which is 6 * 3 = 18
...
 max bpc: 12
  range: (6, 12)
...
thus:
533250 * 18 + 8 - 1 / 8 = 1199813 # this is maximum mode rate of this monitor.

[Fix]
It needs to use the updated parsing table (intel BDB table version > 230) for 
supporting high pixel clock monitors.

[Test Plan]

 * Steps to reproduce
  1. Connect a high pixel clock monitor (533KHz in my case) to i915 graphic 
which vbios version is v237 (In my case:
 ModelName "U2879G6"
 VendorName "AOC"

  2. Check the display setting, expect a 3840*2160*60Hz option but there
is not 3840*2160*60Hz option.

 * if upgrade drm debugging level then you will see the modeline be dropped 
because of high clock.
kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

 * after applying the change, the resolution work good.

[Where problems could occur]

 * This change considered the backward compatibility, which will check
the BDB version before applying different parsing rule.

 * From software perspective, the monitor will show nothing if Intel
vBIOS using BDB > 230 with undefined dp_max_link_rate field.

 * Otherwise, it looks quite ok.

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: In Progress

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: jeremyszu (os369510)
 Status: New


** Tags: oem-priority originate-from-1920881 stella

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => jeremyszu (os369510)

** Tags added: oem-priority originate-from-1920881 stella

** Summary changed:

- i915 doesn't support 4k * 60Hz monitor
+ i915 doesn't support some high pixel clock 4k * 60Hz monitors

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
   Importance: High => Critical

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

Title:
  i915 doesn't support some high pixel clock 4k * 60Hz monitors

Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

   * Some 4K monitors can not display as maximum resolution from i915
  graphic.

   * In some 4k monitors, it's support higher pixel clock

  The following is the case I have:

  Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168
   +hsync -vsync

  Which will be dropped because the mode rate is greater than i915 maximum data 
rate.
  kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline "3840x2160": 60 
533250 3840 3888 3920 4000 2160 2163 2168  0x48 0x9
  kernel: [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: 
CLOCK_HIGH

  The BDB version of Intel vBIOS is 237
  kernel: i915 :00:02.0: [drm:intel_bios_init [i915]] VBT signature "$VBT 
TIGERLAKE  ", BDB version 237

  In old i915 parsing rule (for greater than v216), the common rate is decoded 
as 16200
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000

  Since the Intel updated the parsing rule (for greater then 230). the common 
rate is up to 54
  kernel: i915 :00:02.0: [drm:intel_dp_print_rates [i915]] common rates: 
162000, 27,
   54

  There are 4 lanes support.
  i915

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

I just adapted the solution offered on Reddit
(https://www.reddit.com/r/linuxhardware/comments/f2vdad/a_service_handling_touchpad_numpad_switching_for/)

for my Asus UX433 laptop and it works fine.

Source code:
https://github.com/mohamed-badaoui/ux433-touchpad-numpad

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

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

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

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

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

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

[Kernel-packages] [Bug 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71

2021-04-02 Thread Tim Gardner

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

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

Title:
  Security-Fix Xen XSA 371 for Kernel 5.4.0-71

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [SRU Justification]

  See [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html). commit
  871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error
  handling in xen_blkbk_map()") introduced a security vulnerability.

  Original Commit:
  871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error handling in 
xen_blkbk_map()")

  New commit with security fix:
  a846738f8c3788d846ed1f587270d2f2e3d32432 ("xen-blkback: don't leak persistent 
grants from xen_blkbk_map()")

  [Test Plan]
  none

  [Where problems could occur]
  Unknown

  [Other Info]
  - http://xenbits.xen.org/xsa/advisory-371.html
  - http://xenbits.xen.org/xsa/xsa371-linux.patch
  - http://xenbits.xen.org/xsa/advisory-365.html
  - http://xenbits.xen.org/xsa/xsa365-linux.patch

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

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

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

This change was made by a bot.

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

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

Title:
  My touchpad stopped working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm filing this bug report because my touchpad recently stopped
  working at all.

  I executed this at at a terminal :  cat /proc/bus/input/devices
  but there was no touchpad in the list. 

  I read this page (https://wiki.ubuntu.com/DebuggingTouchpadDetection)
  and found out it must be a bug related to the kernel.

  I'm attaching the result of the cat /proc/bus/input/devices command.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-70-generic 5.4.0-70.78
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florence   1302 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Fri Apr  2 13:51:27 2021
  InstallationDate: Installed on 2021-02-09 (51 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook Flip 14_ASUS Flip TP412UA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash i8042.nomux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-70-generic N/A
   linux-backports-modules-5.4.0-70-generic  N/A
   linux-firmware1.187.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP412UA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP412UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412UA.303:bd07/27/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14_ASUSFlipTP412UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook Flip 14_ASUS Flip TP412UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1922354] [NEW] My touchpad stopped working

2021-04-02 Thread Florence Costa

Public bug reported:

I'm filing this bug report because my touchpad recently stopped working
at all.

I executed this at at a terminal :  cat /proc/bus/input/devices
but there was no touchpad in the list. 

I read this page (https://wiki.ubuntu.com/DebuggingTouchpadDetection)
and found out it must be a bug related to the kernel.

I'm attaching the result of the cat /proc/bus/input/devices command.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-70-generic 5.4.0-70.78
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  florence   1302 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Apr  2 13:51:27 2021
InstallationDate: Installed on 2021-02-09 (51 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
 Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook Flip 14_ASUS Flip TP412UA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash i8042.nomux vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-70-generic N/A
 linux-backports-modules-5.4.0-70-generic  N/A
 linux-firmware1.187.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TP412UA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TP412UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412UA.303:bd07/27/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14_ASUSFlipTP412UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: VivoBook Flip
dmi.product.name: VivoBook Flip 14_ASUS Flip TP412UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

** Attachment added: "the result of cat /proc/bus/input/devices command"
   https://bugs.launchpad.net/bugs/1922354/+attachment/5483501/+files/devices

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

Title:
  My touchpad stopped working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm filing this bug report because my touchpad recently stopped
  working at all.

  I executed this at at a terminal :  cat /proc/bus/input/devices
  but there was no touchpad in the list. 

  I read this page (https://wiki.ubuntu.com/DebuggingTouchpadDetection)
  and found out it must be a bug related to the kernel.

  I'm attaching the result of the cat /proc/bus/input/devices command.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-70-generic 5.4.0-70.78
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florence   1302 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Fri Apr  2 13:51:27 2021
  InstallationDate: Installed on 2021-02-09 (51 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook Flip 14_ASUS Flip TP412UA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash i8042.nomux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-70-generic N/A
   linux-backports-modules-5.4.0-70-generic  N/A
   linux-firmware1.187.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2018
  dmi.bios.vendor: American Megatrends Inc.

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

This change was made by a bot.

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

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

Title:
  missing amdgpu firmware reported when updating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing the following:

  update-initramfs: Generating /boot/initrd.img-5.11.0-13-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ta.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sos.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_toc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_rlc.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec2.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_me.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_pfp.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ce.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec2.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_me.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_pfp.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_ce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_sdma.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sdma.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_vcn.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_smc.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_dmcub.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_dmcub.bin for 
module amdgpu
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for cups (2.3.3op2-3ubuntu3) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.67.5-2) ...
  Processing triggers for libc-bin (2.33-0ubuntu4) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-1ubuntu3) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-11-generic 5.11.0-11.12
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dad2584 F pulseaudio
   /dev/snd/controlC0:  dad2584 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr  2 12:27:30 2021
  InstallationDate: Installed on 2021-02-08 (52 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  MachineType: TUXEDO TUXEDO Pulse 15 Gen1
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=UUID=dca66736-5282-45e6-a144-59d3339a8d0f ro quiet splash

[Kernel-packages] [Bug 1922350] [NEW] missing amdgpu firmware reported when updating

2021-04-02 Thread fossfreedom

Public bug reported:

I'm seeing the following:

update-initramfs: Generating /boot/initrd.img-5.11.0-13-generic
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ta.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_asd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_rlc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_mec.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_me.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_pfp.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_ce.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_ce.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_sdma.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_vcn.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_vcn.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_smc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/dimgrey_cavefish_dmcub.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_dmcub.bin for module 
amdgpu
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for cups (2.3.3op2-3ubuntu3) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for libglib2.0-0:amd64 (2.67.5-2) ...
Processing triggers for libc-bin (2.33-0ubuntu4) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.20-1ubuntu3) ...

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-11-generic 5.11.0-11.12
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dad2584 F pulseaudio
 /dev/snd/controlC0:  dad2584 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: Budgie:GNOME
Date: Fri Apr  2 12:27:30 2021
InstallationDate: Installed on 2021-02-08 (52 days ago)
InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210208)
MachineType: TUXEDO TUXEDO Pulse 15 Gen1
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=UUID=dca66736-5282-45e6-a144-59d3339a8d0f ro quiet splash
RebootRequiredPkgs: network-manager
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-11-generic N/A
 linux-backports-modules-5.11.0-11-generic  N/A
 linux-firmware 1.196
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N.1.07.A02
dmi.board.asset.tag: Standard
dmi.board.name: PULSE1501
dmi.board.vendor: TUXEDO

[Kernel-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)

2021-04-02 Thread Luis Arias

Just tested on the 21.04 beta iso and this issue still persists.

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

Title:
sounds not working on Dell XPS 17 (9700)

Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Fix Released

Bug description:
My investigation process:

Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
worked.

I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm
headphones,
using linux-image-5.4.0-42-generic, I did not try blutooth.

I sudo apt upgrade, dist-upgrade to get kernels

linux-image-5.8.0-38-generic
linux-image-5.8.0-40-generic

Sounds did not work.
I download linux-image-unsigned-5.10.9-051009-generic.
Sounds did not work.

I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
Sounds did not work.

After googling I found this solution in the comments:
https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

"""

Download and install dkms module:

https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
dkms/+packages

Alternatively, you can install linux-oem-20.04, it will install
the 5.6 kernel with the above driver. Your system may be more stable
with 5.4 kernel since it is in wide use.

Manually install sof-firmware from Arch Linux:

https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
firmware-1.5.1-1-any.pkg.tar.zst.html

You will need to delete the existing "sof" and "sof-tplg" files
from the Ubuntu linux-firmware package first. Note if this package
gets updated from Canoncial and they don't update these, you will have
to delete and then reextract. Files go into the
/usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg
folders.

Manually install the ucm2 files:

http://xps17.ddns.net/sof-soundwire.zip

These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
contents of the existing sof-soundwire folder (if you have it) and
replace them with the ones from the archive.

Reboot. You should now have all your audio devices available. If speakers
do not play, you may need to run alsamixer (non-root) from a terminal and
unmute and set the mixer levels all the way up.
"""

This solution worked for me on linux-image-5.6.0-1042-oem AFTER
manually opening alsa-mixer and changing soundcard to sof. The sound
would otherwise just show 'dummy'.

My sounds still do not work on 5.8 or 5.10, full name listed above. I
did not get to test this temporary fix with 5.4.

my full alsa-info:
http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

based on some google research, this seems to be a common problem:

https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/

https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/

https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
etc...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
Uname: Linux 5.6.0-1042-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: neoh 1786 F pulseaudio
/dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio
/dev/snd/controlC0: neoh 1786 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 21 12:08:45 2021
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0CXCCY
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Dependencies:

DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-01-20 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux
PackageArchitecture: all

[Kernel-packages] [Bug 1922338] [NEW] Bluetooth not working after reboot after upgrade to 21.04

2021-04-02 Thread Karol

Public bug reported:

1)
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04

2)
bluez:
  Installed: 5.56-0ubuntu3
  Candidate: 5.56-0ubuntu3
  Version table:
 *** 5.56-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status

After every reboot bluetooth doesn't work. The GNOME bluetooth on/off switch 
can be changed but doesn't have any effect - no devices are shown.
Output from systemctl after reboot:

karol@toronto:~$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Fri 2021-04-02 11:26:31 CEST; 2min 6s ago
   Docs: man:bluetoothd(8)
   Main PID: 811 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 14115)
 Memory: 3.2M
 CGroup: /system.slice/bluetooth.service
 └─811 /usr/lib/bluetooth/bluetoothd

Apr 02 11:26:24 toronto systemd[1]: Starting Bluetooth service...
Apr 02 11:26:25 toronto bluetoothd[811]: Bluetooth daemon 5.56
Apr 02 11:26:31 toronto systemd[1]: Started Bluetooth service.
Apr 02 11:26:31 toronto bluetoothd[811]: Starting SDP server
Apr 02 11:26:32 toronto bluetoothd[811]: Bluetooth management interface 1.19 
initialized
Apr 02 11:26:37 toronto bluetoothd[811]: Failed to set mode: Blocked through 
rfkill (0x12)
Apr 02 11:27:21 toronto bluetoothd[811]: Failed to set mode: Blocked through 
rfkill (0x12)
Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSink/sbc
Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSource/sbc

Then after running `sudo systemctl restart bluetooth` everything seems
to be fine:

karol@toronto:~$ sudo systemctl restart bluetooth
[sudo] password for karol:
karol@toronto:~$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Fri 2021-04-02 11:30:13 CEST; 3s ago
   Docs: man:bluetoothd(8)
   Main PID: 3152 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 14115)
 Memory: 760.0K
 CGroup: /system.slice/bluetooth.service
 └─3152 /usr/lib/bluetooth/bluetoothd

Apr 02 11:30:13 toronto systemd[1]: Starting Bluetooth service...
Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth daemon 5.56
Apr 02 11:30:13 toronto systemd[1]: Started Bluetooth service.
Apr 02 11:30:13 toronto bluetoothd[3152]: Starting SDP server
Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth management interface 1.19 
initialized
Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSink/sbc
Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSource/sbc
karol@toronto:~$

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  2 11:31:48 2021
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 80Q7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=9996d76c-d95e-4d4c-8902-0a583a091e93 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago)
dmi.bios.date: 12/16/2015
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: D5CN43WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Paris 5A8
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 300-15ISK
dmi.ec.firmware.release: 1.43
dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN43WW:bd12/16/2015:br1.43:efr1.43:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80Q7
dmi.product.sku: LENOVO_MT_80Q7_BU_idea_FM_Lenovo ideapad 300-15ISK
dmi.product.version: Lenovo ideapad 300-15ISK
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
  BD Address: 08:D4:0C:C4:D1:2C  ACL MTU: 1021:5  SCO MTU: 96:6
  UP RUNNING PSCAN ISCAN
  RX bytes:14133 acl:230 sco:0 events:330 errors:0
  TX bytes:5930 acl:17 sco:0 commands:164 errors:0

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


** Tags: amd64 apport-bug hirsute wayland-session

** Description changed:

  1)
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  
  2)
  bluez:
-   Installed: 5.56-0ubuntu3
-   Candidate: 5.56-0ubuntu3
-   Version table:
-  *** 5.56-0ubuntu3 500
- 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64

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

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 1922334

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

Title:
External monitor does not wake up on Titan Ridge laptops when docked
(9500, TB16)

Status in Dell Sputnik:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-meta-oem-5.6 package in Ubuntu:
New

Bug description:
I've recently upgraded my workhorse from XPS 9560 (2016) to a newer
generation XPS 9500 (2020) and ran into several things that feel like
regressions, but are probably related to hardware changes. This is one
of them.

tl;dr:
When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q)
connected to the dock via USB-C to USB-C (DP alternate mode), most of the time
the monitor fails to wake up after going blank.

details:
Simplest way to reproduce is for hit Super+L, wait for the monitor to
properly go in standby, then type something in or move the mouse to wake it up.
8 times out of 10 it does not wake up when using XPS 9500. Most of the time
this can be fixed by power cycling the monitor, however this has a seemingly
random chance of triggering two other issues:

1. The system to lose sight of the monitor for a brief period of time, which
sometimes causes it to hang with a black screen and needs some combination of
restarting the monitor, the dock, and the laptop, because there is a separate
USB issue making hot-plugging unusable.
2. The monitor itself gets stuck in a weird standby state where it stops
reacting to button presses and I need to hold the power button a bit longer for
it to sort of hard reset?

Notably, it wakes up fine every time when using XPS 9560 or Precision
5520 in the same setup which I have been using for ages.

This becomes particularly troublesome when screens go into short-lived
standby during boot: after the Dell logo, after entering the LUKS
password, after logging in. Each of these points has a chance of
triggering the bug, because it looks like there is some sort of mode
change and waking signal submission happening between them that
triggers it. I had to disable screen timeout as a temporary workaround
to be able to work on this system at all without having to play
"monitor wake lottery" every time I go brew a cuppa. The workaround at
boot time is to either re-roll the lottery, or boot with the dock
connected and lid open, then close the lid and keep working from
there.

The dock, the monitor, all USB peripherals are the same in both cases
- it's literally just the TB16 cable plugged into a different laptop.

I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM
(-20.04b and -20.04-edge) kernels on the 9500 with same results. I
have attempted disabling USB autosuspend via a GRUB kernel parameter
to usbcore. I have attempted both NVidia and Intel GPUs. I have
attempted playing with BIOS settings: wake on dell usb-c docks,
disable early sign of life for both checkboxes, disabling SGX and SMM,
checking all 3 boxes for Thunderbolt and switching off Thunderbolt
security. None of these make a noticeable difference.

Since it was fine with 9560, 5520 and a friend with a 9570 has no
issues either, my gut feeling is that this is due to the upgrade from
Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in
this generation - something wrong with the driver, or the firmware may
have missed some of the "lessons learned" in Alpine Ridge and caused
this regression. That would also make it applicable to 9300, which has
a "developer edition" option under Project Sputnik and several reports
of the same problem scattered across the internet:

https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a
duplicate, but for WD19TB dock on 9300, so may be slightly different too)

https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/

etc etc. Those reports suggest high bandwidth usage sometimes affects
it, so it's worth noting that my external monitor is a 1440p 144Hz one
that uses tons of bandwidth indeed.

The only hint in terms of logs seems to be this message in dmesg that
I see when power

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

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 1922336

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

Title:
  ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop
  into a dock (9500, TB16)

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-meta-oem-5.6 package in Ubuntu:
  New

Bug description:
  I've recently upgraded my workhorse from XPS 9560 (2016) to a newer
  generation XPS 9500 (2020) and ran into several things that feel like
  regressions, but are probably related to hardware changes. This is one
  of them.

  tl;dr:
  When using XPS 9500 with a TB16 dock, hot-plugging the dock causes ACPI 
errors in dmesg and some kind of reset loop with USB peripherals connected via 
the dock.

  
  details:
  USB peripherals keep reconnecting according to dmesg, but in practice they 
barely ever finish registering with the system before disappearing again. Maybe 
1 out of 40 USB keyboard presses registers while this is happening. At this 
point my choices are to either reboot with the dock connected or work without 
the dock and consequently without any peripherals on my desk. Booting with an 
open lid and the dock connected works fine until I re-plug the dock.

  Notably, it hot-plugs fine every time when using XPS 9560 or Precision
  5520 in the same setup which I have been using for ages and which had
  similar problems until around kernel 4.13.

  Since it was fine with 9560, 5520 and a friend with a 9570 has no
  issues either, my gut feeling is that this is due to the upgrade from
  Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in
  this generation - something wrong with the driver, or the firmware may
  have missed some of the "lessons learned" in Alpine Ridge and caused
  this regression. That would also make it applicable to 9300, which has
  a "developer edition" option under Project Sputnik.

  I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM
  (-20.04b and -20.04-edge) kernels on the 9500 with same results. I
  have attempted rebinding the XHCI controller after reconnecting the
  dock. I have attempted disabling USB autosuspend and ASPM via a GRUB
  kernel parameter. I have attempted playing with BIOS settings: wake on
  dell usb-c docks, disable early sign of life for both checkboxes,
  disabling SGX and SMM, checking all 3 boxes for Thunderbolt and
  switching off Thunderbolt security. None of these make a noticeable
  difference.

  System config:

  XPS 9500, i7, 32GB RAM
  BIOS 1.6.1, TB3 firmware NVM60
  Ubuntu 20.04.02 LTS, kernels 5.6-oem, 5.8-generic, 5.10-oem (same behaviour)
  TB16 dock firmware 1.0.4 (MST 3.12.02)

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

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

[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)

2021-04-02 Thread Georgi Boiko

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

** Also affects: linux-meta-oem-5.6 (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/1922334

Title:
  External monitor does not wake up on Titan Ridge laptops when docked
  (9500, TB16)

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  New
Status in linux-meta-oem-5.6 package in Ubuntu:
  New

Bug description:
  I've recently upgraded my workhorse from XPS 9560 (2016) to a newer
  generation XPS 9500 (2020) and ran into several things that feel like
  regressions, but are probably related to hardware changes. This is one
  of them.

  tl;dr:
  When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) 
connected to the dock via USB-C to USB-C (DP alternate mode), most of the time 
the monitor fails to wake up after going blank.

  
  details:
  Simplest way to reproduce is for hit Super+L, wait for the monitor to 
properly go in standby, then type something in or move the mouse to wake it up. 
8 times out of 10 it does not wake up when using XPS 9500. Most of the time 
this can be fixed by power cycling the monitor, however this has a seemingly 
random chance of triggering two other issues:

  1. The system to lose sight of the monitor for a brief period of time, which 
sometimes causes it to hang with a black screen and needs some combination of 
restarting the monitor, the dock, and the laptop, because there is a separate 
USB issue making hot-plugging unusable.
  2. The monitor itself gets stuck in a weird standby state where it stops 
reacting to button presses and I need to hold the power button a bit longer for 
it to sort of hard reset?

  Notably, it wakes up fine every time when using XPS 9560 or Precision
  5520 in the same setup which I have been using for ages.

  This becomes particularly troublesome when screens go into short-lived
  standby during boot: after the Dell logo, after entering the LUKS
  password, after logging in. Each of these points has a chance of
  triggering the bug, because it looks like there is some sort of mode
  change and waking signal submission happening between them that
  triggers it. I had to disable screen timeout as a temporary workaround
  to be able to work on this system at all without having to play
  "monitor wake lottery" every time I go brew a cuppa. The workaround at
  boot time is to either re-roll the lottery, or boot with the dock
  connected and lid open, then close the lid and keep working from
  there.

  The dock, the monitor, all USB peripherals are the same in both cases
  - it's literally just the TB16 cable plugged into a different laptop.

  I have attempted  5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM
  (-20.04b and -20.04-edge) kernels on the 9500 with same results. I
  have attempted disabling USB autosuspend via a GRUB kernel parameter
  to usbcore. I have attempted both NVidia and Intel GPUs. I have
  attempted playing with BIOS settings: wake on dell usb-c docks,
  disable early sign of life for both checkboxes, disabling SGX and SMM,
  checking all 3 boxes for Thunderbolt and switching off Thunderbolt
  security. None of these make a noticeable difference.

  Since it was fine with 9560, 5520 and a friend with a 9570 has no
  issues either, my gut feeling is that this is due to the upgrade from
  Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in
  this generation - something wrong with the driver, or the firmware may
  have missed some of the "lessons learned" in Alpine Ridge and caused
  this regression. That would also make it applicable to 9300, which has
  a "developer edition" option under Project Sputnik and several reports
  of the same problem scattered across the internet:

  
https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a 
duplicate, but for WD19TB dock on 9300, so may be slightly different too)
  
https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/

  etc etc. Those reports suggest high bandwidth usage sometimes affects
  it, so it's worth noting that my external monitor is a 1440p 144Hz one
  that uses tons of bandwidth indeed.

  The only hint in terms of logs seems to be this message in dmesg that
  I see when power cycling the monitor and getting back into the system:

  [  250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present
  [  250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
  [  250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to 
D0 (config space inaccessible)
  [  250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19
  [  250.778340]

[Kernel-packages] [Bug 1922336] Re: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16)

2021-04-02 Thread Georgi Boiko

Kernel logs with the ACPI errors

** Attachment added: "usb-acpi-reset-loop.log"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1922336/+attachment/5483390/+files/usb-acpi-reset-loop.log

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

** Also affects: linux-meta-oem-5.6 (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/1922336

Title:
  ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop
  into a dock (9500, TB16)

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  New
Status in linux-meta-oem-5.6 package in Ubuntu:
  New

Bug description:
  I've recently upgraded my workhorse from XPS 9560 (2016) to a newer
  generation XPS 9500 (2020) and ran into several things that feel like
  regressions, but are probably related to hardware changes. This is one
  of them.

  tl;dr:
  When using XPS 9500 with a TB16 dock, hot-plugging the dock causes ACPI 
errors in dmesg and some kind of reset loop with USB peripherals connected via 
the dock.

  
  details:
  USB peripherals keep reconnecting according to dmesg, but in practice they 
barely ever finish registering with the system before disappearing again. Maybe 
1 out of 40 USB keyboard presses registers while this is happening. At this 
point my choices are to either reboot with the dock connected or work without 
the dock and consequently without any peripherals on my desk. Booting with an 
open lid and the dock connected works fine until I re-plug the dock.

  Notably, it hot-plugs fine every time when using XPS 9560 or Precision
  5520 in the same setup which I have been using for ages and which had
  similar problems until around kernel 4.13.

  Since it was fine with 9560, 5520 and a friend with a 9570 has no
  issues either, my gut feeling is that this is due to the upgrade from
  Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in
  this generation - something wrong with the driver, or the firmware may
  have missed some of the "lessons learned" in Alpine Ridge and caused
  this regression. That would also make it applicable to 9300, which has
  a "developer edition" option under Project Sputnik.

  I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM
  (-20.04b and -20.04-edge) kernels on the 9500 with same results. I
  have attempted rebinding the XHCI controller after reconnecting the
  dock. I have attempted disabling USB autosuspend and ASPM via a GRUB
  kernel parameter. I have attempted playing with BIOS settings: wake on
  dell usb-c docks, disable early sign of life for both checkboxes,
  disabling SGX and SMM, checking all 3 boxes for Thunderbolt and
  switching off Thunderbolt security. None of these make a noticeable
  difference.

  System config:

  XPS 9500, i7, 32GB RAM
  BIOS 1.6.1, TB3 firmware NVM60
  Ubuntu 20.04.02 LTS, kernels 5.6-oem, 5.8-generic, 5.10-oem (same behaviour)
  TB16 dock firmware 1.0.4 (MST 3.12.02)

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

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

[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz


  
  Starting c1
  action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror 
msg="Failed starting container" name=c1 stateful=false 
t=2021-03-30T02:42:14+
  error: Error calling 'lxd forkstart c1 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': 
err='Failed to run: /usr/bin/lxd forkstart c1 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: '
lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script 
exited with status 137.
lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to 
run mount hooks for container 'c1'.
lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to 
setup container "c1".
lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error 
occurred in another process (expected sequence number 5)
lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed 
to spawn container "c1".
lxc 20210330024214.663 ERROR lxc_container - 
lxccontainer.c:wait_on_daemonized_start:804 - Received container state 
"ABORTING" instead of "RUNNING"

  Try `lxc info --show-log lxd2:c1` for more info
  ==> Cleaning up
  ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
  ==> Deleting all containers
  ==> Deleting all images
  ==> Deleting all profiles
  Profile default deleted
  Profile docker deleted
  ==> Checking for locked DB tables
  ==> Checking for leftover files
  ==> Checking for leftover DB entries
  ==> Tearing down directory backend in 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
  ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
  ==> Deleting all containers
  ==> Deleting all images
  ==> Deleting all profiles
  Profile default deleted
  Profile docker deleted
  ==> Checking for locked DB tables
  ==> Checking for leftover files
  ==> Checking for leftover DB entries
  ==> Tearing down directory backend in 
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt

  
  ==> TEST DONE: remote usage
  ==> Test result: failure

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

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

[Kernel-packages] [Bug 1922200] Re: linux ADT test failure with linux/4.4.0-207.239 - ubuntu_qrt_kernel_security.test-kernel-security.py