[Kernel-packages] [Bug 1942952] Re: Kernel Call Trace on Secure Boot

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel Call Trace on Secure Boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  Could the call traces in dmesg be related to UEFI secure boot?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-34-generic 5.11.0-34.36
  ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  js1 948 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Sep  7 21:05:54 2021
  InstallationDate: Installed on 2021-09-06 (1 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M
   |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic 
root=/dev/mapper/vgkubuntu-root ro ipv6.disable=1 elevator=deadline splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.197.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 15.63
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.63
  dmi.board.name: 84B6
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 76.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 76.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.63:bd03/25/2021:br15.63:efr76.32:svnHP:pn:pvr:sku:rvnHP:rn84B6:rvrKBCVersion76.32:cvnHP:ct10:cvrChassisVersion:
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1943287] Re: Can't start qemu on linux-5.14.2-051402-lowlatency

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't start qemu on linux-5.14.2-051402-lowlatency

Status in linux package in Ubuntu:
  Expired

Bug description:
  After installing kernel package linux-image-
  unsigned-5.14.2-051402-lowlatency from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/ starting libvirtd, and
  thus qemu, results in 2 stack traces. Then libvirtd stops.

  Rolling back to 5.11.0-34-lowlatency fixes the problem.

  sep 10 17:07:37 kernel: invalid opcode:  [#3] PREEMPT SMP NOPTI
  sep 10 17:07:37 kernel: CPU: 8 PID: 21670 Comm: daemon-init Tainted: G  D 
W 5.14.2-051402-lowlatency #202109080331
  sep 10 17:07:37 kernel: Hardware name: Supermicro 
C9X299-PG300F/C9X299-PG300F, BIOS 2.1 06/16/2020
  sep 10 17:07:37 kernel: RIP: 0010:vmx_create_vcpu+0x6a7/0x6f0 [kvm_intel]
  sep 10 17:07:37 kernel: Code: 89 e7 48 8d 75 cc ba 04 00 00 00 e8 c3 58 fb d1 
85 c0 74 d7 4c 89 ff 4c 89 f3 41 bd f2 ff ff ff e8 fe d9 5f d2 e9 0b fd ff ff 
<0f> 0b 4c 89 ff 45 89 e5 e8 ec d9 5f d2 45 85 e4 0f 84 34 fb ff ff
  sep 10 17:07:37 kernel: RSP: 0018:b976caa0fc78 EFLAGS: 00010202
  sep 10 17:07:37 kernel: RAX: 9fce6af99db0 RBX: 9fce6af98000 RCX: 
0007
  sep 10 17:07:37 kernel: RDX: 0006 RSI: 0001 RDI: 
0122
  sep 10 17:07:37 kernel: RBP: b976caa0fcb8 R08:  R09: 
9fce6afa1080
  sep 10 17:07:37 kernel: R10: 0293 R11: 9fdd3fc33588 R12: 
0007
  sep 10 17:07:37 kernel: R13: fff4 R14: 9fce6af98000 R15: 

  sep 10 17:07:37 kernel: FS:  7f75e8b79640() GS:9fdd3fc0() 
knlGS:
  sep 10 17:07:37 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  sep 10 17:07:37 kernel: CR2: 7f75f8dc2800 CR3: 000314c88005 CR4: 
003726e0
  sep 10 17:07:37 kernel: DR0:  DR1:  DR2: 

  sep 10 17:07:37 kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  sep 10 17:07:37 kernel: Call Trace:
  sep 10 17:07:37 kernel:  kvm_arch_vcpu_create+0x288/0x390 [kvm]
  sep 10 17:07:37 kernel:  kvm_vm_ioctl_create_vcpu+0x188/0x420 [kvm]
  sep 10 17:07:37 kernel:  ? obj_cgroup_uncharge_pages+0x69/0xe0
  sep 10 17:07:37 kernel:  kvm_vm_ioctl+0x546/0x7b0 [kvm]
  sep 10 17:07:37 kernel:  ? kvm_uevent_notify_change.part.0+0x17b/0x210 [kvm]
  sep 10 17:07:37 kernel:  ? kfree+0x22a/0x3e0
  sep 10 17:07:37 kernel:  ? __fget_files+0x74/0xa0
  sep 10 17:07:37 kernel:  __x64_sys_ioctl+0x8e/0xc0
  sep 10 17:07:37 kernel:  do_syscall_64+0x59/0xc0
  sep 10 17:07:37 kernel:  ? do_syscall_64+0x69/0xc0
  sep 10 17:07:37 kernel:  ? exit_to_user_mode_prepare+0x37/0xb0
  sep 10 17:07:37 kernel:  ? syscall_exit_to_user_mode+0x27/0x50
  sep 10 17:07:37 kernel:  ? do_syscall_64+0x69/0xc0
  sep 10 17:07:37 kernel:  ? exit_to_user_mode_prepare+0x37/0xb0
  sep 10 17:07:37 kernel:  ? syscall_exit_to_user_mode+0x27/0x50
  sep 10 17:07:37 kernel:  ? __x64_sys_close+0x11/0x40
  sep 10 17:07:37 kernel:  ? do_syscall_64+0x69/0xc0
  sep 10 17:07:37 kernel:  ? exit_to_user_mode_prepare+0x37/0xb0
  sep 10 17:07:37 kernel:  ? syscall_exit_to_user_mode+0x27/0x50
  sep 10 17:07:37 kernel:  ? __x64_sys_read+0x19/0x20
  sep 10 17:07:37 kernel:  ? do_syscall_64+0x69/0xc0
  sep 10 17:07:37 kernel:  ? asm_sysvec_apic_timer_interrupt+0xa/0x20
  sep 10 17:07:37 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
  sep 10 17:07:37 kernel: RIP: 0033:0x7f75f895aecb
  sep 10 17:07:37 kernel: Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 
4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 
<48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6d 1f 0d 00 f7 d8 64 89 01 48

  sep 10 17:07:37 kernel: RSP: 002b:7f75e8b78498 EFLAGS: 0246 ORIG_RAX: 
0010
  sep 10 17:07:37 kernel: RAX: ffda RBX: 7f75b02d1260 RCX: 
7f75f895aecb
  sep 10 17:07:37 kernel: RDX:  RSI: ae41 RDI: 
0022
  sep 10 17:07:37 kernel: RBP: 7f75e8b78510 R08:  R09: 

  sep 10 17:07:37 kernel: R10:  R11: 0246 R12: 

  sep 10 17:07:37 kernel: R13: 7f75b02ddd18 R14:  R15: 
7f75b02ddd10
  sep 10 17:07:37 kernel: Modules linked in: cpuid snd_seq_dummy snd_hrtimer 
ip6t_REJECT nf_reject_ipv6 xt_CHECKSUM xt_tcpudp ipt_REJECT nf_reject_ipv4 
xt_set ip_set_hash_ip ip_set bridge stp llc xt_MASQUERADE xt_conntrack 
nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nf_tables nfnetlink zstd lz4 lz4_compress zram netconsole 
macvlan binfmt_misc dm_crypt 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  System crash loop randomly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The systems seems to crash loop randomly.Audio logs loop at a 2 second
  interval(approximate).


  Release:21.10
  Package: Ubuntu Base (Released on Nov 1 via software updater)
  Kernel:5.13.0-22-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 12 16:32:21 2021
  InstallationDate: Installed on 2017-03-09 (1709 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Bluetooth Adapter Not Detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Attempted every Stackoverflow & related solution I could find, at this
  point I can only assume this is a bug.

  Installed Ubuntu 21.10 on ASUS-TUF-Gaming-F17-FX706HM-TUF706HM. No
  Bluetooth devices can connect.

  Exact symptoms:

  Click on the taskbar. It says Bluetooth Off. When I expand that, it
  gives me the option to turn Bluetooth off. That is not a typo.

  Go into Settings->Bluetooth. Sliding button on the top says Bluetooth
  is on (button is on the right, filled in purple), but the page says
  Bluetooth is off.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   1632 F pulseaudio
   /dev/snd/pcmC0D0p:   alex   1632 F...m pulseaudio
   /dev/snd/controlC1:  alex   1632 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Fri Nov 12 20:52:18 2021
  InstallationDate: Installed on 2021-11-07 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F17 FX706HM_TUF706HM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=46136636-f0da-438b-826d-858cd17bf141 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX706HM.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX706HM
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX706HM.309:bd10/05/2021:br5.19:efr3.6:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF17FX706HM_TUF706HM:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnFX706HM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ASUS TUF Gaming F17
  dmi.product.name: ASUS TUF Gaming F17 FX706HM_TUF706HM
  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/1950842/+subscriptions


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

[Kernel-packages] [Bug 1950842] [NEW] Bluetooth Adapter Not Detected

[Alex B]

Public bug reported:

Attempted every Stackoverflow & related solution I could find, at this
point I can only assume this is a bug.

Installed Ubuntu 21.10 on ASUS-TUF-Gaming-F17-FX706HM-TUF706HM. No
Bluetooth devices can connect.

Exact symptoms:

Click on the taskbar. It says Bluetooth Off. When I expand that, it
gives me the option to turn Bluetooth off. That is not a typo.

Go into Settings->Bluetooth. Sliding button on the top says Bluetooth is
on (button is on the right, filled in purple), but the page says
Bluetooth is off.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alex   1632 F pulseaudio
 /dev/snd/pcmC0D0p:   alex   1632 F...m pulseaudio
 /dev/snd/controlC1:  alex   1632 F pulseaudio
CasperMD5CheckResult: pass
Date: Fri Nov 12 20:52:18 2021
InstallationDate: Installed on 2021-11-07 (5 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F17 FX706HM_TUF706HM
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=46136636-f0da-438b-826d-858cd17bf141 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX706HM.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX706HM
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.ec.firmware.release: 3.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX706HM.309:bd10/05/2021:br5.19:efr3.6:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF17FX706HM_TUF706HM:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnFX706HM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ASUS TUF Gaming F17
dmi.product.name: ASUS TUF Gaming F17 FX706HM_TUF706HM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug impish

** Attachment added: "attachments.tar.gz"
   
https://bugs.launchpad.net/bugs/1950842/+attachment/5540538/+files/attachments.tar.gz

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

Title:
  Bluetooth Adapter Not Detected

Status in linux package in Ubuntu:
  New

Bug description:
  Attempted every Stackoverflow & related solution I could find, at this
  point I can only assume this is a bug.

  Installed Ubuntu 21.10 on ASUS-TUF-Gaming-F17-FX706HM-TUF706HM. No
  Bluetooth devices can connect.

  Exact symptoms:

  Click on the taskbar. It says Bluetooth Off. When I expand that, it
  gives me the option to turn Bluetooth off. That is not a typo.

  Go into Settings->Bluetooth. Sliding button on the top says Bluetooth
  is on (button is on the right, filled in purple), but the page says
  Bluetooth is off.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   1632 F pulseaudio
   /dev/snd/pcmC0D0p:   alex   1632 F...m pulseaudio
   /dev/snd/controlC1:  alex   1632 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Fri Nov 12 20:52:18 2021
  InstallationDate: Installed on 2021-11-07 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F17 FX706HM_TUF706HM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=46136636-f0da-438b-826d-858cd17bf141 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit 

[Kernel-packages] [Bug 1950834] Re: System crash loop randomly.

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

I changed ubuntu-release-upgrader (which moves a system from one
release, to a later release; eg. 21.04 to 21.10) to the linux kernel.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

** Package changed: ubuntu-release-upgrader (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/1950834

Title:
  System crash loop randomly.

Status in linux package in Ubuntu:
  New

Bug description:
  The systems seems to crash loop randomly.Audio logs loop at a 2 second
  interval(approximate).


  Release:21.10
  Package: Ubuntu Base (Released on Nov 1 via software updater)
  Kernel:5.13.0-22-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-release-upgrader-core 1:21.10.8
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 12 16:32:21 2021
  InstallationDate: Installed on 2017-03-09 (1709 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

[Kernel-packages] [Bug 1950834] [NEW] System crash loop randomly.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The systems seems to crash loop randomly.Audio logs loop at a 2 second
interval(approximate).


Release:21.10
Package: Ubuntu Base (Released on Nov 1 via software updater)
Kernel:5.13.0-22-generic

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-core 1:21.10.8
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 12 16:32:21 2021
InstallationDate: Installed on 2017-03-09 (1709 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade impish third-party-packages
-- 
System crash loop randomly. 
https://bugs.launchpad.net/bugs/1950834
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 1950721] Re: Re-enable CONFIG_PINCTRL_ELKHARTLAKE

[Anthony Wong]

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

** Changed in: linux-intel-5.13 (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Changed in: linux-intel-5.13 (Ubuntu)
   Status: New => Triaged

** Description changed:

  We have test BIOS now for supporting pinctrl. From what we learnt, ODMs
- also got the BIOS fix, so it's now time to re-enable this kernel config.
+ also got the BIOS fix, it's now time to re-enable this kernel config.

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

Title:
  Re-enable CONFIG_PINCTRL_ELKHARTLAKE

Status in HWE Next:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Triaged

Bug description:
  We have test BIOS now for supporting pinctrl. From what we learnt,
  ODMs also got the BIOS fix, it's now time to re-enable this kernel
  config.

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


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

[Kernel-packages] [Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD

[Shaun]

Hey, look what I found!
https://gitlab.freedesktop.org/drm/amd/-/issues/1671 there is also
https://gitlab.freedesktop.org/drm/amd/-/issues/1438 which is the bug
report for the previous legion laptops, that one seems to center around
the 4000 series APUs, whereas this time it's centered around the 5000
series.

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1671
   https://gitlab.freedesktop.org/drm/amd/-/issues/1671

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1438
   https://gitlab.freedesktop.org/drm/amd/-/issues/1438

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

Title:
  Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD

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

Bug description:
  The screen brightness controls don't work on the Legion Slim 7 (AMD)
  laptop running in hybrid/dynamic mode.

  The backlight control files appear in /sys/class/backlight/amdgpu_bl0,
  and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the
  value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the
  screen brightness always remains at 100%.

  I have tried kernel boot parameters:

  acpi_backlight=vendor

  amdgpu.backlight=0

  but neither makes any difference.

  I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can
  get the backlight working with the amdgpu.backlight=0 kernel boot
  parameter. One difference between them and this laptop is that it has
  advanced optimus, meaning that it can switch the laptop display
  between the amdgpu and nvidia card without rebooting, if that is at
  all relevant.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rocko  1978 F pulseaudio
   /dev/snd/controlC1:  rocko  1978 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 20 09:20:33 2021
  InstallationDate: Installed on 2021-09-15 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 82K8
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic 
root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet 
splash amdgpu.backlight=0 vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.200
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3

[Anonymous]

** Tags added: kernel-bug-exists-upstream

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

Title:
  wifi (mwifiex_pcie) stops working undeterministically in 18.04 on
  Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
  After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  logs as attachments are following

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


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

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

[Anonymous]

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1950825/+attachment/5540507/+files/RfKill.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

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

[Anonymous]

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540501/+files/ProcCpuinfo.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem 

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

[Anonymous]

apport information

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a 

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

[Anonymous]

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540503/+files/ProcEnviron.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem 

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

[Anonymous]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540500/+files/Lsusb-v.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a 

[Kernel-packages] [Bug 1950825] acpidump.txt

[Anonymous]

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540510/+files/acpidump.txt

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

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540492/+files/AlsaInfo.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540493/+files/CRDA.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540494/+files/CurrentDmesg.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540495/+files/IwConfig.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540496/+files/Lspci.txt

** Attachment removed: "Lspci-vt.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540497/+files/Lspci-vt.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540498/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540501/+files/ProcCpuinfo.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540502/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540503/+files/ProcEnviron.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540508/+files/UdevDb.txt

** Attachment removed: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540510/+files/acpidump.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540507/+files/RfKill.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540505/+files/ProcModules.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540504/+files/ProcInterrupts.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540506/+files/PulseList.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+attachment/5540509/+files/WifiSyslog.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a 

[Kernel-packages] [Bug 1950825] PulseList.txt

[Anonymous]

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540506/+files/PulseList.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

[Kernel-packages] [Bug 1950825] Lsusb.txt

[Anonymous]

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1950825/+attachment/5540498/+files/Lsusb.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem 

[Kernel-packages] [Bug 1950825] Lspci-vt.txt

[Anonymous]

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540497/+files/Lspci-vt.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

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

[Anonymous]

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

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

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

[Anonymous]

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540495/+files/IwConfig.txt

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 

[Kernel-packages] [Bug 1950825] Re: Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some headset / speakers

[Anonymous]

** Tags added: apport-collected focal

** Description changed:

  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb
  
  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:
  
  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  
  So it pretty much looks like the laptop sends a connection request, but
  never sees a reply from the Teufel headset.
  
  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:
  
  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
  Handle: 1
  > HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 
5.078928
Read Remote Supported Features (0x01|0x001b) ncmd 1
  Status: Success (0x00)
  [...]
  
  What could cause the Intel 8087 / 0029 bluetooth chip / driver not being
  able to connect to the Teufel speakers?
  
  There is also another report with a similar problem here: 
https://askubuntu.com/questions/1020584/apple-keyboard-a1016-pairing-fails
  How to further debug this problem?
  Is it necessary to buy some bt sniffer hardware to get to the bottom of this? 
I would invest in a cheapo 10€ CC2531 clone sniffer (like this 
https://www.amazon.com/-/en/dp/B081WRGL31) but I am not sure if they are 
sufficient to capture the pairing 

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1950825

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

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
8.822002
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 
8.822041
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 
8.822352
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 
39.891457
  Status: LMP Response Timeout / LL Response Timeout (0x22)
  Handle: 65535
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL (0x01)
  Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 
39.891549
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 
39.891575
Pair Device (0x0019) plen 7
  Status: Timeout (0x08)
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 
4.925811
  BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 
4.925831
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Packet type: 0xcc18
DM1 may be used
DH1 may be used
DM3 may be used
DH3 may be used
DM5 may be used
DH5 may be used
  Page scan repetition mode: R2 (0x02)
  Page scan mode: Mandatory (0x00)
  Clock offset: 0x
  Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 
4.928927
Create Connection (0x01|0x0005) ncmd 1
  Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 
5.077961
  Status: Success (0x00)
  Handle: 1
  Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
  Link type: ACL 

[Kernel-packages] [Bug 1950825] [NEW] Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some headset / speakers

[Anonymous]

Public bug reported:

I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
with Intel bluetooth card. dmesg recognizes it as:
usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
It uses the btusb driver:
usbcore: registered new interface driver btusb

The driver / chip has problems to connect / pair with some headsets / speakers. 
Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy Wireless headset.
Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
It looks like this on btmon:

@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 8.822002
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: KeyboardDisplay (0x04)
< HCI Command: Create Connection (0x01|0x0005) plen 13  #22 [hci0] 8.822041
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
  DM1 may be used
  DH1 may be used
  DM3 may be used
  DH3 may be used
  DM5 may be used
  DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4   #23 [hci0] 8.822352
  Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11   #28 [hci0] 39.891457
Status: LMP Response Timeout / LL Response Timeout (0x22)
Handle: 65535
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8  {0x0002} [hci0] 39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Connect Failed (0x000d) plen 8  {0x0001} [hci0] 39.891549
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10   {0x0001} [hci0] 39.891575
  Pair Device (0x0019) plen 7
Status: Timeout (0x08)
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

So it pretty much looks like the laptop sends a connection request, but
never sees a reply from the Teufel headset.

Same conversation for a Surface Pro 3 laptop (with some broadcom
bluetooth chip if I remember correctly, also using btusb driver) also
running Ubuntu 20.04:

@ MGMT Command: Pair Device (0x0019) plen 8{0x0001} [hci0] 4.925811
BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Capability: DisplayYesNo (0x01)
< HCI Command: Create Connection (0x01|0x0005) plen 13  #50 [hci0] 4.925831
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Packet type: 0xcc18
  DM1 may be used
  DH1 may be used
  DM3 may be used
  DH3 may be used
  DM5 may be used
  DH5 may be used
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x
Role switch: Allow slave (0x01)
> HCI Event: Command Status (0x0f) plen 4   #51 [hci0] 4.928927
  Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event: Connect Complete (0x03) plen 11#54 [hci0] 5.077961
Status: Success (0x00)
Handle: 1
Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 5.078179
Handle: 1
> HCI Event: Command Status (0x0f) plen 4   #56 [hci0] 5.078928
  Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
[...]

What could cause the Intel 8087 / 0029 bluetooth chip / driver not being
able to connect to the Teufel speakers?

There is also another report with a similar problem here: 
https://askubuntu.com/questions/1020584/apple-keyboard-a1016-pairing-fails
How to further debug this problem?
Is it necessary to buy some bt sniffer hardware to get to the bottom of this? I 
would invest in a cheapo 10€ CC2531 clone sniffer (like this 
https://www.amazon.com/-/en/dp/B081WRGL31) but I am not sure if they are 
sufficient to capture the pairing process.

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


** Tags: hirsute

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel

[Mike]

Debug loop from Modem Manager with endless loop on modem initialization
on kernel 5.13.x.

** Attachment added: "Debug Log from Modem Manager"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+attachment/5540476/+files/ModemManager.Debug.log

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

Title:
  HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Focal Fossa 20.04.1
  HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It 
is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't 
use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem.
  I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible 
with updated libc from Ubuntu 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mp 2798 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (554 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 820 G3
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash 
resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware 1.187.20
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.asset.tag: 5CG60906BD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook820G3:pvr:skuL4Q17AV:rvnHP:rn807C:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.product.sku: L4Q17AV
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1050.49)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1050.49) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 (amd64)
virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
lttng-modules/2.12.5-1ubuntu2~20.04.1 (amd64)
rtl8821ce/5.5.2.1-0ubuntu4~20.04.4 (amd64)
evdi/1.9.1-1ubuntu4~20.04.1 (amd64)
oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.91.102~18.04.81)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-hwe-5.4 
(5.4.0.91.102~18.04.81) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
v4l2loopback/0.10.0-1ubuntu1.2 (s390x)
kpatch/0.5.0-0ubuntu1.1 (amd64)
acpi-call/1.1.0-4 (ppc64el, s390x)
virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
asic0x/1.0.1-1 (s390x)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-hwe-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-dell300x/4.15.0.1031.33)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-dell300x (4.15.0.1031.33) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/237-3ubuntu10.52 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-dell300x

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1950816] [NEW] Bionic update: upstream stable patchset 2021-11-12

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2021-11-12

Ported from the following upstream stable releases:
v4.14.250, v4.19.210
v4.14.251, v4.19.211
   v4.19.212
v4.14.252, v4.19.213

   from git://git.kernel.org/

net: mdio: introduce a shutdown method to mdio device drivers
xen-netback: correct success/error reporting for the SKB-with-fraglist case
sparc64: fix pci_iounmap() when CONFIG_PCI is not set
ext2: fix sleeping in atomic bugs on error
scsi: sd: Free scsi_disk device via put_device()
usb: testusb: Fix for showing the connection speed
usb: dwc2: check return value after calling platform_get_resource()
scsi: ses: Retry failed Send/Receive Diagnostic commands
libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD.
lib/timerqueue: Rely on rbtree semantics for next timer
selftests: be sure to make khdr before other targets
UBUNTU: upstream stable to v4.14.250, v4.19.210
Partially revert "usb: Kconfig: using select for USB_COMMON dependency"
USB: cdc-acm: fix racy tty buffer accesses
USB: cdc-acm: fix break reporting
ovl: fix missing negative dentry check in ovl_rename()
nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero
xen/balloon: fix cancelled balloon action
ARM: dts: omap3430-sdp: Fix NAND device node
ARM: dts: qcom: apq8064: use compatible which contains chipid
bpf: add also cbpf long jump test cases with heavy expansion
bpf, mips: Validate conditional branch offsets
xtensa: call irqchip_init only when CONFIG_USE_OF is selected
bpf: Fix integer overflow in prealloc_elems_and_freelist()
phy: mdio: fix memory leak
net_sched: fix NULL deref in fifo_set_limit()
powerpc/fsl/dts: Fix phy-connection-type for fm1mac3
ptp_pch: Load module automatically if ID matches
ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence
net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size()
netlink: annotate data races around nlk->bound
drm/nouveau/debugfs: fix file release memory leak
rtnetlink: fix if_nlmsg_stats_size() under estimation
i40e: fix endless loop under rtnl
i2c: acpi: fix resource leak in reconfiguration device addition
net: phy: bcm7xxx: Fixed indirect MMD operations
HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
netfilter: ip6_tables: zero-initialize fragment offset
mac80211: Drop frames from invalid MAC address in ad-hoc mode
m68k: Handle arrivals of multiple signals correctly
net: sun: SUNVNET_COMMON should depend on INET
scsi: ses: Fix unsigned comparison with less than zero
scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
perf/x86: Reset destroy callback on event init failure
sched: Always inline is_percpu_thread()
bpf, arm: Fix register clobbering in div/mod implementation
i40e: Fix freeing of uninitialized misc IRQ vector
UBUNTU: upstream stable to v4.14.251, v4.19.211
mac80211: check return value of rhashtable_init
UBUNTU: upstream stable to v4.19.212
stable: clamp SUBLEVEL in 4.14
ALSA: seq: Fix a potential UAF by wrong private_free call order
s390: fix strrchr() implementation
btrfs: deal with errors when replaying dir entry during log replay
btrfs: deal with errors when adding inode reference during log replay
btrfs: check for error when looking up inode during dir entry replay
xhci: Fix command ring pointer corruption while aborting a command
xhci: Enable trust tx length quirk for Fresco FL11 USB controller
cb710: avoid NULL pointer subtraction
efi/cper: use stack buffer for error record decoding
efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock()
usb: musb: dsps: Fix the probe error path
Input: xpad - add support for another USB ID of Nacon GC-100
USB: serial: qcserial: add EM9191 QDL support
USB: serial: option: add Quectel EC200S-CN module support
USB: serial: option: add Telit LE910Cx composition 0x1204
USB: serial: option: add prod. id for Quectel EG91
virtio: write back F_VERSION_1 before validate
nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells
x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically
iio: adc: aspeed: set driver data when adc probe.
iio: adc128s052: Fix the error handling path of 'adc128_probe()'
iio: light: opt3001: Fixed timeout error when 0 lux
iio: ssp_sensors: add more range checking in ssp_parse_dataframe()
iio: ssp_sensors: fix error code in ssp_print_mcu_debug()
sctp: account stream padding length for reconf chunk
net: arc: select CRC32

[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs

[Heitor Alves de Siqueira]

Verified for Focal according to test case from description. A standard
multipass VM with 8 vCPUs configured was able to capture a kernel dump
without errors.

Additionally, since the 5.4 kernel doesn't hit the MMU/reset bug
directly, I've done some additional testing to ensure we didn't
introduce any weird regressions. These scenarios included:

- default crash kernel config
- nested VM crash kernel with multiple CPUs
- nested VM crash kernel with default config
- basic smoke testing of VM up/down through virsh
- basic smoke testing of reboots from within the VM

All of these behaved as expected and showed no issues.

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

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

Title:
  KVM emulation failure when booting into  VM crash kernel with multiple
  CPUs

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

Bug description:
  [Impact]
  When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.

  This happens only when there are multiple enabled CPUs in the crash
  kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
  being used. Due to the vCPU MMU state not being cleaned up correctly,
  the secondary CPUs try to access virtual addresses with a faulty MMU
  context that will result in the emulation failure. This shows up with
  a similar spew as below:

  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000  9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3=290b8001 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70  71 66 
0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a

  [Test Plan]
  1. Boot an Ubuntu guest VM with e.g. multipass:
  $ multipass launch daily:focal -c8 -m16g -n focal-vm

  2. Configure guest crash kernel command-line with `nr_cpus=8`:
  ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line
  KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0"

  3. Crash guest VM and watch for the KVM emulation failure:
  ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger

  [Where problems could occur]
  As we're resetting MMU context on vCPUs, potential regressions would show up 
in workloads relying on KVM guests. We should properly test the scenario 
mentioned in the bug to make sure secondary CPUs are being cleaned up properly, 
and that no other regressions have been introduced when rebooting or kexec'ing 
into different kernels.
  Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression 
potential should be fairly low and contained to starting/resetting vCPUs (i.e. 
VM start and reboot).

  [Other info]
  This has been fixed by upstream commit:
0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT

  The commit above has been picked up by stable trees up until 5.11, so it's 
only needed in Bionic and Focal (4.15 and 5.4 kernels). There are also two 
follow up commits, which revert the vendor-specific resets:
5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()

  These follow ups have not been picked up in stable trees due to the risk of
  regressions. According to the original fix, they have been introduced 
primarily to aid bisection in case there are workflows relying on the vendor 
resets. As these are not required for the fix and don't conflict with the 
backport, we should leave them out to prevent potential regressions in the 
older kernels.

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


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

[Kernel-packages] [Bug 1950712] Re: ESX u20.04 VM refuses to boot after upgrading to kernel 5.4.0-81 and up

[William Overstreet]

** Attachment added: "kernel-5.4.0-90.boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950712/+attachment/5540475/+files/kernel-5.4.0-90.boot.log

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

Title:
  ESX u20.04 VM refuses to boot after upgrading to kernel 5.4.0-81 and
  up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ESX 6.7
  Ubuntu focal 20.04

  While using ESX encryption for EAR, if the MV has a mixture of
  encrypted/unencrypted disks assigned to it, it fails to boot right
  around where the kernel is trying to init the disks.

  I've attempted to boot with 5.11.0-40, same issue.

  I heard from a coworker that Ubuntu bionic 18.04 might be having the
  same issue, which I have not been able to look into yet.

  left alone to boot: https://imgur.com/dUz2966

  where it sits before the hung tasks starts being cranky
  https://imgur.com/crPuuVl

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-80-generic 5.4.0-80.90
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov 12 04:04 seq
   crw-rw+ 1 root audio 116, 33 Nov 12 04:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Fri Nov 12 04:10:26 2021
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=/dev/mapper/rootvg-rootlv ro vga=791 ipv6.disable=1 apparmor=1 
security=apparmor audit=1 audit_backlog_limit=8192 elevator=noop kaslr pti=on 
slab_nomerge page_poison=1 slub_debug=FPZ nosmt
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-80-generic N/A
   linux-backports-modules-5.4.0-80-generic  N/A
   linux-firmware1.187.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/4.15.0.1103.99)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1103.99) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)
ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64)
glibc/2.27-3ubuntu1.4 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1875254] Re: Intermittent display blackouts on event

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  Intermittent display blackouts on event

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  When audio device enters runpm D3(idle for 7 seconds) and then wakes it up to 
make a sound, it flicks the screen.
  This behavior could be observed while plug/remove AC cable or USB disk, or 
open a terminal and press backsapce key.

  [Fix]
  This issue could be fixed by this commit, it fixes the flicker during 
boot-time, but it also fixes the flicker during rumtime wakeup.
  1ee48a61aa57 drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only

  Audio drivers communicate with i915 over HDA bus multiple times during system 
boot-up and each of these transactions result in matching
  get_power/put_power calls to i915, and depending on the platform,
  a modeset change causing visible flicker.
  
  GLK is the only platform with minimum CDCLK significantly lower
  than BCLK, and thus for GLK setting a higher CDCLK is mandatory.

  For other platforms, minimum CDCLK is close but below 2*BCLK
  (e.g. on ICL, CDCLK=176.4kHz with BCLK=96kHz). Spec-wise the constraint
  should be set, but in practise no communication errors have been
  reported and the downside if set is the flicker observed at boot-time.

  [Test]
  Verified on Dell XPS 13 9300

  [Regression Potential]
  Low, it fixes below commit which contains in ubuntu kernel and should have 
been applied on ubuntu kernel, too.
  Fixes: f6ec9483091f ("drm/i915: extend audio CDCLK>=2*BCLK constraint to more 
platforms")

  =

  Issues with the screen going black for a second on certain events on a dell 
XPS 9370 2 in 1, especially when on battery.
  Seems to be a known bug in arch 
(https://wiki.archlinux.org/index.php/Dell_XPS_13_2-in-1_(7390)).
  Last 5.6.7 kernel tested and the issues has disappears but pb with sound card.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucie  2232 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=056fd229-d014-4b3b-a581-1b646105d1ed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  Dell XPS 13 (7390) Display Flickering - 19.10

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  Hi there,
  I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to 
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, 
there is one issue which occurs frequently whereby the display flickers and 
becomes unusable. The best way to describe the appearance is that the image 
becomes heavily distorted. 

  Sometimes it only happens for a split second, other times it is
  permanently distorted. When this happens, simply closing the laptop
  lip and re-opening seems to put the display back into it's correct
  state.

  I didn't experience this issue on 18.04 LTS which is why I believe
  it's a Software Bug within 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 11:11:43 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-10-25 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

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


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

[Kernel-packages] [Bug 1948044] Re: charon-systemd fails on raspberry pi systems under ubuntu 21.10

[Paride Legovini]

** Changed in: strongswan (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  charon-systemd fails on raspberry pi systems under ubuntu 21.10

Status in linux-raspi package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 21.10 from Ubuntu 21.04 my Strongswan
  installation fails. It seems that charon-systemd can´t be started. The
  problem occurs also when using a fresh install of the offical Ubuntu
  Server 21.10 image (from ).

  The problem doesn't exist on a VM running on an AMD64 system.

  I attach the output of journalctl -xeu strongswan.service (after
  increasing charons loglevel to 2).

  Kind regards
  Sven

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: charon-systemd 5.9.1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
  Uname: Linux 5.13.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 21 11:54:32 2021
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: strongswan
  UpgradeStatus: Upgraded to impish on 2021-10-19 (2 days ago)

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


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

[Kernel-packages] [Bug 1950712] Re: ESX u20.04 VM refuses to boot after upgrading to kernel 5.4.0-81 and up

[William Overstreet]

Spoke with the other person, we are getting similar issues in bionic
after 4.15.0-154 for the same type of disk configuration

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

Title:
  ESX u20.04 VM refuses to boot after upgrading to kernel 5.4.0-81 and
  up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ESX 6.7
  Ubuntu focal 20.04

  While using ESX encryption for EAR, if the MV has a mixture of
  encrypted/unencrypted disks assigned to it, it fails to boot right
  around where the kernel is trying to init the disks.

  I've attempted to boot with 5.11.0-40, same issue.

  I heard from a coworker that Ubuntu bionic 18.04 might be having the
  same issue, which I have not been able to look into yet.

  left alone to boot: https://imgur.com/dUz2966

  where it sits before the hung tasks starts being cranky
  https://imgur.com/crPuuVl

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-80-generic 5.4.0-80.90
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov 12 04:04 seq
   crw-rw+ 1 root audio 116, 33 Nov 12 04:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Fri Nov 12 04:10:26 2021
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=/dev/mapper/rootvg-rootlv ro vga=791 ipv6.disable=1 apparmor=1 
security=apparmor audit=1 audit_backlog_limit=8192 elevator=noop kaslr pti=on 
slab_nomerge page_poison=1 slub_debug=FPZ nosmt
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-80-generic N/A
   linux-backports-modules-5.4.0-80-generic  N/A
   linux-firmware1.187.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1020.21)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1020.21) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

v4l2loopback/0.12.5-1ubuntu1 (amd64)
rtl8821ce/5.5.2.1-0ubuntu6 (amd64)
evdi/1.9.1-1ubuntu4~21.04.1 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64)
oss4/4.2-build2010-5ubuntu8 (amd64)
backport-iwlwifi-dkms/8613-0ubuntu2 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
lttng-modules/2.12.5-1ubuntu2~21.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1950804] Re: impish:linux-gcp systemd upstream-1 test fails

[Tim Gardner]

** Attachment added: "Failure log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1950804/+attachment/5540458/+files/log.txt

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

** Tags added: 5.13 gcp impish sru-20211108

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

Title:
  impish:linux-gcp systemd upstream-1 test fails

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

Bug description:
  upstream-1   FAIL non-zero exit status 1

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


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

[Kernel-packages] [Bug 1950804] Re: impish:linux-gcp systemd upstream-1 test fails

[Tim Gardner]

impish linux-gcp 5.13.0-1007.8

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

Title:
  impish:linux-gcp systemd upstream-1 test fails

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

Bug description:
  upstream-1   FAIL non-zero exit status 1

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


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

[Kernel-packages] [Bug 1950804] [NEW] impish:linux-gcp systemd upstream-1 test fails

[Tim Gardner]

Public bug reported:

upstream-1   FAIL non-zero exit status 1

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: 5.13 bot-stop-nagging gcp impish sru-20211108

** Tags added: bot-stop-nagging

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

Title:
  impish:linux-gcp systemd upstream-1 test fails

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

Bug description:
  upstream-1   FAIL non-zero exit status 1

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


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

[Kernel-packages] [Bug 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel

[Mike]

***I have a recent Fossil's ModemManager 1.16.6-2-20.04 and under kernel 5.8.x 
it works:
ModemManager.service - Modem Manager
 Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor >
 Active: active (running) since Fri 2021-11-12 14:46:59 CET; 2h 19min ago
   Main PID: 661 (ModemManager)
  Tasks: 5 (limit: 19006)
 Memory: 11.6M
 CGroup: /system.slice/ModemManager.service
 ├─ 661 /usr/sbin/ModemManager
 └─1054 /usr/libexec/qmi-proxy

nov 12 14:47:03 UB820 ModemManager[661]:   [modem0/sim0] couldn't load li>
nov 12 14:47:03 UB820 ModemManager[661]:   [modem0] couldn't load list of>
nov 12 14:47:03 UB820 ModemManager[661]:   [modem0] couldn't load UE mode>
nov 12 14:47:04 UB820 ModemManager[661]:   [modem0] state changed (unknow>
nov 12 14:47:04 UB820 ModemManager[661]:   [modem0] state changed (disabl>
nov 12 14:47:04 UB820 ModemManager[661]:   [modem0] power state updated: >
nov 12 14:47:04 UB820 ModemManager[661]:   [modem0] state changed (enabli>
nov 12 14:47:05 UB820 ModemManager[661]:   [modem0] 3GPP registration sta>
nov 12 14:47:05 UB820 ModemManager[661]:   [modem0] 3GPP registration sta>
nov 12 14:47:05 UB820 ModemManager[661]:   [modem0] state changed (enable>

***After Ubuntu update to recent kernel 5.1x (5.10.x,5.11.x,5.13.x) 
ModemManager stays the same version and displays:
sudo systemctl status ModemManager
● ModemManager.service - Modem Manager
 Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Fri 2021-11-12 17:08:24 CET; 1min 30s ago
   Main PID: 818 (ModemManager)
  Tasks: 3 (limit: 18992)
 Memory: 6.7M
 CGroup: /system.slice/ModemManager.service
 └─818 /usr/sbin/ModemManager

nov 12 17:09:53 UB820 ModemManager[818]:   [base-manager] couldn't check 
support for device '/sys/devices/pci:00/:00:14.0/usb1/>
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] port cdc-wdm0 
released by device '/sys/devices/pci:00/:00:14.0/usb1/1>
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] port wwan0 
released by device '/sys/devices/pci:00/:00:14.0/usb1/1-3'
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] couldn't check 
support for device '/sys/devices/pci:00/:00:14.0/usb1/>
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] port cdc-wdm0 
released by device '/sys/devices/pci:00/:00:14.0/usb1/1>
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] port wwan0 
released by device '/sys/devices/pci:00/:00:14.0/usb1/1-3'
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] couldn't check 
support for device '/sys/devices/pci:00/:00:14.0/usb1/>
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] port cdc-wdm0 
released by device '/sys/devices/pci:00/:00:14.0/usb1/1>
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] port wwan0 
released by device '/sys/devices/pci:00/:00:14.0/usb1/1-3'
nov 12 17:09:54 UB820 ModemManager[818]:   [base-manager] couldn't check 
support for device '/sys/devices/pci:00/:00:14.0/usb1/

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

Title:
  HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Focal Fossa 20.04.1
  HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It 
is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't 
use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem.
  I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible 
with updated libc from Ubuntu 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mp 2798 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-07 (554 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 03f0:9d1d HP, Inc HP lt4120 Snapdragon X5 LTE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 820 G3
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 ro quiet splash 
resume=UUID=02d7c99f-6ec6-49fa-8577-3e6243dc7891 resume_offset=698368 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  

[Kernel-packages] [Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others

[Jeffrey Bolle]

I have the same issue with a Dell XPS 17 9700 when using 5.13.0-21.

5.13.0-20 works with a full power cycle.

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

Title:
  WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on
  Dell XPS 13 9310 and others

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the 5.13.0-21 kernel, the device fails:

  $ lshw -c network
*-network 
 description: Network controller
 product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)]
 vendor: Qualcomm
 physical id: 0
 bus info: pci@:72:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=ath11k_pci latency=0
 resources: irq:182 memory:a250-a25f

  $ lspci | grep Qualcomm
  72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter 
[AX500-DBS (2x2)] (rev 01)

  $ sudo modprobe ath11k_pci

  $ sudo dmesg | grep ath
  [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002)
  [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0
  [   10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110
  [   10.337692] ath11k_pci :72:00.0: failed to send qmi firmware 
indication: -110
  [   39.931711] ath11k_pci :72:00.0: link down error during global reset
  [   45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [   45.575668] ath11k_pci :72:00.0: qca6390 hw2.0
  [   45.630047] ath11k_pci :72:00.0: failed to set pcie link register 
0x01e0c0ac: 0x != 0x0010
  [   45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110
  [   45.650253] ath11k_pci :72:00.0: link down error during global reset

  $ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  In the 5.13.0-20 kernel, the device works:

  $ sudo dmesg | grep ath
  [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002)
  [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0
  [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 
0xff soc_id 0x
  [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 
2020-06-24 19:50 fw_build_id
  [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0
  [ 351.080712] ath11k_pci :72:00.0: link down error during global reset
  [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 15:23:07 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-05-04 (190 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 3.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.2.0
  dmi.board.name: 0MRT12
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1950793] Re: util-linux/lsblk reports WWN as SERIAL in focal

[Boris]

Maybe this is the issue: https://github.com/util-linux/util-
linux/commit/b95752ad206222dfaa854a01c6106c89d2c607a2

https://github.com/util-linux/util-linux/issues/1143

Maybe you can backport it?

** Bug watch added: github.com/util-linux/util-linux/issues #1143
   https://github.com/util-linux/util-linux/issues/1143

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

Title:
  util-linux/lsblk reports WWN as SERIAL in focal

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've come across the problem that lsblk treats the WWN as SN.

  ~# lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ~# apt-cache policy util-linux
  util-linux:
Installed: 2.34-0.1ubuntu9.1
Candidate: 2.34-0.1ubuntu9.1
Version table:
   *** 2.34-0.1ubuntu9.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.34-0.1ubuntu9 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  What I expected to happen:
  Show the disks serial when using the SERIAL output

  What happened instead:
  The WWN is printed instead. This does not happen with every disk.

  how to reproduce:
  ~# lsblk -dn -o WWN /dev/sdb
  0x539ad8d2cd39
  ~# lsblk -dn -o SERIAL /dev/sdb
  539ad8d2cd39

  smartctl show the correct serial

  ~# smartctl -a /dev/sdb
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Toshiba MG06ACA... Enterprise Capacity HDD
  Device Model: TOSHIBA MG06ACA800E
  Serial Number:41P0A0SHFKRE
  LU WWN Device Id: 5 39 ad8d2cd39
  <... snip ...>

  A disks where it works:
  ~# lsblk -dn -o SERIAL /dev/sdn
  SMC0515D93017CH75029
  ~# lsblk -dn -o WWN /dev/sdn
  0x515d93017c29

  ~# smartctl -a /dev/sdn
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Silicon Motion based OEM SSDs
  Device Model: SuperMicro SSD
  Serial Number:SMC0515D93017CH75029
  LU WWN Device Id: 5 15d930 17c29
  <... snip ...>

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


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

[Kernel-packages] [Bug 1948436] Re: Add RevID field to VPD info in EEPROM

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-bluefield/5.4.0-1022.25
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal

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

Title:
  Add RevID field to VPD info in EEPROM

Status in linux-bluefield package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  Currently, the VPD info stored in the EEPROM does not include a Rev ID. This 
field is incremented when a PN goes through minor HW changes. Sometimes, SW 
needs to differentiate the two versions of the card. Hence, this field should 
be supported in the EEPROM MFG partition.

  [Fix]
  EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add 
it to the EEPROM MFG and provide a sysfs entry to access the same via 
mlx-bootctl.

  [Test Case]
  This field is typically programmed at the manufacturing step using the bfcfg 
tool which uses the write mechanism in the driver and then the MFG partition is 
locked. Reading the "rev" sysfs will show the current value.

  [Regression Potential]
  Can be considered minimum.

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


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

[Kernel-packages] [Bug 1948434] Re: Check if secure boot is enabled with development keys

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-bluefield/5.4.0-1022.25
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal

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

Title:
  Check if secure boot is enabled with development keys

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  Currently, there is no indication from mlx-bootctl when the user reads the 
lifecycle_state sysfs as to whether secure boot is enabled with development 
keys or production keys. In order to make this clear to the user, add a check 
in the driver.

  [Fix]
  Check the secure boot development mode status bit. If secure boot is enabled 
with the development key, then print it to the output buffer when 
lifecycle_state_show() is invoked.

  [Test Case]
  On a system in secure state, if it has been programmed with development keys, 
then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should 
print a message that indicates the same.
  Similarly, a secure system which has been programmed with production keys 
must print the appropriate message when the lifecycle_state sysfs is read.

  [Regression Potential]
  Can be considered minimum.

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


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

[Kernel-packages] [Bug 1950540] Re: alsa/sof: All audio jacks can't detect hotplug when only codec is suspended

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oem-5.13/5.13.0-1020.24
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-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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-focal

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

Title:
  alsa/sof: All audio jacks can't detect hotplug when only codec is
  suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  If the codec is in rt_suspend while the controller is in rt_resume,
  all audio jacks can't detect hotplug.

  [Fix]
  Backport a upstream patch, this will enable WAKEEN in the period
  between codec suspend and controller suspend.

  [Test]
  Booting the patched kernel, add snd_sof_pci.sof_pci_debug=0x1 in
  the bootargs, plug the headset to the audio jacks, the system
  could detect the plug in or plug out.

  [Where problems could occur]
  The patch enable the WAKEEN after codec is in rt_suspend, this
  could affect the audio jack hotplug detection, if it introduces
  regression, it will be on the audio jack detection, but this
  possibility is very low, we already verified this patch on
  many machines.

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


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

[Kernel-packages] [Bug 1950793] Re: util-linux/lsblk reports WWN as SERIAL in focal

[Boris]

As I don't know what kind of data will be sent and this is a production
system with customer data on it, I won't do this.

There is also no need to actuall collect data from the system, as it is
a simple out of the box installation.

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

Title:
  util-linux/lsblk reports WWN as SERIAL in focal

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've come across the problem that lsblk treats the WWN as SN.

  ~# lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ~# apt-cache policy util-linux
  util-linux:
Installed: 2.34-0.1ubuntu9.1
Candidate: 2.34-0.1ubuntu9.1
Version table:
   *** 2.34-0.1ubuntu9.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.34-0.1ubuntu9 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  What I expected to happen:
  Show the disks serial when using the SERIAL output

  What happened instead:
  The WWN is printed instead. This does not happen with every disk.

  how to reproduce:
  ~# lsblk -dn -o WWN /dev/sdb
  0x539ad8d2cd39
  ~# lsblk -dn -o SERIAL /dev/sdb
  539ad8d2cd39

  smartctl show the correct serial

  ~# smartctl -a /dev/sdb
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Toshiba MG06ACA... Enterprise Capacity HDD
  Device Model: TOSHIBA MG06ACA800E
  Serial Number:41P0A0SHFKRE
  LU WWN Device Id: 5 39 ad8d2cd39
  <... snip ...>

  A disks where it works:
  ~# lsblk -dn -o SERIAL /dev/sdn
  SMC0515D93017CH75029
  ~# lsblk -dn -o WWN /dev/sdn
  0x515d93017c29

  ~# smartctl -a /dev/sdn
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Silicon Motion based OEM SSDs
  Device Model: SuperMicro SSD
  Serial Number:SMC0515D93017CH75029
  LU WWN Device Id: 5 15d930 17c29
  <... snip ...>

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


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

[Kernel-packages] [Bug 1950471] Re: Touchpad on HP Spectre x360 gets into unusable state

[Michael A Shantzis]

Ran apport-collect as requested but it printed out the following
messages, then hung in the end:

% apport-collect 1950471
dpkg-query: no packages found matching libinput
dpkg-query: no packages found matching linux

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1950793

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

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

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

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

** Tags added: focal

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

Title:
  util-linux/lsblk reports WWN as SERIAL in focal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've come across the problem that lsblk treats the WWN as SN.

  ~# lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ~# apt-cache policy util-linux
  util-linux:
Installed: 2.34-0.1ubuntu9.1
Candidate: 2.34-0.1ubuntu9.1
Version table:
   *** 2.34-0.1ubuntu9.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.34-0.1ubuntu9 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  What I expected to happen:
  Show the disks serial when using the SERIAL output

  What happened instead:
  The WWN is printed instead. This does not happen with every disk.

  how to reproduce:
  ~# lsblk -dn -o WWN /dev/sdb
  0x539ad8d2cd39
  ~# lsblk -dn -o SERIAL /dev/sdb
  539ad8d2cd39

  smartctl show the correct serial

  ~# smartctl -a /dev/sdb
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Toshiba MG06ACA... Enterprise Capacity HDD
  Device Model: TOSHIBA MG06ACA800E
  Serial Number:41P0A0SHFKRE
  LU WWN Device Id: 5 39 ad8d2cd39
  <... snip ...>

  A disks where it works:
  ~# lsblk -dn -o SERIAL /dev/sdn
  SMC0515D93017CH75029
  ~# lsblk -dn -o WWN /dev/sdn
  0x515d93017c29

  ~# smartctl -a /dev/sdn
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Silicon Motion based OEM SSDs
  Device Model: SuperMicro SSD
  Serial Number:SMC0515D93017CH75029
  LU WWN Device Id: 5 15d930 17c29
  <... snip ...>

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


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

[Kernel-packages] [Bug 1950471] Lsusb.txt

[Michael A Shantzis]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1950471/+attachment/5540440/+files/Lsusb.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] PulseList.txt

[Michael A Shantzis]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540448/+files/PulseList.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540442/+files/Lsusb-v.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: 

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

[Michael A Shantzis]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1950471/+attachment/5540449/+files/RfKill.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] PaInfo.txt

[Michael A Shantzis]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1950471/+attachment/5540443/+files/PaInfo.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] acpidump.txt

[Michael A Shantzis]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540453/+files/acpidump.txt

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] Xrandr.txt

[Michael A Shantzis]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1950471/+attachment/5540452/+files/Xrandr.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540444/+files/ProcCpuinfo.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] xdpyinfo.txt

[Michael A Shantzis]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540454/+files/xdpyinfo.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: 

[Kernel-packages] [Bug 1950471] Lspci-vt.txt

[Michael A Shantzis]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540439/+files/Lspci-vt.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540437/+files/IwConfig.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] DpkgLog.txt

[Michael A Shantzis]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540436/+files/DpkgLog.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] Re: Touchpad on HP Spectre x360 gets into unusable state

[Michael A Shantzis]

apport information

** Description changed:

  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially starts,
  it's working fine, then at some point in time (it's unclear what
  triggers it), it gets into this state where simply doing a single-finger
  swipe to move the cursor no longer works. If I press down and swipe, it
  does move/select as expected, but when I return to not pressing down, it
  goes back to its previous, unworking state.
  
  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  michael1879 F pulseaudio
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CasperMD5CheckResult: pass
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ DistUpgraded: Fresh install
+ DistroCodename: impish
+ 

[Kernel-packages] [Bug 1950471] Lspci-vt.txt

[Michael A Shantzis]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540432/+files/Lspci-vt.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] DpkgLog.txt

[Michael A Shantzis]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540429/+files/DpkgLog.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1950471/+attachment/5540430/+files/IwConfig.txt

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

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

[Michael A Shantzis]

apport information

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

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

Bug description:
  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially
  starts, it's working fine, then at some point in time (it's unclear
  what triggers it), it gets into this state where simply doing a
  single-finger swipe to move the cursor no longer works. If I press
  down and swipe, it does move/select as expected, but when I return to
  not pressing down, it goes back to its previous, unworking state.

  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1929 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
  InstallationDate: Installed on 2021-10-28 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP Spectre x360 Convertible 13t-aw200
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201.1
  Tags:  impish wayland-session ubuntu wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2021
  dmi.bios.release: 15.13
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8709
  dmi.board.vendor: HP
  dmi.board.version: 31.32
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 31.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13t-aw200
  dmi.product.sku: 8WP89AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1950471] Re: Touchpad on HP Spectre x360 gets into unusable state

[Michael A Shantzis]

apport information

** Tags added: apport-collected ubuntu

** Description changed:

  I have an HP Spectre x360 (13t-aw200) that has had problems with its
  touchpad since I first loaded Ubuntu onto it. When it initially starts,
  it's working fine, then at some point in time (it's unclear what
  triggers it), it gets into this state where simply doing a single-finger
  swipe to move the cursor no longer works. If I press down and swipe, it
  does move/select as expected, but when I return to not pressing down, it
  goes back to its previous, unworking state.
  
  Other clues:
  - It appears if I press HARD but don't cause a down event, it SOMETIMES moves 
the cursor.
  - If it's in this state and I'm on some scrolling window, it will scroll with 
a single finger (i.e. as it acts as if I have two fingers down).
  - It often will return to a working state for a while then go back to not 
working.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 05:56:51 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-10-28 (13 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  michael1929 F pulseaudio
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CasperMD5CheckResult: pass
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ DistUpgraded: Fresh install
+ DistroCodename: impish
+ DistroRelease: Ubuntu 21.10
+ DistroVariant: ubuntu
+ GraphicsCard:
+  Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
+Subsystem: Hewlett-Packard Company TigerLake GT2 [Iris Xe Graphics] 
[103c:8709]
+ InstallationDate: Installed on 2021-10-28 (15 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ MachineType: HP HP Spectre x360 Convertible 13t-aw200
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/zsh
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/vg--crypt-lv--root ro quiet splash i8042.dumbkbd=1 vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-19-generic N/A
+  linux-backports-modules-5.13.0-19-generic  N/A
+  linux-firmware 1.201.1
+ Tags:  impish wayland-session ubuntu wayland-session
+ Uname: Linux 5.13.0-19-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2021
+ dmi.bios.release: 15.13
+ dmi.bios.vendor: AMI
+ dmi.bios.version: F.13
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 8709
+ dmi.board.vendor: HP
+ dmi.board.version: 31.32
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: HP
+ dmi.chassis.version: Chassis Version
+ dmi.ec.firmware.release: 31.32
+ dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd04/01/2021:br15.13:efr31.32:svnHP:pnHPSpectrex360Convertible13t-aw200:pvr:sku8WP89AV:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV HP Spectre
+ dmi.product.name: HP Spectre x360 Convertible 13t-aw200
+ dmi.product.sku: 8WP89AV
+ dmi.sys.vendor: HP
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.107-8ubuntu1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
+ version.libgl1-mesa-glx: libgl1-mesa-glx N/A
+ version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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

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

Title:
  Touchpad on HP Spectre x360 gets into unusable state

Status in libinput package in 

[Kernel-packages] [Bug 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle

[Anthony Wong]

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

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  USB Type-C hotplug event not handled properly in TGL-H system during
  s2idle

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  The system will be hold by the infinite loop in ACPI method IPCS after 
exiting s2idle in TGL-H systems if the docking station with external display 
connected is unplugged when the system is still in s2idle. It's
  because the system is unaware of the unplug event and it seems keep something 
asserted which will never be released while the system trying to exit s2idle.

  [Fix]
  Disconnect TypeC PHYs during system suspend and shutdown, even with the
  corresponding TypeC sink still plugged to its connector. The HPD event is no 
longer triggered when the system is in s2idle so the resume process will not be 
hindered.

  [Test Case]
  1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the 
NVIDIA GPU is running in either On-Demand mode or Performance mode.
  2. Connect the docking station with the external display connected.
  3. Suspend the system.
  4. Remove the docking station when the system is suspended.
  5. Press power button to wake up the system and wait > 1 minutes to make sure 
if the display comes back.

  [Where problems could occur]
  Low. This will only make a difference in the TypeC DP alternate mode, and the 
display driver will detect the display connector after resume.

  == Original Bug Description ==

  [Summary]
  As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting 
s2idle in TGL-H systems if the USB Type-C docking/dongle with external display 
connected is unplugged when the system is still in s2idle. The system will be 
hold by the infinite loop in ACPI method IPCS and then the PCIe root port of 
NVIDIA gpu fails the power transition from D3cold to D0. It's because the 
display connector hotplug event not handled properly in graphics drivers and 
the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit.

  [ 154.446781]
  [ 154.446783]
  [ 154.446783] Initialized Local Variables for Method [IPCS]:
  [ 154.446784] Local0: 9863e365  Integer 09C5
  [ 154.446790]
  [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments
  defined for method invocation)
  [ 154.446792] Arg0: 25568fbd  Integer 00AC
  [ 154.446795] Arg1: 9ef30e76  Integer 
  [ 154.446798] Arg2: fdf820f0  Integer 0010
  [ 154.446801] Arg3: 9fc2a088  Integer 0001
  [ 154.446804] Arg4: 3a3418f7  Integer 0001
  [ 154.446807] Arg5: 20c4b87c  Integer 
  [ 154.446810] Arg6: 8b965a8a  Integer 
  [ 154.446813]
  [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error
  (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to
  previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due
  to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529)
  [ 154.446860] acpi device:02: Failed to change power state to D0
  [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0
  for parent in (unknown)

  [Reproduce Steps]
  1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system.
  2. Connect to external display to HDMI/DisplayPort of the docking
  3. 

[Kernel-packages] [Bug 1950793] [NEW] util-linux/lsblk reports WWN as SERIAL in focal

[Boris]

Public bug reported:

I've come across the problem that lsblk treats the WWN as SN.

~# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04

~# apt-cache policy util-linux
util-linux:
  Installed: 2.34-0.1ubuntu9.1
  Candidate: 2.34-0.1ubuntu9.1
  Version table:
 *** 2.34-0.1ubuntu9.1 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.34-0.1ubuntu9 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

What I expected to happen:
Show the disks serial when using the SERIAL output

What happened instead:
The WWN is printed instead. This does not happen with every disk.

how to reproduce:
~# lsblk -dn -o WWN /dev/sdb
0x539ad8d2cd39
~# lsblk -dn -o SERIAL /dev/sdb
539ad8d2cd39

smartctl show the correct serial

~# smartctl -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Toshiba MG06ACA... Enterprise Capacity HDD
Device Model: TOSHIBA MG06ACA800E
Serial Number:41P0A0SHFKRE
LU WWN Device Id: 5 39 ad8d2cd39
<... snip ...>

A disks where it works:
~# lsblk -dn -o SERIAL /dev/sdn
SMC0515D93017CH75029
~# lsblk -dn -o WWN /dev/sdn
0x515d93017c29

~# smartctl -a /dev/sdn
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Silicon Motion based OEM SSDs
Device Model: SuperMicro SSD
Serial Number:SMC0515D93017CH75029
LU WWN Device Id: 5 15d930 17c29
<... snip ...>

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

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

Title:
  util-linux/lsblk reports WWN as SERIAL in focal

Status in linux package in Ubuntu:
  New

Bug description:
  I've come across the problem that lsblk treats the WWN as SN.

  ~# lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ~# apt-cache policy util-linux
  util-linux:
Installed: 2.34-0.1ubuntu9.1
Candidate: 2.34-0.1ubuntu9.1
Version table:
   *** 2.34-0.1ubuntu9.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.34-0.1ubuntu9 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  What I expected to happen:
  Show the disks serial when using the SERIAL output

  What happened instead:
  The WWN is printed instead. This does not happen with every disk.

  how to reproduce:
  ~# lsblk -dn -o WWN /dev/sdb
  0x539ad8d2cd39
  ~# lsblk -dn -o SERIAL /dev/sdb
  539ad8d2cd39

  smartctl show the correct serial

  ~# smartctl -a /dev/sdb
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Toshiba MG06ACA... Enterprise Capacity HDD
  Device Model: TOSHIBA MG06ACA800E
  Serial Number:41P0A0SHFKRE
  LU WWN Device Id: 5 39 ad8d2cd39
  <... snip ...>

  A disks where it works:
  ~# lsblk -dn -o SERIAL /dev/sdn
  SMC0515D93017CH75029
  ~# lsblk -dn -o WWN /dev/sdn
  0x515d93017c29

  ~# smartctl -a /dev/sdn
  smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build)
  Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Family: Silicon Motion based OEM SSDs
  Device Model: SuperMicro SSD
  Serial Number:SMC0515D93017CH75029
  LU WWN Device Id: 5 15d930 17c29
  <... snip ...>

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


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

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

[bugproxy]

I can repro this with the latest Focal kernel on:

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

Title:
  IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash
  P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  It looks like our P8 node "entei" tend to fail with the IPv6 TCP test
  from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels:

   # send cpu 119, receive socket 119
   # send cpu 121, receive socket 121
   # send cpu 123, receive socket 123
   # send cpu 125, receive socket 125
   # send cpu 127, receive socket 127
   #  IPv6 TCP 
  publish-job-status: using request.json

  It failed silently here, this can be 100% reproduced with Groovy 5.8
  and Focal 5.8.

  This will cause the ubuntu_kernel_selftests being interrupted, the
  test result for other tests cannot be processed to our result page.

  Please find attachment for the complete "net" test result on this node
  with Groovy 5.8.0-52.59

  Add the kqa-blocker tag as this might needs to be manually verified.

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


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

[Kernel-packages] [Bug 1950117] Re: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi

[Juerg Haefliger]

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

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

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

Title:
  [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
  5.13.0-1010.11-raspi

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [Description]
  Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi.

  Fail rate: 12 times out of 14 attempts

  [Steps to reproduce]
  1. Flash image (see additional information)
  2. Boot into system
  3. apt dist-upgrade all packages and reboot
  4. Enable proposed repository
  5. apt install linux-raspi
  6. Reboot

  [Actual result]
  Device does not boot into system

  [Expected result]
  Boot into system successfully

  [Additional information]
  Hardware: rpi3 and cm3+
  Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz
     ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz
  Kernel Version: 5.13.0-1010.11-raspi

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


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

[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

[Daniel Axtens]

I can repro on upstream, all the way back to 5.4.0. It might have
existed before that - I haven't tested any earlier yet.

Was the test methodology changed just before this was found? I'm just
wondering why it suddenly appeared ~a year after Focal was released. I
thought it might have been a patch picked up for a SRU, but it's looking
like the problem predates Focal by some way...

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

Title:
  IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash
  P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  It looks like our P8 node "entei" tend to fail with the IPv6 TCP test
  from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels:

   # send cpu 119, receive socket 119
   # send cpu 121, receive socket 121
   # send cpu 123, receive socket 123
   # send cpu 125, receive socket 125
   # send cpu 127, receive socket 127
   #  IPv6 TCP 
  publish-job-status: using request.json

  It failed silently here, this can be 100% reproduced with Groovy 5.8
  and Focal 5.8.

  This will cause the ubuntu_kernel_selftests being interrupted, the
  test result for other tests cannot be processed to our result page.

  Please find attachment for the complete "net" test result on this node
  with Groovy 5.8.0-52.59

  Add the kqa-blocker tag as this might needs to be manually verified.

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


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

[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450

[Sadovskiy Denis Olegovich]

Thanks, "nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1" works on
Ubuntu 20.04 5.11.0-40-generic with Nvidia driver 495.44 on Lenovo
Legion 15ARH05.

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

Title:
  no brightness control in {455,460} after update from 450

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
  GTX 1050 Ti Mobile]:

  WORKS FINE:
  nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1

  NO BRIGHTNESS CONTROL:
  nvidia-driver-455: 455.38-0ubuntu0.18.04.1
  nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
  nvidia-driver-460: 460.39-0ubuntu0.18.04.1

  *WORKAROUND: See comment #11 (add nvidia drivers to initramfs).

  *Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
  not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.

  Updating to nvidia-driver-455 (or -460) results in loss of brightness
  control.  On boot, the laptop display brightness is somewhat less than
  fully bright and cannot be changed.   The brightness up/down keys do
  pop up the gnome gui brightness widget, and
  /sys/class/backlight/nvidia_0/* values do change, but the actual
  display's brightness does not.

  Problem occurs with either version of nvidia-driver-455 (the archive
  or the ~graphics-drivers/PPA) or any version of -460.

  Normal functionality returns if I downgrade to any version of nvidia-
  driver-450.

  Also observed: 455 and 460 temporarily display some pixel garbage
  while mode-switching during the graphic login sequence.  Only a minor
  glitch, but note that 450 does not exhibit that issue either.

  Note also that manually applying this to 
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
  
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Codename: bionic

  kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
  2020 x86_64 x86_64 x86_64 GNU/Linux

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


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

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

[Hemanth V. Alluri]

Oh, I should mention that I faced the same issue when running Ubuntu
18.04 (DE: XFCE) last year. Sadly, I don't recall which version of the
kernel I was running - the damage to my battery ended up getting so bad
that by the end of the year, my battery lost it's capacity to hold
charge and I had to replace it (got warnings from OEM software on
Windows, as well as on boot - before the bootloader menu loaded).

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

[Hemanth V. Alluri]

Hello. I would just like to mention that I, too, face this same exact
issue. I'm running Manjaro and can confirm that I observe this issue on
both Linux 5.10.70-1 and Linux 5.13.9-2. After a full week of testing I
can confirm that I face this power drain only when gracefully shutting
down from Linux.

Basic hardware specs:
  OS: Manjaro Linux x86_64
  Host: HP Pavilion Laptop 15-cc1xx
  Kernel: 5.10.70-1-MANJARO
  Resolution: 1920x1080
  DE: Plasma 5.22.5
  WM: KWin
  CPU: Intel i7-8550U (8) @ 4.000GHz
  GPU: Intel UHD Graphics 620
  GPU: NVIDIA GeForce 940MX

Bios: InsydeH20 f.36 Rev 5

Some timings I've recorded:
  - 44% drain in 9h20m
  - 36% drain in 6h48m
  - 32% drain in 5h35m

When sifting through the system logs using journalctl I didn't find
anything that stuck out as unusually suspicious. No errors as far as I
can tell - but honestly, I don't know enough about Linux to be 100% sure
so please don't hold me to this. I can attach these logs if needed.

Commands used:
  - journalctl -b -1 -r
  - journalctl /sbin/init -b -1 -r | grep -i shutdown
  - journalctl /sbin/init -b -1 -p err..alert

Like asgard2 I can confirm that I do not have wake-on-lan enabled (my
system doesn't support it in the first place as confirmed by the lack of
an option in my UEFI menu and no indication from ethtool), no usb ports
providing power when shutdown, no noticible power drain when shutting
down from the UEFI menu or from Windows, etc. basically everything they
have reported above.

I'd love to help get this fixed - if I can help out by providing more
data, please let me know.

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1950014] Re: Focal update: v5.4.153 upstream stable release

[Stefan Bader]

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

Title:
  Focal update: v5.4.153 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

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

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

  Partially revert "usb: Kconfig: using select for USB_COMMON dependency"
  USB: cdc-acm: fix racy tty buffer accesses
  USB: cdc-acm: fix break reporting
  usb: typec: tcpm: handle SRC_STARTUP state if cc changes
  xen/privcmd: fix error handling in mmap-resource processing
  mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk
  ovl: fix missing negative dentry check in ovl_rename()
  nfsd: fix error handling of register_pernet_subsys() in init_nfsd()
  nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero
  xen/balloon: fix cancelled balloon action
  ARM: dts: omap3430-sdp: Fix NAND device node
  ARM: dts: qcom: apq8064: use compatible which contains chipid
  MIPS: BPF: Restore MIPS32 cBPF JIT
  bpf, mips: Validate conditional branch offsets
  soc: qcom: socinfo: Fixed argument passed to platform_set_data()
  ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference
  soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment
  ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo
  ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo
  arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding
  xtensa: move XCHAL_KIO_* definitions to kmem_layout.h
  xtensa: use CONFIG_USE_OF instead of CONFIG_OF
  xtensa: call irqchip_init only when CONFIG_USE_OF is selected
  bpf, arm: Fix register clobbering in div/mod implementation
  bpf: Fix integer overflow in prealloc_elems_and_freelist()
  phy: mdio: fix memory leak
  net_sched: fix NULL deref in fifo_set_limit()
  powerpc/fsl/dts: Fix phy-connection-type for fm1mac3
  ptp_pch: Load module automatically if ID matches
  arm64: dts: freescale: Fix SP805 clock-names
  arm64: dts: ls1028a: add missing CAN nodes
  ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence
  net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size()
  net/sched: sch_taprio: properly cancel timer from taprio_destroy()
  net: sfp: Fix typo in state machine debug string
  netlink: annotate data races around nlk->bound
  bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893
  video: fbdev: gbefb: Only instantiate device when built for IP32
  drm/nouveau/debugfs: fix file release memory leak
  gve: Correct available tx qpl check
  rtnetlink: fix if_nlmsg_stats_size() under estimation
  gve: fix gve_get_stats()
  i40e: fix endless loop under rtnl
  i40e: Fix freeing of uninitialized misc IRQ vector
  net: prefer socket bound to interface when not in VRF
  i2c: acpi: fix resource leak in reconfiguration device addition
  bpf, s390: Fix potential memory leak about jit_data
  RISC-V: Include clone3() on rv32
  x86/platform/olpc: Correct ifdef symbol to intended CONFIG_OLPC_XO15_SCI
  x86/hpet: Use another crystalball to evaluate HPET usability
  x86/Kconfig: Correct reference to MWINCHIP3D
  Linux 5.4.153
  UBUNTU: upstream stable to v5.4.153

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


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

[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk

[Mauricio Faria de Oliveira]

Verified bionic, focal, and hirsute (hwe kernel in focal) with steps in
comment #1.

The kernel packages in -updates hit the issue.
The kernel packages in -proposed don't hit it.

ubuntu@mfo-aufs-bionic:~/aufs$ uname -rv
4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021

ubuntu@mfo-aufs-focal:~$ uname -rv
5.4.0-91-generic #102-Ubuntu SMP Fri Nov 5 16:31:28 UTC 2021

ubuntu@mfo-aufs-focal:~/aufs$ uname -rv
5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021


** Tags removed: verification-needed-bionic verification-needed-focal 
verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal 
verification-done-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/1948470

Title:
  aufs: kernel bug with apparmor and fuseblk

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Invalid

Bug description:
  [Impact]

   * AppArmor-enabled applications on the aufs filesystem
     might hit a kernel bug when getting file attributes.

   * The aufs filesystem explicitly assigns a NULL pointer
     to `struct path.mnt` for `vfs_getattr()`, which calls
     into AppArmor that checks `struct path.mnt->mnt_flags`,
     triggering a kernel NULL pointer dereference.

   * This is almost 10 years old [1,2], reproducible w/ the
     Linux v3.2 kernel, but it's rare as apparently it needs
     a fuseblk mount as an aufs branch, and file creation/
     open (O_CREAT), with a filename that exists only in a
     lower aufs branch. On Linux v5.15-rc* it doesn't need
     AppArmor anymore.

  [Fix]

   * The patch fixing this issue does set `struct path.mnt`
     properly, by taking `struct path` as parameter instead
     of just `struct dentry` (and making up an incomplete
     `struct path` w/ that `dentry` and `mnt = NULL`.)

   * Since it changes the signature of a key, leaf function
     with several callers, the patch is a bit long/refactor,
     but it has been tested by the upstream aufs maintainer
     with a private test-suite.

  [Test Plan]

   * Synthetic reproducer available in [1] and comment #1.

  [Regression Potential]

   * Regressions would probably manifest as kernel errors
     mostly in the lookup and open paths, but more subtle
     manifestations would be possible as well.

   * The patch modifies a fair number of functions, even if
     doing so in simple ways. The synthetic reproducer only
     covers one of those functions.

   * The other code paths have been tested by the maintainer
     w/ the mainline kernel, and should be equivalent to our
     kernel as none of such changed for cherry-pick/backport.

   * The upstream aufs maintainer runs a private test suite
     that covers several features and use cases of aufs, so
     hopefully that provides some relief to take this patch.

  [Other Info]

   * Impish no longer ships aufs; no fix needed.
   * Hirsute/Focal/Bionic do/need it. (H only for backports)
   * Hirsute/Focal are clean cherry-picks.
   * Bionic is a trivial backport.

  [1] https://sourceforge.net/p/aufs/mailman/message/37363599/
  [2] 
https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic

  [Kernel Traces]

  BUG: kernel NULL pointer dereference, address: 0010
  ...
  CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure 
#60~18.04.1-Ubuntu
  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 
090008 12/07/2018
  RIP: 0010:aa_path_name+0x55/0x370
  ...
  Call Trace:
  ? request_wait_answer+0xc4/0x200
  path_name+0x60/0xe0
  profile_path_perm.part.9+0x57/0xa0
  aa_path_perm+0xe2/0x130
  common_perm+0x59/0x130
  common_perm_cond+0x4c/0x70
  apparmor_inode_getattr+0x1d/0x20
  security_inode_getattr+0x35/0x50
  vfs_getattr+0x21/0x40
  vfsub_update_h_iattr+0x95/0xb0 [aufs]
  ? lookup_dcache+0x44/0x70
  ? lookup_one_len+0x66/0x90
  vfsub_lookup_one_len+0x50/0x70 [aufs]
  au_sio_lkup_one+0x8e/0xa0 [aufs]
  au_lkup_dentry+0x3fa/0x660 [aufs]
  aufs_lookup.part.35+0x11c/0x210 [aufs]
  aufs_atomic_open+0xec/0x3c0 [aufs]
  path_openat+0xe30/0x16a0
  ? aufs_lookup+0x30/0x30 [aufs]
  ? path_openat+0xe30/0x16a0
  ? unlock_page_memcg+0x12/0x20
  ? filemap_map_pages+0x17d/0x3b0
  do_filp_open+0x9b/0x110
  ? __check_object_size+0xdb/0x1b0
  ? __alloc_fd+0xb2/0x170
  do_sys_open+0x1ba/0x2e0
  ? do_sys_open+0x1ba/0x2e0
  __x64_sys_openat+0x20/0x30
  do_syscall_64+0x5e/0x200
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  RIP: 0033:0x4a06fa

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1950009] Re: Focal update: v5.4.152 upstream stable release

[Stefan Bader]

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

Title:
  Focal update: v5.4.152 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

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

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

  net: mdio: introduce a shutdown method to mdio device drivers
  xen-netback: correct success/error reporting for the SKB-with-fraglist case
  sparc64: fix pci_iounmap() when CONFIG_PCI is not set
  ext2: fix sleeping in atomic bugs on error
  scsi: sd: Free scsi_disk device via put_device()
  usb: testusb: Fix for showing the connection speed
  usb: dwc2: check return value after calling platform_get_resource()
  selftests: be sure to make khdr before other targets
  selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn
  scsi: ses: Retry failed Send/Receive Diagnostic commands
  tools/vm/page-types: remove dependency on opt_file for idle page tracking
  KVM: do not shrink halt_poll_ns below grow_start
  kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[]
  perf/x86: Reset destroy callback on event init failure
  silence nfscache allocation warnings with kvzalloc
  libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD.
  Linux 5.4.152
  UBUNTU: upstream stable to v5.4.152

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


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

[Kernel-packages] [Bug 1950665] Autopkgtest regression report (nvidia-graphics-drivers-470/470.86-0ubuntu0.21.10.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted nvidia-graphics-drivers-470 
(470.86-0ubuntu0.21.10.1) for impish have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build2 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#nvidia-graphics-drivers-470

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Update the 470 NVIDIA driver to 470.86

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Committed

Bug description:
  Update the 470 NVIDIA series in Bionic, Focal, Hirsute, and Impish.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470 ==
    * New upstream release (LP: #1950665):
  - Fixed a regression which prevented DisplayPort and HDMI 2.1
    variable refresh rate (VRR) G-SYNC Compatible monitors from
    functioning correctly in variable refresh rate mode, resulting
    in issues such as flickering.

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: impish

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

Title:
  Thunderbolt dock usb ports not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo Thunderbolt 3 Gen 2 dock and wanted to use this with
  Ubuntu 21.10. When booting an unmodified version the usb ports do not
  work. After an inspection with journalctl I find the error message "No
  bus number available for hot-added bridge" and a google search led me
  to this workaround: Add pci=realloc,assign-busses,hpbussize=0x33. This
  line as a boot parameter makes the dock work as intended. I believe
  this should be fixed so that people using the live image can see that
  their hardware works as intended before installing.

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


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

[Kernel-packages] [Bug 1950064] Re: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi

[Stefan Bader]

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

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

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

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

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

Title:
  [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after
  upgrade to kernel 5.11.0-1022.23-raspi

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Hirsute:
  In Progress

Bug description:
  [Description]
  Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 
5.11.0-1022.23-raspi

  [Steps to reproduce]
  1. Flash image (see additional information)
  2. Boot into system
  3. apt dist-upgrade all packages and reboot
  4. Enable proposed repository
  5. apt install linux-raspi
  6. Reboot

  [Actual result]
  Device does not boot into system

  [Expected result]
  Boot into system successfully

  [Additional information]
  Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+
  Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz
     ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz
  Kernel Version: 5.11.0-1022.23-raspi

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


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